17 May
2012
17 May
'12
2:48 p.m.
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
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
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
3:08 p.m.
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
3:10 p.m.
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
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 
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?"
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."
8:24 p.m.
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
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
10:22 p.m.
Indeed, this was a problem.
Doru
On 17 May 2012, at 22:07, Stéphane Ducasse wrote:
doru
--
www.tudorgirba.com
"To lead is not to demand things, it is to make them happen."
> (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
18 May
18 May
2:57 a.m.
More feedback
Thanks!
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?
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)
...
ROMorphTest>>testClickingScenario(event is
shadowed)
ROExporter>>toVW (VW5PackageExporter is Undeclared)
Loaded -> RoassalMorphic-AlexandreBergel.28 --- http://www.squeaksource.com/Roassal
--- cache
Thanks, this should be all fixed!
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
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? 
17 Jun
17 Jun
10:27 a.m.
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.
cheers -ben
11:33 a.m.
On Jun 17, 2012, at 10:27 AM, Ben Coman wrote:
Stéphane Ducasse wrote:
Look for the email in pharo from simon allier about Manifest
Stef (running to buy vegetables before it is too late)
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.
cheers -ben
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
18 Jun
18 Jun
5:25 p.m.
Gofer
new
url: 'http://www.squeaksource.com/PharoTaskForces';
package: 'ConfigurationOfManifest';
load.
((Smalltalk at: #ConfigurationOfManifest) project version: #stable) load
But squeaksource is down now
Alexandre
On Jun 17, 2012, at 5:33 AM, Stéphane Ducasse wrote:
On Jun 17, 2012, at 10:27 AM, Ben Coman wrote:
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Stéphane Ducasse wrote:
Look for the email in pharo from simon allier about Manifest
Stef (running to buy vegetables before it is too late)
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.
cheers -ben
_______________________________________________
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
4333
days inactive
4365
days old
15 comments
4 participants
participants (4)
-
Alexandre Bergel -
Ben Coman -
Stéphane Ducasse -
Tudor Girba