As i mentioned, i tried only the roassal menus "Roassal evaluator" and "Roassal examples" (under tools). No roassal window popped up. Looks like problem is in "trachelShapeFor" of class RTLabel (txt replaceAllRegex). There is no selector "replaceAllRegex" and it is the only place where such message is send. Look: trachelShapeFor: anElement | c txt lines n s lbl | c := self colorFor: anElement. txt := self textFor: anElement. txt := txt replaceAllRegex: String tab with: ' '. lines := txt lines. Maybe this is a dependency to an other package? BW, Volkert Am 17.05.2014 11:29, schrieb Alexandre Bergel: _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Hi Volkert, I took a look. The problem is that Roassal2 used a method that does not come with Pharo. I fixed the problem and now you can again use Roassal2 independently from the Moose distribution. Cheers, Doru On Sat, May 17, 2014 at 5:06 PM, volkert(a)nivoba.de <mailto:volkert@nivoba.de> &lt;volkert(a)nivoba.de <mailto:volkert@nivoba.de>> wrote: Some more problems with the examples in the RTMondrianExample. "exampleClasses" and "exampleSystemComplexity" not work because selectors like "numberOfLinesOfCode" and "numberOfVariables" are missing. The examples in RTRoassalExample are fine, except the examples depending on the error in RTLabel. BW, Volkert Am 17.05.2014 12:38, schrieb volkert(a)nivoba.de <mailto:volkert@nivoba.de>: As i mentioned, i tried only the roassal menus "Roassal evaluator" and "Roassal examples" (under tools). No roassal window popped up. Looks like problem is in "trachelShapeFor" of class RTLabel (txt replaceAllRegex). There is no selector "replaceAllRegex" and it is the only place where such message is send. Look: trachelShapeFor: anElement | c txt lines n s lbl | c := self colorFor: anElement. txt := self textFor: anElement. txt := txt replaceAllRegex: String tab with: ' '. lines := txt lines. Maybe this is a dependency to an other package? BW, Volkert Am 17.05.2014 11:29, schrieb Alexandre Bergel: Hi Volker! Can you tell us which example exactly fails? I am away from my laptop this week end. I will not be able to fix much Cheers, Alexandre Le 17-05-2014 à 4:57, Esteban Lorenzano &lt;estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> a écrit : yeah, but where? looks like a roassal problem, not a pharo one. Redirecting to moose list :) Esteban On 17 May 2014, at 10:24, volkert(a)nivoba.de <mailto:volkert@nivoba.de> wrote: Am 01.05.2014 13:07, schrieb Alexandre Bergel: Yes yes yes ... it works. I quickly jumped through some examples. Roassal2 looks so nice. Thank you. Let me know how it goes. Documentation is missing, but we have many many examples... The chapter in Deep into Pharo (www.deepintopharo.com <http://www.deepintopharo.com>) contains a documentation about Roassal1 and the Mondrian builder, written on top of the core of Roassal. Roassal2 is largely compatible with Roassal1. When it is not, then small changes have to be made. Alexandre today i started with a fresh pharo 3.0 image (#30848) und loaded roassal2 (following the video tutorial). But when selecting the example and evalution menu i got a "MessageNotUnderstood: ByteString>>replaceAllRegex:with:". Something is broken here. BW, Volkert _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com <http://www.tudorgirba.com> "Every thing has its own flow" _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

These problems are now fixed Roassal2 works well on vanilla Pharo 3. You just need to update the font. Alexandre