Hi guys!
I want to ask everyone who is developing something important for Roassal-related projects to include your example in easel. For now on there is only some Mondrian and Roassal’s examples. Also Roberto’s tree map builder examples appear when roassal-extras are loaded.
For example GraphET has a lot of examples, but they are not integrated into easel and so it’s not easy to view them. So please, spend a bit more time to make your examples available in roassal easel and so making it easier for others to use your project.
Also my rectangle packing layout example were not transferred to Roassal, can someone please handle that?
Cheers.
Uko
hello,
i just want to report a crash of moose on the OS Windows XP
there the error message :
Sorry but the VM crashed
Exception Code : C0000005
Exception address : 66E4B46D
Current Byte Code : -1
Primitive Index : 117
Crashed in the VM thread
--
View this message in context: http://forum.world.st/crash-of-moose-WinXP-tp4729306.html
Sent from the Moose mailing list archive at Nabble.com.
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 1028 by chisvasi...(a)gmail.com: the transformation block is not
called correctly
http://code.google.com/p/moose-technology/issues/detail?id=1028
When using a transmission with a transformation block, the transformation
block is not called when creating the presentations. The code bellow will
show a list from 1 to 10 instead of one from 1 to 20:
browser := GLMTabulator new.
browser row: #row.
browser transmit
to: #row;
transformed: [ :anInt | anInt+10 ];
andShow: [ :aComposite :anInt |
aComposite list
display: [ 1 to: anInt ] ].
browser openOn: 10.
The transformation block is only called when populating the port, which
happens after the presentation was created.
This can be fixed by modifying GLMPresentStrategy>>presentations to use the
transformation, but the the block will be called two times.
--
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
I notice that several builds are green, though I added a breaking test to Pharo 3.
That probably means that those builds don't run all of the Pharo tests.
Most builds probably don't need to run all tests (all the time), but it might be
useful to be able to mark tests as integration tests, that are expected to be
run by all downstream builds.
Concrete, every Pharo 3 build that loads Grease should currently be red.
Stephan
Hi guys
I would like to present moose to the students at Prague and I wonder if there are
Moose presentations around. I have some but they are too marketing oriented :)
Usman the ones you did for RIC are the best I have so far.
Stef
Hi,
It seems that lately, the energy equilibrium on this mailing list got
slightly off balance. When most messages get negative, you easily get to
feel down and this gets to show in your work. To bring back the positive
energy, I kindly ask you for a simple thing:
Find one thing you like about Moose, and post as a reply to this message.
The reply can be as succinct or as elaborate as you want. You can even
write a blog post about it. And be specific. Pick something you really like
and let the world know.
And remember this: in an open-source environment, people that appreciate
the work or others have more chances of being served.
Let's see where we are :).
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
baseline17: spec
<version: '0.7-baseline'>
spec for: #'common' do: [
spec blessing: #'baseline'.
spec description: ''.
spec author: 'AlexandreBergel'.
spec timestamp: '9/11/2013 23:34'.
spec repository: 'http://www.smalltalkhub.com/mc/ObjectProfile/Roassal/main'.
spec
package: #Roassal;
package: #RoassalMorphic;
package: #RoassalExtras;
package: #RoassalAthens.
the dependencies between packages are missing.
I really do not like that after I spent 3 days fixing Moose dependencies.
Each project should be clean.
Stef
Hi guys
here at prague we tried to load
- fame
- roassal in Pharo 30
and either the configurations were not published in the right
metarepository or it was not working.
For example roassal configuration loaded from repo 20 did not
work in 3.0 (colorNames problems).
So could you publish configurations that works on 30?
Stef
Hey,
please, pretty please, write class comments. Right now I’m trying to understand how GraphET works and there no class is commented. So I have GETAbstractLineDiagram and 2 subclasses: GETLineDiagram and GETOrdinaryLineDiagram. A I’ve mentioned there are no comments. So I’m wandering what do this classes do. Where is GETUnordinaryLineDiagram or GETExtraordinaryLineDiagram. Is it GETLineDiagram? Is line ordinary or is it a diagram? Of course this are all jokes. But my message is: buy spending only a couple of minutes pet class, you can help a lot of there developers. I’d really appreciate this effort.
Cheers!
Uko