Moose description mooseName printOn:
by Simon Denier
This morning, I tried to understand (I thought I understood before)
the things about printing Moose entities, either in the finder or in
an inspector, or whatever.
Only thing I can say is it's a mess with a lot of yo-yo in the
hierarchy.
So there is
MooseEntity>>description
MooseEntity>>mooseName
MooseEntity>>printOn:
also mooseNameOn: etc.
MooseGroup tends to use description.
mooseName is likely a unique identifier, however it is also used to
print an entity sometimes (in the moose finder)
#printOn: is not rationally overridden everywhere...
Maybe someone wants to take a look and proposes a solution, at least
some conventions/documentation.
Which selector is used in which context.
Which method should I override in a new entity.
--
Simon
14 years, 1 month
MooseLoader
by Laval Jannik
Hi all,
In a Pharo-Core, when I try to load Moose with:
---
Gofer new
squeaksource: 'Moose';
addPackage: 'ConfigurationOfMoose';
load.
(Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault.
---
There is a warning because of dependencies to OBCodeBrowser and
OBCommand.
I think we should integrate these packages in the loader or create
another loader for PharoCore or remove these dependencies.
Cheers
---
Jannik Laval
PhD Student - Rmod Team - INRIA
Certified Project Management Associate (IPMA)
http://www.jannik-laval.eu
http://rmod.lille.inria.fr
---
14 years, 1 month
mooseImporter 10 times faster
by Laval Jannik
Hi all,
I did a MessageTally on
MooseScript>>createModelForPharoOnlyPackageInCycle.
Result: 6613413 msec (110 minutes)
and most of time (80%) passed in FAMIXInvocation>>candidates:.
precisely in FMMultivalueLink>>unsafeAdd: because of
SequenceableCollection>>includes:
The parameter of candidates: is an OrderedCollection but it should not
contained duplicated entities.
So I do a method uncheckUnsafeAdd: which do not check if the entity is
included.
Tests which I made give the same number of entities that the older
importer.
But time is divided by 10: 654300 msec (11 minutes)
For MooseScript>>createModelForMoose
Result before: 73 seconds
Result after: 43 second
All tests pass,
I think we should test it on other models.
Cheers,
---
Jannik Laval
PhD Student - Rmod Team - INRIA
Certified Project Management Associate (IPMA)
http://www.jannik-laval.eu
http://rmod.lille.inria.fr
---
14 years, 1 month
Re: Moose-dev Digest, Vol 38, Issue 16
by Usman Bhatti
Thanx a lot for the quick help. I got stuck with the installation of VW and
Moose on my new machine.
I've got moose from this site:
http://moose.unibe.ch/download/vw
I am running the script provided by Doru with MOOSE.
| inh |
view nodes: classGroup.
view edgeShape: MOOrthoVerticalLineShape new.
inh := view edgesFrom: #superclass.
view treeLayout userDefinedEdges: inh.
view edges: classGroup from: #yourself toAll: #invokedClasses using:
(MOCurveFitterShape new color: Color red).
However, when I try to run the script on the LAN sample classes, Easel is
having difficulty in understanding these two constructs...
MOOrthoVerticalLineShape and MOCurveFitterShape...
I would like to mention here that I was having difficulty in downloading VW
so I downloaded Virtual machine and Required components from this site:
http://www.cincomsmalltalk.com/scripts/DownloadFiles.ssp
I'm surely missing something here but cannot figure it out.
And I am sure you people can help :-)
On Fri, Oct 30, 2009 at 5:42 PM, <moose-dev-request(a)iam.unibe.ch> wrote:
> Send Moose-dev mailing list submissions to
> moose-dev(a)iam.unibe.ch
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> or, via email, send a message with subject or body 'help' to
> moose-dev-request(a)iam.unibe.ch
>
> You can reach the person managing the list at
> moose-dev-owner(a)iam.unibe.ch
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Moose-dev digest..."
>
>
> Today's Topics:
>
> 1. Help needed with class hierarchy visualization (Usman Bhatti)
> 2. Re: Help needed with class hierarchy visualization (Tudor Girba)
> 3. Re: glamour day - november 6 (Simon Denier)
> 4. Re: Help needed with class hierarchy visualization (Simon Denier)
> 5. Re: Help needed with class hierarchy visualization
> (Alexandre Bergel)
> 6. Re: Help needed with class hierarchy visualization (Tudor Girba)
> 7. Re: Help needed with class hierarchy visualization (Tudor Girba)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 30 Oct 2009 15:05:17 +0500
> From: Usman Bhatti <usman.bhatti(a)gmail.com>
> Subject: [Moose-dev] Help needed with class hierarchy visualization
> To: moose-dev(a)iam.unibe.ch
> Message-ID:
> <716651510910300305x1db798b9p23634f3244b6a7d5(a)mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi all,
>
> I am looking to visualize my class hierarchy in moose in such a way that
> the
> method calls within classes is overlapped over the class hierarchy
> visualization.
>
> In addition to this, I am looking to filter the visualization results by
> specifying invoked methods so that my visualization does not get cluttered
> with all the method calls within the class hierarchy. Can I generate such a
> visualization with Moose?
>
> regards,
>
> Usman
>
14 years, 1 month
Re: publishing changes on glamour
by Tudor Girba
Hi Veronica,
Indeed, Momo has just changed dramatically because Alain was nice
enough to work on a proper multi-selection tree widget. I am now
working on adopting the rendering to work with these changes.
Cheers,
Doru
On 1 Nov 2009, at 21:15, Veronica Isabel Uquillas Gomez wrote:
> done...
>
> few changes to allow me the use of subclasses with my own formatting.
>
> btw, the last version of Momo removed a method that is used when
> rendering the trees...
>
> regards,
> Veronica
>
>
> On 01 Nov 2009, at 20:32, Tudor Girba wrote:
>
>> Hi Veronica,
>>
>> Please publish them and I will check the differences and give you
>> feedback.
>>
>> Cheers,
>> Doru
>>
>>
>> On 1 Nov 2009, at 20:17, Veronica Isabel Uquillas Gomez wrote:
>>
>>> Hello Tudor,
>>>
>>> On Monday I extended Glamour to include a diff browser, I just
>>> noticed you already did that on thursday night :(
>>> Well, the point is that i am using my own MorphicLibrary to
>>> include new elements to the tags (e.g. icons, icons + text).
>>>
>>> So i have some changes that i would like to include in the last
>>> version... Am i allowed to publish them? or should i send you the
>>> changes?
>>>
>>> Thanks,
>>> Veronica Uquillas
>>>
>>
>> --
>> www.tudorgirba.com
>>
>> "It's not what we do that matters most, it's how we do it."
>>
>
--
www.tudorgirba.com
"Being happy is a matter of choice."
14 years, 1 month
