Roassal and Moose: the plan - Moose-dev

Stéphane Ducasse

17 May 17 May

3:05 p.m.

Excellent! Tx alex. Do you have a plan for a chapter :) Stef On May 17, 2012, at 2:48 PM, Alexandre Bergel wrote:

Hi! The release of Roassal is now official. As you might have seen, Roassal is now distributed with Moose. The plan is to slowly replace Mondrian by Roassal. This may take some time, but we will reach the point that Mondrian can rest in peace. Roassal remains largely compatible with Mondrian. The visualizations you have scripted with Mondrian should normally work with Roassal without too much pain. Gofer new squeaksource: 'Roassal'; package: 'ConfigurationOfRoassal'; load. (Smalltalk at: #ConfigurationOfRoassal) project lastVersion load. Having Roassal out implies that I will essentially focus on Roassal instead of Mondrian. Naturally, I will continue to incorporate important bug fixes in Mondrian. But as far I am concerned, no major enhancement of Mondrian is planned. We learnt a lot with Mondrian. Roassal really goes one step further with better interactions, a clean low level if you wish to build your own domain specific language. To be short, Roassal is simpler and better. I suggest people to enter bug fixes and requests for enhancement in the Moose google project as we are doing for Mondrian. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: 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

Reply

Alexandre Bergel

3:49 p.m.

This is fixed. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On May 17, 2012, at 9:08 AM, Stéphane Ducasse wrote:

...

Alex roValue: is defined on BlockContext but BlockContext is deprecated since the introduction of closures. On May 17, 2012, at 2:48 PM, Alexandre Bergel wrote:

Hi! The release of Roassal is now official. As you might have seen, Roassal is now distributed with Moose. The plan is to slowly replace Mondrian by Roassal. This may take some time, but we will reach the point that Mondrian can rest in peace. Roassal remains largely compatible with Mondrian. The visualizations you have scripted with Mondrian should normally work with Roassal without too much pain. Gofer new squeaksource: 'Roassal'; package: 'ConfigurationOfRoassal'; load. (Smalltalk at: #ConfigurationOfRoassal) project lastVersion load. Having Roassal out implies that I will essentially focus on Roassal instead of Mondrian. Naturally, I will continue to incorporate important bug fixes in Mondrian. But as far I am concerned, no major enhancement of Mondrian is planned. We learnt a lot with Mondrian. Roassal really goes one step further with better interactions, a clean low level if you wish to build your own domain specific language. To be short, Roassal is simpler and better. I suggest people to enter bug fixes and requests for enhancement in the Moose google project as we are doing for Mondrian. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: 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

Reply

Tudor Girba

8:16 p.m.

Hi, Roassal does not depend on Mondrian :). I guess that you are referring to ROMondrianViewBuilder. This is nothing but a facade that makes it possible to use the Mondrian "DSL" to run on Roassal. It is not quite complete, but it's quite advanced. The idea is to ease the transition by simply switching the underlying engines without necessarily altering the scripts. Cheers, Doru On 17 May 2012, at 15:10, Stéphane Ducasse wrote:

...

More feedback Why Roassal is referencing Mondrian? I would like to load it in Pharo20 without mondrian. I would really like also that people start to use SmallLint and the manifest support we built. Loading 0.161 of ConfigurationOfRoassal... Fetched -> Roassal-AlexandreBergel.174 --- http://www.squeaksource.com/Roassal --- http://www.squeaksource.com/Roassal Fetched -> RoassalMorphic-AlexandreBergel.28 --- http://www.squeaksource.com/Roassal --- http://www.squeaksource.com/Roassal ROForceBasedLayout>>doExecute: (MORadialTreeLayout is Undeclared) ROMondrianViewBuilder>>forNode:whenEnteringUpdateNode:whenLeavingUpdateNode:withLayoutUpdate: (MOMouseEnter is Undeclared) ROMondrianViewBuilder>>forNode:whenEnteringUpdateNode:whenLeavingUpdateNode:withLayoutUpdate: (MOMouseLeave is Undeclared) ROMondrianViewBuilderTest>>testDefaultTitle(window is shadowed) ROMondrianViewBuilderTest>>testTitle(window is shadowed) Loaded -> Roassal-AlexandreBergel.174 --- http://www.squeaksource.com/Roassal --- cache ROBitmapGenerationTest>>testContainingElementDragging(node1 is shadowed) ROBitmapGenerationTest>>testContainingElementDragging(node2 is shadowed) ROBitmapGenerationTest>>testContainingElementRenderingSimple(node1 is shadowed) ROBitmapGenerationTest>>testContainingElementRenderingSimple(node2 is shadowed) ROBitmapGenerationTest>>testLabelRendering(view is shadowed) ROBitmapGenerationTest>>testViewRendering(node1 is shadowed) ROBitmapGenerationTest>>testViewRendering(node2 is shadowed) ROBitmapGenerationTest>>testViewRendering(view is shadowed) ROMorphTest>>testClickingScenario(event is shadowed) ROExporter>>toVW (VW5PackageExporter is Undeclared) Loaded -> RoassalMorphic-AlexandreBergel.28 --- http://www.squeaksource.com/Roassal --- cache _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- www.tudorgirba.com "To lead is not to demand things, it is to make them happen."

Reply

Tudor Girba

10:22 p.m.

Indeed, this was a problem. Doru On 17 May 2012, at 22:07, Stéphane Ducasse wrote:

...

doru

> (MORadialTreeLayout is Undeclared)

ROExporter>>toVW (VW5PackageExporter is Undeclared)

(MOMouseEnter is Undeclared)

(MOMouseLeave is Undeclared)

I thought MO meant Mondrian. Stef _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- www.tudorgirba.com "To lead is not to demand things, it is to make them happen."

Reply

Stéphane Ducasse

10:19 p.m.

excellent. We really want to check roassal. Stef On May 17, 2012, at 8:24 PM, Alexandre Bergel wrote:

...

This is due to some left over. Thanks Stef, I will work on them Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On May 17, 2012, at 9:10 AM, Stéphane Ducasse wrote:

More feedback Why Roassal is referencing Mondrian? I would like to load it in Pharo20 without mondrian. I would really like also that people start to use SmallLint and the manifest support we built. Loading 0.161 of ConfigurationOfRoassal... Fetched -> Roassal-AlexandreBergel.174 --- http://www.squeaksource.com/Roassal --- http://www.squeaksource.com/Roassal Fetched -> RoassalMorphic-AlexandreBergel.28 --- http://www.squeaksource.com/Roassal --- http://www.squeaksource.com/Roassal ROForceBasedLayout>>doExecute: (MORadialTreeLayout is Undeclared) ROMondrianViewBuilder>>forNode:whenEnteringUpdateNode:whenLeavingUpdateNode:withLayoutUpdate: (MOMouseEnter is Undeclared) ROMondrianViewBuilder>>forNode:whenEnteringUpdateNode:whenLeavingUpdateNode:withLayoutUpdate: (MOMouseLeave is Undeclared) ROMondrianViewBuilderTest>>testDefaultTitle(window is shadowed) ROMondrianViewBuilderTest>>testTitle(window is shadowed) Loaded -> Roassal-AlexandreBergel.174 --- http://www.squeaksource.com/Roassal --- cache ROBitmapGenerationTest>>testContainingElementDragging(node1 is shadowed) ROBitmapGenerationTest>>testContainingElementDragging(node2 is shadowed) ROBitmapGenerationTest>>testContainingElementRenderingSimple(node1 is shadowed) ROBitmapGenerationTest>>testContainingElementRenderingSimple(node2 is shadowed) ROBitmapGenerationTest>>testLabelRendering(view is shadowed) ROBitmapGenerationTest>>testViewRendering(node1 is shadowed) ROBitmapGenerationTest>>testViewRendering(node2 is shadowed) ROBitmapGenerationTest>>testViewRendering(view is shadowed) ROMorphTest>>testClickingScenario(event is shadowed) ROExporter>>toVW (VW5PackageExporter is Undeclared) Loaded -> RoassalMorphic-AlexandreBergel.28 --- http://www.squeaksource.com/Roassal --- cache _______________________________________________ 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

Reply

Stéphane Ducasse

10:04 a.m.

...

I would really like also that people start to use SmallLint and the manifest support we built.

Which tool? I am not aware of it. Nautilus does not seem to support SmallLint… How can I have SmallLint?

This is more than smallLint this is metadata handling so that we do not have to always see the same false positive. Stef Hi pharoers Since a couple of months the Pharo team has been working on improving the support for rules checking and in particular the handling of false positives (there is nothing more boring that to get all the time the same warnings that we know are not adequate). We added a manifest mechanism to manage the false/true positive of SmallLint, the rule checker of Pharo. A manifest is a class that contains meta data. In the future we may add package license and package documentation. This data is stored in methods on the meta side of the class. So, manifest can be versioned in Monticello and not lost. There is one manifest per package. It possible to use SmallLint with Manifest using the Critics Browser (menuWorld > Tool > CriticBrowser). With the Critics browser you can inspect violations of rules and mark them as false positive or true positive (ToDo) and see previous warnings flagged as false positives or toDo. In addition all the logic of the browser has been developed so that the manifest can be saved within the package without adding dependencies. We will continue to improve the Browser. In addition we will run SmallLint rules to all the Pharo packages and the rules checking will be part of the package validation. We want the community to use rule checking for real so that we all improve. Simon and Stef Gofer new url: 'http://www.squeaksource.com/PharoTaskForces'; package: 'ConfigurationOfManifest'; load. ((Smalltalk at: #ConfigurationOfManifest) project version: #stable) load

Reply

Stéphane Ducasse

11:33 a.m.

On Jun 17, 2012, at 10:27 AM, Ben Coman wrote:

...

Stéphane Ducasse wrote:

More feedback Why Roassal is referencing Mondrian? I would like to load it in Pharo20 without mondrian. I would really like also that people start to use SmallLint and the manifest support we built.

Steph, How do I find out about using SmallLint ? All the google results refer to SmallInteger only.

Look for the email in pharo from simon allier about Manifest Stef (running to buy vegetables before it is too late)

...

cheers -ben _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Reply

Tudor Girba

17 May 17 May

8:14 p.m.

Thanks, Alex! And thanks for releasing, too :). I am very happy that this part of Moose got traction again. I hope to get more in the future. Roassal is already integrated with Glamour (and it even has an Easel now), and thus it loads in Moose. The key now would be to focus on removing all dependencies from Mondrian to stress the new engine. There are still rough edges in Roassal, but if we focus on it I am sure we can enhance it significantly. Cheers, Doru On 17 May 2012, at 14:48, Alexandre Bergel wrote:

...

Hi! The release of Roassal is now official. As you might have seen, Roassal is now distributed with Moose. The plan is to slowly replace Mondrian by Roassal. This may take some time, but we will reach the point that Mondrian can rest in peace. Roassal remains largely compatible with Mondrian. The visualizations you have scripted with Mondrian should normally work with Roassal without too much pain. Gofer new squeaksource: 'Roassal'; package: 'ConfigurationOfRoassal'; load. (Smalltalk at: #ConfigurationOfRoassal) project lastVersion load. Having Roassal out implies that I will essentially focus on Roassal instead of Mondrian. Naturally, I will continue to incorporate important bug fixes in Mondrian. But as far I am concerned, no major enhancement of Mondrian is planned. We learnt a lot with Mondrian. Roassal really goes one step further with better interactions, a clean low level if you wish to build your own domain specific language. To be short, Roassal is simpler and better. I suggest people to enter bug fixes and requests for enhancement in the Moose google project as we are doing for Mondrian. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: 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

-- www.tudorgirba.com "What is more important: To be happy, or to make happy?"

Reply