Le 30/03/2015 21:22, Peter Uhnák a écrit :
I think the idea would be to have option to load it in one go instead of loading two independent libraries... something like
ConfigurationOfRoassal loadWithPresenters.
This one is easy.
or ConfigurationOfRoassal load; loadPresenters.
I think this one would work as well.
(I'm not sure if either of those are possible with Meta(monti)cello.)
Well, it is often not Metacello the issue, it has more to do with the fact that dependencies in configurations may be hard to set up.
I think it would be welcome addition.
I have been tempted to fork Roassal on github at times (sorry Alexandre :)) just to have - a correct Roassal2 for Pharo 3, and, yes, all the dependencies setup right.
This would be especially easy, because: git merge would take care of merging back Roassal2 developments inside the Pharo 3 branch (with the old example browser) probably without any conflicts, and a simple baseline would fetch the latest Roassal nicely, since we allways load the development version directly.
Thierry
Peter
On Sun, Mar 22, 2015 at 2:22 PM, Sean P. DeNigris <sean@clipperadams.com mailto:sean@clipperadams.com> wrote:
> Could you be more specific? In what Pharo version are you? I loaded Roassal2 stable into Pharo 4.0 but didn’t get the presenters, so I had to load Glamour stable to get them (after searching and figuring out where they lived) Cheers, Sean ------------------------------------------------------------------------ View this message in context: Re: Suggestion: Load Presenters with Roassal (was Re: Roassal Example Browser in Pharo) <http://forum.world.st/Roassal-Example-Browser-in-Pharo-tp4813039p4814089.html> Sent from the Moose mailing list archive <http://forum.world.st/Moose-f1310756.html> at Nabble.com. _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev