Hi,
I put together a little implementation for traversals. It is inspired by an
original implementation from Mariano. Using DeepTraverser, you can traverse
arbitrary graphs by describing the traversal and by specifying the actions
you want to perform on the nodes and relations.
The code is available in the Moose image as part of the MooseAlgos
subproject, but can also be loaded separately in a Pharo image via:
Gofer new
url: 'http://www.smalltalkhub.com/mc/Moose/DeepTraverser/main';
package: ‘ConfigurationOfDeepTraverser’;
load.
(Smalltalk globals at: #ConfigurationOfDeepTraverser) loadDevelopment.
Just to give you an idea, here are some representative examples:
Number
deep: #subclasses
do: [:each | Transcript show: each; cr].
Number deepCollect: #subclasses.
Number
deep: #subclasses
collect: #name.
Number
deep: #subclasses
do: [:each | Transcript show: each; cr]
relationDo: [ :from :to | Transcript show: from; show: ' <-- '; show:
to; cr ].
More details about the usages and a little description of the
implementation can be found here:
http://www.humane-assessment.com/blog/traversal-enabled-pharo-objects/
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Hi everyone!
I want to display graphET diagrams in moose finder. All other diagram usages are based on Mondrian builder. Can someone help me to build diagrams with other builder?
Cheers.
Uko
Hi guys,
you will probably hate me after today, but I have one more question.
I’m trying to plot some data that is related to time. By default GraphET (and Roassal) do not support Date as value. Of course I can convert timestamp to seconds from epoch but maybe it would be cool to be able to use just Timestamp. For me it seems that evolution of some metric in time should be quite common.
Does anybody have intention to implement something like this?
Uko
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