minimap in Glamour-Roassal
by Usman Bhatti
Hello,
I am trying to create a roassal minimap in a glamour browser. But I do not
get a minimap when pressing m key.
It might be something to do with how keystrokes are interpreted in Glamour.
can you have a look?
Here's a simple browser with a roassal visualization (adapted from one of
ben's mail on moose-dev).
| browser viewHack |
browser := GLMTabulator new.
browser column: #list; column: #drawing.
browser transmit
to: #list;
andShow: [ :a | a list ].
browser transmit
to: #drawing;
andShow: [ :a | a roassal painting:
[ :moview :collection |
moview raw @ (ROMiniMap new targetView: moview stack).
collection do: [ :x | moview view add: (ROElement spriteOn:
x) + ROLabel + ROBox white ].
ROVerticalLineLayout on: moview view elements.
viewHack := moview view.
] ].
browser transmit
from: #list port:#selection;
to: #drawing;
transformed:
[ :x | | foundElements |
viewHack elements do: [ :el | ROUnhighlightElement on: el ].
targetElement := viewHack elements at: x.
ROFocusView on: targetElement.
ROHighlightElement on: targetElement color: Color red.
viewHack signalUpdate
].
browser openOn: #(1 2 3 4 5 6).
9 years, 9 months
Issue 942 in moose-technology: Fame-ImportExport - XML Export - transformation of \n and \t not working.
by moose-technology@googlecode.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 942 by v.blonde...(a)gmail.com: Fame-ImportExport - XML Export -
transformation of \n and \t not working.
http://code.google.com/p/moose-technology/issues/detail?id=942
In the class FMXMLPrinter of the Fame-ImportExport package, the
method 'primitive:' doesn't remplace the Character cr by \n and Character
tab by \t as expected in the source code. Indeed the affectation of the
local block variable by this line of code :
char = $n
doesn't work.
The result expected is :
'<?xml version="1.0"?>
<Document>
<Element name="FAMIX.Comment" id="1">
<Attribute name="content">
<String value="This is a test\"\n\t"/>
</Attribute>
</Element>
</Document>'
What we have actually :
'<?xml version="1.0"?>
<Document>
<Element name="FAMIX.Comment" id="1">
<Attribute name="content">
<String value="This is a test\"\
\ "/>
</Attribute>
</Element>
</Document>'
Platform : Win7, Pharo 2.0
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
9 years, 9 months
Issue 1018 in moose-technology: Message not understood Exception when asking for senders of some methods
by moose-technology@googlecode.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Critical Milestone-5.0
New issue 1018 by anne.et...(a)gmail.com: Message not understood Exception
when asking for senders of some methods
http://code.google.com/p/moose-technology/issues/detail?id=1018
Describe the problem: what do you get? what do you expect?
A message not understood exception occurs when asking for senders instead
the opening of a window with the list of senders.
How to reproduce the problem: step by step if necessary
Finding the senders of #+ works.
But finding the senders of #ifTrue: or #new or... does not work.
Additional information: platform, context which may impact the problem
The error comes from GRPackage that does not implement
#includesSelector:OfClassName:.
Only Magritte and Grease use GRPackage.
Please fill in the labels with the following information:
* Type-Defect
* Component-XXX
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
9 years, 9 months
slice for issue 989
by Anne Etien
Hello,
We create slice to manage exception in the MoosePanel request form (each beginWith: 'C'). We modified Glamour to correctly manage the exception and not launch the debugger when the message sent is not supported.
Doru, can you please have a look and integrate our change?
Thanks in advance,
Rafael, Gustavo, Guillaume and Anne.
9 years, 9 months
Issue 1036 in moose-technology: Ctrl + S and Alt + S haven't the same behaviour
by moose-technology@googlecode.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 1036 by v.blonde...(a)gmail.com: Ctrl + S and Alt + S haven't the
same behaviour
http://code.google.com/p/moose-technology/issues/detail?id=1036
Describe the problem: what do you get? what do you expect?
To save the modified source code in the debugger under Pharo3.0, we can
make Ctrl + S or Alt + S.
But with the latest version of Moose5.0. Alt + S save the source and move
the stack to the saved method. Ctrl + S only save the source.
How to reproduce the problem: step by step if necessary
Open a debugger, select an other method in the stack trace, modify it.
Try to save with Ctrl + S and do it again with Alt + S.
Additional information: platform, context which may impact the problem
Windows 7 x64 and Linux Ubuntu x64
Please fill in the labels with the following information:
* Type-Defect
* Component-GTDebugger
* Milestone-5.0
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
9 years, 10 months
Activity Diagram
by Serge Stinckwich
Dear all,
with a colleague from Savoie University, we are looking for some
Smalltalk code in order to model, execute and animate Activity
Diagram. Any existing works ?
Regards,
--
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/
9 years, 10 months