Hi,
The Glamorous Toolkit, including the Glamorous Inspector, is now in the Moose image. There was a tiny problem of loading due the fact that SystemAnnouncements are already in the base image.
Cheers,
Doru
--
www.tudorgirba.com
"Be rather willing to give than demanding to get."
I've just downloaded moose-dev-4.7 and the first change i noticed was the
absence of a very useful feature in System browser: search bar. The change
comes from the move from pharo 1.3 to pharo 1.4. Sure, the same thing can
be done with ctrl + F but the search bar was much more easily accessible
and fewer windows in the system.
May be there is some custom browser that I can load to avoid changing my
habits.
regards,
usman
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 780 by fabrizio...(a)gmail.com: pairsDistanceFrom: should be
renamed since it is not a distance metric
http://code.google.com/p/moose-technology/issues/detail?id=780
The method SequenceableCollection>>pairsDistanceFrom: should be renamed
since it is not a distance metric.
What do you think of this PetitParser example? Is there a better way to do
this?
Parse a string like '{"login", "bash"}' (an Applescript list) into a
collection of items (i.e. #("login" "bash))...
| delimiter item contents listParser result listClose |
delimiter := ', ' asParser.
listClose := $} asParser.
item := (delimiter / listClose) negate plus flatten.
contents := (item separatedBy: delimiter) ==> [ :nodes | nodes reject: [ :n
| n = ', ' ] ].
listParser := ${ asParser, contents optional, listClose ==> #second.
result := listParser parse: returnString.
^ result isNil
ifTrue: [ OrderedCollection new ]
ifFalse: [ result collect: [ :e | self processAtom: e ] ].
Thanks.
Sean
--
View this message in context: http://forum.world.st/PetitParser-Example-tp4420008p4420008.html
Sent from the Moose mailing list archive at Nabble.com.
Hi,
Recently, I received all sorts of questions related to how to use Moose in practical settings. Many of the answers are provided on the humane assessment website. In particular, I am trying to update the blog continuously both with demos and with stories from the engineering trenches.
If you want to stay up to date register to the RSS feed:
http://www.humane-assessment.com/blog/?view=PBEntriesRssView
or follow the @humaneA on Twitter:
http://twitter.com/humaneA
And of course, I would be happy to answer more questions, and to hear more of your stories, too.
Cheers,
Doru
--
www.tudorgirba.com
"In a world where everything is moving ever faster,
one might have better chances to win by moving slower."
Hi,
I just wanted to let you know that the Glamour and Metanool (transformation engine between Fame and Magritte) are now using Magritte 3.
Consequently, in the latest Moose image you will find Magritte 3.
Cheers,
Doru
--
www.tudorgirba.com
Things happen when they happen,
not when you talk about them happening.
Hi all,
I have a meta-model implemented as a UML profile and i would like to
use this meta-model in MOOSE/Pharo.
Is there anyway to convert this meta-model in FM3 or i have to do it by hand ?
Regards,
--
Serge Stinckwich
UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam
Matsuno Laboratory, Kyoto University, Japan (until 12/2011)
http://www.mechatronics.me.kyoto-u.ac.jp/
Every DSL ends up being Smalltalk
http://doesnotunderstand.org/
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 778 by fabrizio...(a)gmail.com: FAMIXAssociation should not
implement sourceAnchor
http://code.google.com/p/moose-technology/issues/detail?id=778
FAMIXAssociation should not implement sourceAnchor.
Status: New
Owner: tudor.gi...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.7
New issue 779 by tudor.gi...(a)gmail.com: Glamour listing should update the
morph
http://code.google.com/p/moose-technology/issues/detail?id=779
The morphic rendering does not properly update the list in the morph tree
morph. This is due to changes in the morphtreemorph internal structure.