Hi all
I revert the stupid change I did to do not display Smalltalk for class.
I think that the renaming
moosePrintOn: to mooseNameOn: is really important because it conveys
that the moosePrintOn: is not about printing but naming the entity.
Stef
Begin forwarded message:
> From: François Tanguy <francois.tanguy(a)gmail.com>
> Date: May 10, 2009 10:46:36 AM CEDT
> To: pharo-project-request <Pharo-project(a)lists.gforge.inria.fr>
> Subject: [Pharo-project] The Fame code generator does not generate
> "container" annotation.
> Reply-To: Pharo-project(a)lists.gforge.inria.fr
>
> Hello all,
>
> The Fame code generator does not generate "container" annotation.
>
> ex : if in a MSE file
> (FM3.Property
> (id: 10051)
> (name ''superEquipment'')
> (type (ref: 5))
> (container true)
> (opposite (ref: 10061))
> )
>
> the code generated looks like this :
> superEquipment
> <MSEProperty: #superEquipment type: #SCAbstractEquipment
> opposite: #subEquipments>
> ^superEquipment
>
> should not it be like the following ?
> superEquipment
> <MSEProperty: #superEquipment type: #SCAbstractEquipment
> opposite: #subEquipments> <container>
> ^superEquipment
>
> It is pretty important because it allows the traversal of a model
> based on the containment of objects.
>
> François
> _______________________________________________
> Pharo-project mailing list
> Pharo-project(a)lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
Hi.
My questions:
1. If I only want to use EyeSee graphing tool for a project, what is the
minimal set of parcels I need to load and is there any specific setup?
2. I installed Moose off the repository by loading the MooseSetup
parcel; but when I try to run some of the EyeSee samples eg:
Examples>>lineDiagram (evaluate self new lineDiagram)
>>lineBarCompositeDiagramWithSameAxis
I get the error Message not understood: #width on a SmallInteger (each
width; where each is integer 3346) called from
setlabelDistanceFromAxisCalculation: aDiagram on ValueLabelDecorator
I get the same error from the image I also downloaded from the web site
(moose-suite-2008-11-25.zip).
Should I load a different version of parcels; or is there something
missing?
Thanks
Liliana
Hi guys
do we have a displayString in moose?
Because I'm fedup to see Smalltalk::Morph..... all the times
we have moosePrintOn: so I was in the mood to skip 'Smalltalk' when
the parent namespace is smalltalk.
Stef
There is a prelimary one I did some years ago to extract limited
information out of MC loaded code.
MSEExporter on SqueakSource.
Stef
On May 6, 2009, at 8:23 PM, Alexandre Bergel wrote:
> Dear All,
>
> Is there a Smalltalk -> MSE translator? Probably not since there is an
> importer. I am just wondering.
>
> Cheers,
> Alexandre
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project(a)lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
Hi,
I marked the MooseDevelopment 3.2.149.soulintegration as broken
because it has unloadable definitions.
With this occasion I looked at the code and I could not really
understand the changes. Especially adding a "version" instance
variable in FAMIXModelRoot does not sound right.
If this is something needed by SOUL, then you want to use the built-in
attribute dictionary:
self __state__ attributeGet: #YOUR_VAR default: VALUE
self __state__ attributeSet: #YOUR_VAR value: VALUE
Also, the code added in the constructor of EntityVersion makes
reference to an inexistent method (perhaps a SOUL method?):
aVersionEntity shouldStoreVersion ifTrue:[ aVersionEntity version:
version ].
Cheers,
Doru
--
www.tudorgirba.com
"Every now and then stop and ask yourself if the war you're fighting
is the right one."