- Moose-dev - INF Mailman

by Alexandre Bergel

Hi! Some improvement were made over the last few days (Thanks Henrik!). Here is the health report run on a 64/32 vm, 5.7b3. Compared with the report sent on August 11, we are significantly faster on simple rendering of edges (due to the fast node lookup scheme), rendering inner nodes (due to the fast node lookup scheme again) But a bit slower on rending simple nodes (27%), ManyInnerNodesAndEdges (3%), many small nodes. Report produced on 2010-09-14T10:26:51+00:00 System version Pharo-1.1-11411 of 17 July 2010 update 11411 Benchmark ManyNode (simple rendering of nodes) : 100 nodes => 6 ms 200 nodes => 11 ms 300 nodes => 16 ms 400 nodes => 21 ms 500 nodes => 28 ms 600 nodes => 32 ms 700 nodes => 36 ms 800 nodes => 42 ms 900 nodes => 48 ms 1000 nodes => 52 ms 1600 nodes => 84 ms 3200 nodes => 169 ms 6400 nodes => 485 ms Benchmark ManyEdges (simple rendering of edges) : 10 edges => 3 ms 20 edges => 7 ms 30 edges => 15 ms 40 edges => 26 ms 50 edges => 40 ms 60 edges => 56 ms 70 edges => 213 ms 80 edges => 99 ms 90 edges => 128 ms 100 edges => 273 ms 200 edges => 1120 ms 300 edges => 3538 ms Benchmark ManyInnerNodes : 5 nodes => 142 ms 10 nodes => 2754 ms 15 nodes => 9345 ms Benchmark Displaying ManyInnerNodes : 5 nodes => 193 ms 10 nodes => 888 ms 15 nodes => 10393 ms Benchmark Displaying ManyInnerNodesAndEdges : 1 nodes => 8 ms 2 nodes => 232 ms 3 nodes => 3328 ms 4 nodes => 34497 ms Benchmark Displaying elementAt : 100 nodes => 4 ms 500 nodes => 6 ms 1000 nodes => 9 ms 1500 nodes => 12 ms 2000 nodes => 15 ms 2500 nodes => 18 ms Benchmark many small nodes : 2000 nodes => 3328 ms Benchmark edges bounds : 500 nodes => 134 ms Benchmark subnodes lookup : 20000 nodes => 3896 ms -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

14 years, 9 months

1
0
0 0

Mondrian display issue

by Laval Jannik

Hi Alex, I have a problem with Mondrian (last version). Text are cut when displayed. I see only the top of the text. You can reproduce it with: ===== (view shape: (MOFixedRectangleShape new width: 180; height: 180; text: [:entity | entity asString]; withBorder; borderColor: Color gray)). view nodes: #(blah blaf blag) ====== Cheers, --- Jannik Laval

14 years, 9 months

4
9
0 0

FAMOOSr Proceedings Online

by Mircea Lungu

Hi guys, You can now find the proceedings of this year's FAMOOSr online at: http://www.moosetechnology.org/events/famoosr2010#proceedings You can look at the papers and even if you will not be physically present there, you can send us questions that we could ask the presenters during the workshop. Cheers, Mircea and Simon.

14 years, 9 months

1
0
0 0

Major speedup of node lookup

by Alexandre Bergel

Hi! After a short session of pair programming with Henrik, we found places where node lookup can be severally optimized. As a result, blueprint complexity opens on 509 classes in 72 seconds. I know that some issues are still open related to node lookup (lazy edges and http://code.google.com/p/moose-technology/issues/detail?id=400). I will work on them... Thanks Henrik! Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

14 years, 9 months

2
1
0 0

Re: Visual Basic / VB.Net parsers

by Alberto Bacchelli

On 9/9/10 6:13 PM, alberto.bacchelli(a)usi.ch wrote: > On 9/9/10 6:09 PM, Alexandre Bergel wrote: >> Let us know how it goes Alberto >> >> A good test for your work may be to parse the whole JDK. I did a similar experiment a few years ago. I used Smacc. I had to manually modify some files because the java parser in the Java compiler is written by hand. And it permits things that are not expressed in the grammar. For example: >> >> class Foo {} ; >> >> is accepted by the Java compiler, but it is hardly accessed by most grammars. > > Yes, the Java Language Specifications are very very very badly written. > The book is full of errors and does not consider some cases, as > you also reported. > For this reason, I based my porting on the grammar written for > ANTLR: it passes all the regression tests that the hand-written > compiler passes. "It" is referring to the ANTLR grammar, not to PetitJava (yet ;)

14 years, 10 months

1
0
0 0

Re: Visual Basic / VB.Net parsers

by Alberto Bacchelli

On 9/9/10 6:09 PM, Alexandre Bergel wrote: > Let us know how it goes Alberto > > A good test for your work may be to parse the whole JDK. I did a similar experiment a few years ago. I used Smacc. I had to manually modify some files because the java parser in the Java compiler is written by hand. And it permits things that are not expressed in the grammar. For example: > > class Foo {} ; > > is accepted by the Java compiler, but it is hardly accessed by most grammars. Yes, the Java Language Specifications are very very very badly written. The book is full of errors and does not consider some cases, as you also reported. For this reason, I based my porting on the grammar written for ANTLR: it passes all the regression tests that the hand-written compiler passes. If anyone wants to have a look, you can find petitjava on squeaksource. Alberto

14 years, 10 months

1
0
0 0

Re: Visual Basic / VB.Net parsers

by Alberto Bacchelli

On 9/9/10 4:45 PM, Fabrizio Perin wrote: > Hi, > i'm soo sorry but it is not a secret/encrypted message. The idea was to send a mail to Mircea picking up its email address from the mail about VB and this is the result :) > > Really sorry for the spam! > > By the way as far as i know there is nothing for VB in Moose but recently i got quite impressed from the power of petit parser. I think that would be possible to setup a basic VB parser with Petit Parser in a week. I don't think it will be as easy as it seems. PetitParser is great and simplifies a lot your life. The problem is finding a reliable VB grammar to implement, and creating the AST from the grammar. I am working (although with a certain discontinuity) on PetitJava and it is taking much time. Alberto

14 years, 10 months

2
1
0 0

Visual Basic / VB.Net parsers

by Mircea Lungu

Is there a parser for these languages? Thanks, M. -- Mircea Lungu Researcher Software Composition Group University of Bern http://lungu.org/mircea

14 years, 10 months

4
5
0 0

Friday the 17th: first collabor'active Moose Dojo?

by Simon Denier

Famoosr happens on Friday the 17th, same time as Esug. In particular, a "bazaar session" (I like the name, thanks Mircea :)) is planned at the end of the workshop, which means pair programming and hacking tools. Now, I would not be there because I will be at Esug, but one thing has been on my mind lately: why not try some kind of distributed hacking session between Esug and Famoosr? Not for everybody, just a small experiment with one pair on both sites. I think that Lukas did such a thing in the past to help some clients with Seaside. What do you say? -- Simon

14 years, 10 months

4
5
0 0

3 mondrian canvas tests failing

by Tudor Girba

Hi, There are 3 tests that fail. It looks like they fail because of the same assertion: self assert: v = (742@351). where v is actually 742@350. Alex, any ideas? Cheers, Doru -- www.tudorgirba.com "To lead is not to demand things, it is to make them happen."

14 years, 10 months

1
0
0 0

New version of Mondrian

by Alexandre Bergel

Hi! In the last version of Mondrian, all tests are green. In addition, I made a number of refactorings. If your code is broken and you can't update, just shout. The classes MOFigureDeselection and MOFigureSelection have been renamed into MOElementDeselection and MOElementSelection respectively MondrianPaintings and Glamour-Tests-Morphic have been updated accordingly. Something that might make happy some of you. You can now select more than one node. Very handy when dragging and dropping. Just use the Cmd key. Version 560: fixed the remaining bug of Formsshape. all tests are green Version 561: Selection multiple of elements. Group of multi-nodes be drag-and-dropped. Use the command key to select more than one Version 562: Selection box. click in the background to select several elements Version 563: merged with tg.560 Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

14 years, 10 months

3
3
0 0

MOFormsShape and friends

by Alexandre Bergel

Hi! I would like to remove the class MOFormsAdaptor, MOFigureAdaptor and MOShapeAdaptor since they are not necessary (the implementation I did do not use them). I will do the refactoring in one week time, this leaves some time for you to test formsshapes (which is used by UML Shape). This will remove some #flag: sender. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

14 years, 10 months

1
0
0 0

broken tests

by Tudor Girba

Hi, There are 6 broken tests in DSM, CategoryImporter, and Mondrian: http://hudson.moosetechnology.org/job/moose-latest-dev/lastCompletedBuild/t… Could we please fix these? Doru -- www.tudorgirba.com "Presenting is storytelling."

14 years, 10 months

4
9
0 0

Redirect compiler warnings to file

by Simon Denier

Hi When loading large chunks of code (like Moose), some warnings appear in the Transcript. The problem is the Transcript has a limited size and that with all information dumped into, the first one get lost before we can take a look at them. Does anyone know a way to capture/redirect the Transcript output to a file, or the output from Compiler (maybe using the requestor parameter?) -- Simon

14 years, 10 months

2
2
0 0

glamorous theme :)

by Tudor Girba

Hi, Over the past week I worked on a new theme for Pharo called the Glamorous Theme :). The theme is developed in the context of the Glamour project, and its goal is to create a look that: - does not look like a specific operating system. In particular, the icons should be operating system agnostic, because, for example, people in Windows are confused by the red, yellow, green buttons of apple. - uses a limited amount of colors and effects. It is still work in progress, but you can get the current version by executing: Gofer new squeaksource: 'Glamour'; package: 'Glamour-Morphic-Theme'; load. GLMUITheme defaultSettings: nil. GLMUITheme beCurrent. GLMUITheme setPreferredWorldBackground. Cheers, Doru -- www.tudorgirba.com "Problem solving efficiency grows with the abstractness level of problem understanding."

14 years, 10 months

3
3
0 0

"MooseModel reinitializeMetaTower" raises an error

by Alexandre Bergel

Hi! "MooseModel reinitializeMetaTower" raises an error in the Hudson image (downloaded a few days ago). This error prevents CAnalyzer to run. http://code.google.com/p/moose-technology/issues/detail?id=451 Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

14 years, 10 months

2
4
0 0

Obtaining the version of Moose that I am using

by Alexandre Bergel

Hi! I just entered a new issue (http://code.google.com/p/moose-technology/issues/detail?id=451), but I wasn't able to say which version of Moose I am using. Is there a way to obtain this info? I was thinking about: ConfigurationOfMoose defaultVersion => <>default [ConfigurationOfMoose] Not really helpful ConfigurationOfMoose project lastVersion => >=4.0.14 [ConfigurationOfMoose] But is 4.0.14 the same than default? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

14 years, 10 months

2
5
0 0

Famix-ManifestMf?

by Simon Denier

I noticed a new package Famix-ManifestMf in the Moose config, but I can't figure what it is used for? -- Simon

14 years, 10 months

3
3
0 0

[Glamour] GLMDiffPresentation seems to no longer work

by Cyrille Delaunay

Open the moose panel. Browse a small model. on 'all famixClasses', rigth click and click on Utilities >> Compute duplication. Now, from 'all dudemultiplications', browse 'constellation'. In the browser, when clicking on a multiplication, opening the GLMDiffPresentation raise an error: Message not understood: GLMDiffPresentation >> allowsDeselection. http://code.google.com/p/moose-technology/issues/list?thanks=449&ts=1283506…

14 years, 10 months

2
1
0 0

FAME, some examples?

by Alberto Bacchelli

Hi, Other than reading the paper FAME—A Polyglot Library for Metamodeling at Runtime*, where can I find some *simple* examples/tutorials on how to deal with FAME? Thank you. Cheers, Alberto

14 years, 10 months

3
3
0 0

FAMIX Java, Exceptions, invoked/invoking methods

by Felipe Ignacio Valverde Campos

Hi, how can i get the invoked methods into the try{...}/catch{...} ? and LOC, attributes, etc... from those codes thanks!

14 years, 10 months

6
12
0 0

proposing moose to the esug awards

by Stéphane Ducasse

Simon why not proposing Moose to the ESUG award? Stef

14 years, 10 months

1
0
0 0

Mondrian new "feature or bug" ?

by Laval Jannik

When I do a MOFixedRectangleShape, I want the rectangle does not grown with its content. I try to zoom on a DSM, then I have strange thing: fixedRectangle are really fixed -> they do not zoom. It cause some problems in my visaulization (see screenshot) This is before zooming: After zooming: You can reproduce the issue easily: === view shape: (MOFixedRectangleShape new width: 25; height: 25; withBorder; borderColor: Color gray). view nodes:#(1 2 3). === Cheers, --- Jannik Laval

14 years, 10 months

2
4
0 0

Re: [Pharo-project] Re: load moose in Pharo1.2

by Tudor Girba

I was more considering the issue from a transitory point of view. But, indeed, given that 1.1 is out, there is no point in being backward compatible anymore. Cheers, Doru On 2 Sep 2010, at 16:51, Guillermo Polito wrote: > But, that's why we have metacello configs? don't we? We have to use > a specific version for 1.1 and another one for 1.2. > > If we want to download the lastVersion always, It's not going to > work never :). > > On Thu, Sep 2, 2010 at 11:46 AM, Tudor Girba <tudor.girba(a)gmail.com> > wrote: > No, because if you remove it you break 1.1. I would suggest to just > rename those variables. > > Cheers, > Doru > > > > On 2 Sep 2010, at 16:43, Cyrille Delaunay wrote: > > There is already an issue for that: > > http://code.google.com/p/pharo/issues/detail?id=2734&q=PluggableShoutMorph&… > > Should we (I) remove those variables from PluggableShoutMorph? > > 2010/9/2 Cyrille Delaunay <cy.delaunay(a)gmail.com> > Now I have exactly the same problem with 'PluggableShoutMorph' in > the package Shout (This package is loaded with > ConfigurationOfPetitParser). PluggableShoutMorph (like > MOEaselTextEditor) declare the two instance variables 'styler' and > 'unstyledAcceptText' which are already declared in the superclass > PluggableTextMorph (in Pharo 1.2). Maybe those variable have been > integrated in the superclass for pharo 1.2 and are no longer > usefull ? Anyone know? > > 2010/9/2 Alexandre Bergel <alexandre(a)bergel.eu> > > Strange indeed. This method is apparently never called. This is > related somehow to the completion (which does not work for me. I > will contact Lukas). > > Alexandre > > > On 2 Sep 2010, at 08:22, Cyrille Delaunay wrote: > > > What is strange, is that there is only one reference to > unstyledAcceptText, without affecting it a value. > > > > 2010/9/2 Cyrille Delaunay <cy.delaunay(a)gmail.com> > > No, same problem now with 'unstyledAcceptText' > > > > > > 2010/9/2 Tudor Girba <tudor.girba(a)gmail.com> > > And does the loading work now? > > > > Doru > > > > > > On 2 Sep 2010, at 13:08, Cyrille Delaunay wrote: > > > > done > > > > 2010/9/2 Tudor Girba <tudor.girba(a)gmail.com> > > Yes, please rename it to shoutStyler. > > > > Cheers, > > Doru > > > > > > > > On 2 Sep 2010, at 12:25, Cyrille Delaunay wrote: > > > > So that means that a 'styler' instance variable has been defined > in PluggableTextMorph between pharo 1.1 and Pharo 1.2? Should we > rename the Mondrian instance variable? > > > > 2010/9/2 Cyrille Delaunay <cy.delaunay(a)gmail.com> > > So a solution is to load in a version of OmniBrowser that is > compatible with 1.2, before loading moose: > > > > (ConfigurationOfOmniBrowser project version: '1.1-baseline') load. > > > > Now, I have another error: > > The class MOEaselTextEditor from Mondrian-Easel re-declare the > instance variable 'styler', which is already defined in its > superclass PluggableTextMorph. > > > > 2010/9/1 Lukas Renggli <renggli(a)gmail.com> > > > > Metacello is loading an ancient version of OB. References to > > Preferences have been removed a long time ago. However there is > still > > a problem with the highlighting in Pharo 1.2. You only get a working > > environment if you do not load the package OB-Shout. > > > > Lukas > > > > On 1 September 2010 16:10, Tudor Girba <tudor.girba(a)gmail.com> > wrote: > > > Hi Cyrille, > > > > > > That means that OB needs to be fixed :). Could you raise the > issue on the > > > pharo mailing list? > > > > > > Cheers, > > > Doru > > > > > > > > > On 1 Sep 2010, at 14:48, Cyrille Delaunay wrote: > > > > > >> When I try with the configuration, I get an error when loading > the class > > >> OBMercuryPanel (from the package OB-Standard, that seems to be > loaded with > > >> ConfigurationOfMetacello): > > >> The initialize method is using the old class > "Preferences" (that is no > > >> longer present in Pharo 1.2). > > >> > > >> 2010/9/1 Tudor Girba <tudor.girba(a)gmail.com> > > >> What do you mean by script? Did you try with the configuration? > > >> > > >> Doru > > >> > > >> > > >> > > >> On Sep 1, 2010, at 11:12, Cyrille Delaunay > <cy.delaunay(a)gmail.com> wrote: > > >> > > >> > Hello, > > >> > Is moose loadable in Pharo 1.2 ? Is there a special script > somwhere to > > >> > that? > > >> > _______________________________________________ > > >> > Moose-dev mailing list > > >> > Moose-dev(a)iam.unibe.ch > > >> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > >> > > >> _______________________________________________ > > >> Moose-dev mailing list > > >> Moose-dev(a)iam.unibe.ch > > >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > >> > > >> _______________________________________________ > > >> Moose-dev mailing list > > >> Moose-dev(a)iam.unibe.ch > > >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > > -- > > > www.tudorgirba.com > > > > > > "When people care, great things can happen." > > > > > > > > > > > > _______________________________________________ > > > Moose-dev mailing list > > > Moose-dev(a)iam.unibe.ch > > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > > > > > > > -- > > Lukas Renggli > > www.lukas-renggli.ch > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)iam.unibe.ch > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)iam.unibe.ch > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > -- > > www.tudorgirba.com > > > > "When people care, great things can happen." > > > > > > > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)iam.unibe.ch > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)iam.unibe.ch > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > -- > > www.tudorgirba.com > > > > "Being happy is a matter of choice." > > > > > > > > > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)iam.unibe.ch > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)iam.unibe.ch > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > www.tudorgirba.com > > "If you interrupt the barber while he is cutting your hair, > you will end up with a messy haircut." > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "When people care, great things can happen."

14 years, 10 months

2
1
0 0

[Mondrian] Edges zoom problems

by Felipe Ignacio Valverde Campos

hi! On MOEasel using 'zoom in' button [repeatedly] for basic/Dashed edges example, moves the edges to unrepresentative positions http://code.google.com/p/moose-technology/issues/detail?id=447

14 years, 10 months

2
4
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev