Hi
Apparently changes in Fame broke moose.
processCompiledMethod: aMethod
| pragma prop |
>>> aMethod should be isCompiledMethod.
pragma := Pragma
inMethod: aMethod
So what do we do?
Stef
Hi Cyrille,
I am trying to load your changes related to MooseWizard, but I get a
ListModel DNU packagesList:. Any idea what the problem is?
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow."
Hello everyone,
First of all, thanks for participating to the Glamour day.
Besides being fun, it was quite productive. You can find a small
report on the event page:
http://moose.unibe.ch/events/2009-11-06-glamour-day
Cheers,
Doru
--
www.tudorgirba.com
"Presenting is storytelling."
Hi Simon,
Please use the latest Momo.
The browseSource is on my to do list. It is not difficult, it just
needs to be done :). I will look into it.
Cheers,
Doru
On 6 Nov 2009, at 17:55, Simon Denier wrote:
> I cant launch the annotation browser or the flaw browser in latest
> Moose.
>
> MessageNotUnderstood: MorphTreeMorph>>on:list:multiSelection:
>
> Seems related to the previous bug with Momo, but I do have the Momo.
> 14 you point to.
>
>
> Also, do you think you can quickly enhance the browseSource method
> to launch a code browser on Java model?
>
>
> --
> Simon
>
>
>
--
www.tudorgirba.com
"Speaking louder won't make the point worthier."
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
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.euhttp://rmod.lille.inria.fr
---
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.euhttp://rmod.lille.inria.fr
---
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
>
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."
Hi,
The inFusion team just released version 7.2.5 of inFusion. Among
others, it has three features related to Moose:
- isPublic, isProtected, isPrivate parameters for method in FAMIX 3.0
exporter
- dialog for choosing the folder location when exporting
- fix for the error in exporting the name of a parameter in FAMIX 2.1
You can get it at:
http://www.intooitus.com/inFusion-tryit
Cheers,
Doru
--
www.tudorgirba.com
"Obvious things are difficult to teach."
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
Hi,
As you might know, Glamour received the 3rd prize at the ESUG
Innovation Awards. Together with the nice diploma, we also received a
200 EUR cash prize.
After long deliberations we decided to put this money back to some
good use and organize a Glamour Day on November 6:
http://moose.unibe.ch/events/2009-11-06-glamour-day
The event will be organized in the meeting room of SCG, starting from
10:00, and it will take the form of a sprint in which we can all enjoy
the glamorous glamour of Glamour.
The prize money will be used to provide (within the mentioned limit)
food and beverages.
Everyone is welcome. Just, please let us know if you plan to
participate.
Cheers,
The Glamorous Team
Hello,
The Moose Board is happy to invite the members of the Moose
Association to the general assembly.
The assembly will be held during the CHOOSE Forum on November 23,
2009, 12:40 (just after the CHOOSE General Assembly), at the Allegro
Grand Casino Kursaal in Bern.
The agenda is listed below. For further information, please contact
the board at:
moose-board(a)iam.unibe.ch
1. Anual report
- organized events (Moose Dojos and FAMOOSr)
- awards (ESUG Innovation Award for Glamour, CH Open Source Award
nomination for Moose)
- Moose 4.0 based on Pharo
- discussions with Cincom
2. Audit report
3. Elections
- Board: Orla Greevy, Stephane Ducasse, Michele Lanza, and Tudor Girba
are running for another mandate; also, there we have a new candidate:
Simon Denier
- Auditor: Klaus Witzel is running for another mandate
4. Varia
Kind regards,
The Moose Executive Board
Hi,
Perhaps some of you are interested in this event.
Cheers,
Doru
Begin forwarded message:
> From: Harald Gall <gall(a)ifi.uzh.ch>
> Date: 26 October 2009 22:56:24 GMT+01:00
> To: choose-news(a)iam.unibe.ch
> Cc: Harald Gall <gall(a)ifi.uzh.ch>
> Subject: [scg-staff] [Choose-news] CHOOSE Forum 2009: Human-centric
> software development, Nov 23, Bern
> Reply-To: scg-all(a)iam.unibe.ch, scg-staff(a)iam.unibe.ch
>
> Dear members of CHOOSE,
>
> We are pleased to invite you to the CHOOSE Forum 2009 to be held on
> November 23 at the Allegro Grand Casino Kursaal in Bern.
>
> The full day event consists of five talks and a panel on the topic of
> "Human-centric software development."
>
> The speakers are:
> - Prof. Arie van Deursen, Delft University of Technology
> - Prof. Jim Whitehead, University of California, Santa Cruz
> - Prof. Andrew Ko, University of Washington
> - Peter Stevens, Sierra Charlie Consulting
> - Dr. Tudor Gîrba, Sw-eng. Software Engineering GmbH
>
> The day also features the CHOOSE General Assembly, including reports
> from the President and the Treasurer.
>
> More details together with the registration form can be found on the
> official webpage:
> http://choose.s-i.ch/events/forum2009
>
> We hope to see many of you at the Forum!
>
> Kind regards,
> Harald Gall, Michele Lanza and Tudor Girba
>
>
> --
> CHOOSE News is a *moderated* mailing list for
> announcing non-commercial events related to
> Object Technology in Switzerland.
> To learn more about CHOOSE, see: http://www.choose.s-i.ch/
--
www.tudorgirba.com
"Relationships are of two kinds: those we choose and those that
happen. They both matter."
Hi!
There is a #generated method in some metaclasses of Mondrian. For
example:
MORectangleShape class>generated
^ #(( string '#asString' 'The string to be displayed.' )
( font 'TextStyle defaultFont' 'The font to be used.' )
( color 'Color black' 'The color of the text.' ))
The only sender of #generated is MethodPragmaTest
Is this really used? If not, is there a perpective of using this?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Dear All,
I adapted to Glamour what I did for Mondrian
You will find below the report. I tried to find a bottleneck, but
Glamour behaves linearly in all my tries. This is a good news
therefore :-)
The report has been generated by doit-ing:
GlamourousHealth new produceReport
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Report produced on 2009-10-23T16:33:00+00:00
Version a MCVersionInfo(GlamourLoader-tg.34)
------------------
Opening Browser Benchmark:
15 openings => 3622 ms
------------------
------------------
Selecting Item Benchmark:
100 size and selections => 709 ms
200 size and selections => 815 ms
300 size and selections => 895 ms
400 size and selections => 993 ms
500 size and selections => 1094 ms
600 size and selections => 1197 ms
700 size and selections => 1705 ms
800 size and selections => 1431 ms
900 size and selections => 1533 ms
1000 size and selections => 1639 ms
1500 size and selections => 2493 ms
2000 size and selections => 2729 ms
------------------
------------------
Selecting in finder item Benchmark:
1 size and selections => 26 ms
5 size and selections => 148 ms
10 size and selections => 328 ms
15 size and selections => 483 ms
20 size and selections => 636 ms
25 size and selections => 833 ms
30 size and selections => 999 ms
35 size and selections => 1289 ms
40 size and selections => 1483 ms
45 size and selections => 1700 ms
50 size and selections => 1881 ms
------------------
33.02 % of methods are covered
Progress from last time: 0.0 %
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
I also worked on a test coverage tool. Here is what I obtain for
Glamour.
Execute:
GlamourousHealth new viewTestCoverage
to have a mondrian rendering of the coverage. Inner light red boxes
are methods that are not directly or indirectly executed by unit
tests. Inner white boxes are methods executed when running the tests.
Outer boxes are classes. Edges designate superclass links.
Feedback are welcome
Cheers,
Alexandre
NB: You need to install www.squeaksource.com/Spy.html in order to get
the test coverage
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
I am happy to report that I ported SmallDude to Pharo. It is available
via:
Gofer new
squeaksource: 'SmallDude';
addPackage: 'ConfigurationOfSmallDude';
load.
(Smalltalk at: #ConfigurationOfSmallDude) perform: #loadDefault
All tests are green :).
Cheers,
Doru
--
www.tudorgirba.com
"Not knowing how to do something is not an argument for how it cannot
be done."
Hi,
I added a new DiffPresentation in Glamour based on the DiffMorph. You
can see an example of a Glamorous Diff Browser, by executing the
following in the latest Glamour:
GLMSmalltalkExamples new diffBrowser openOn: (
Collection withAllSubclasses asOrderedCollection sortBy: [:a :b | a
name < b name])
Cheers,
Doru
--
www.tudorgirba.com
"We cannot reach the flow of things unless we let go."
Hi,
I created new Metacello Configurations for Moose, Mondrian, Glamour
and DSM. They are in packages named by the scheme: ConfigurationOfXXX
To load it in the latest Pharo dev image, you should run:
Gofer new
squeaksource: 'Moose';
addPackage: 'ConfigurationOfMoose';
load.
(Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault
Cheers,
Doru
--
www.tudorgirba.com
"Be rather willing to give than demanding to get."
Hi!
I have been working on a "health report" of Mondrian. For now, it
essentially do some benchmarks for nodes, edges and provides an
estimation of the test coverage.
This is very early work for now. I am still experimenting. The
measurements below clearly show a problem: adding edges is definitely
too costly. I am currently working on this.
In the future, I would like identify speed bottleneck.
For now, it is only for Mondrian. Will people be interested in getting
similar data for Moose?
Cheers,
Alexandre
Report produced on 2009-10-20T16:00:26+00:00
Version 'Mondrian-Alexandre_Bergel.277'
Benchmark ManyNode (simple rendering of nodes) :
100 nodes => 14 ms
200 nodes => 50 ms
300 nodes => 108 ms
400 nodes => 198 ms
500 nodes => 335 ms
600 nodes => 442 ms
700 nodes => 627 ms
800 nodes => 768 ms
900 nodes => 969 ms
1000 nodes => 1223 ms
1600 nodes => 2907 ms
Benchmark ManyEdges (simple rendering of edges) :
10 edges => 1 ms
20 edges => 6 ms
30 edges => 14 ms
40 edges => 27 ms
50 edges => 52 ms
60 edges => 82 ms
70 edges => 126 ms
80 edges => 178 ms
90 edges => 364 ms
100 edges => 355 ms
200 edges => 4719 ms
300 edges => 36495 ms
Test coverage: 60.03 % of methods are covered
Progress from last time: 0.0 %
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.