Problems with Roassal2 & Pharo 3.0
Started today with a fresh download of Pharo 3.0 and installed Roassal2 from the Configbrowser. Looks like Roassal now depends on the GTToolkit and other things, which are not correctly handled in the Config. What is missing here? What packages should be loaded? It is a bit disappointing how unstable/fragile the things are .... i see that you want make progress, but it is really hard to follow the development when not a "hardcore&fulltime" User .... Volkert
I think it doesn't have dependency on GT/Glamour because that is now part of Pharo 4.0 core. But I see packages ConfigurationOf... GTInspector, GTPlayground and Glamour (+Core for each of them). So you can try to load these. Maybe playground isn't needed. Also if you started with fresh image why not just switch to Pharo 4.0? Peter On Fri, Nov 14, 2014 at 10:06 PM, volkert@nivoba.de <volkert@nivoba.de> wrote:
Started today with a fresh download of Pharo 3.0 and installed Roassal2 from the Configbrowser. Looks like Roassal now depends on the GTToolkit and other things, which are not correctly handled in the Config.
What is missing here? What packages should be loaded?
It is a bit disappointing how unstable/fragile the things are .... i see that you want make progress, but it is really hard to follow the development when not a "hardcore&fulltime" User ....
Volkert
Also last time I checked Roassal itself worked in Pharo 3.0, only the examples must have changed recently. On Fri, Nov 14, 2014 at 10:39 PM, Peter Uhnák <i.uhnak@gmail.com> wrote:
I think it doesn't have dependency on GT/Glamour because that is now part of Pharo 4.0 core. But I see packages ConfigurationOf... GTInspector, GTPlayground and Glamour (+Core for each of them). So you can try to load these. Maybe playground isn't needed.
Also if you started with fresh image why not just switch to Pharo 4.0?
Peter
On Fri, Nov 14, 2014 at 10:06 PM, volkert@nivoba.de <volkert@nivoba.de> wrote:
Started today with a fresh download of Pharo 3.0 and installed Roassal2 from the Configbrowser. Looks like Roassal now depends on the GTToolkit and other things, which are not correctly handled in the Config.
What is missing here? What packages should be loaded?
It is a bit disappointing how unstable/fragile the things are .... i see that you want make progress, but it is really hard to follow the development when not a "hardcore&fulltime" User ....
Volkert
I tried loading Glamour and GT-Toolkit from the smalltalkhub. It works now. BW, Volkert Am 14.11.2014 um 22:39 schrieb Peter Uhnák:
I think it doesn't have dependency on GT/Glamour because that is now part of Pharo 4.0 core. But I see packages ConfigurationOf... GTInspector, GTPlayground and Glamour (+Core for each of them). So you can try to load these. Maybe playground isn't needed.
Also if you started with fresh image why not just switch to Pharo 4.0?
Peter
On Fri, Nov 14, 2014 at 10:06 PM, volkert@nivoba.de <mailto:volkert@nivoba.de> <volkert@nivoba.de <mailto:volkert@nivoba.de>> wrote:
Started today with a fresh download of Pharo 3.0 and installed Roassal2 from the Configbrowser. Looks like Roassal now depends on the GTToolkit and other things, which are not correctly handled in the Config.
What is missing here? What packages should be loaded?
It is a bit disappointing how unstable/fragile the things are .... i see that you want make progress, but it is really hard to follow the development when not a "hardcore&fulltime" User ....
Volkert
-- www.nivoba.de "The more complex an object, the larger the investment in learning to use it, and the greater the resistance to abandon it.", NW
participants (2)
-
Peter Uhnák -
volkert＠nivoba.de