On Thu, Jan 22, 2015 at 10:17 PM, Sebastian Heidbrink <sheidev(a)yahoo.de>
4.0 is not official, or is it?
Yes, it not the official version but it's in a, more or less, usable state.
I want to present Pharo and Moose to newbies,... I want to make sure
they go home, download Pharo and have fun with the PharoTutorial.
I understand your use case. I fixed the configuration of GToolkit to load
into pharo 3. The following code now works (but does not load the moose
smalltalkhubUser: 'Moose' project: 'GToolkit';
#GTImageSetupCommandLineHandler asClass new activateWithoutSaving.
This loads the entire moose 5.0. Haven't run it but the moose 5 build is
green so it should work:
smalltalkhubUser: 'Moose' project: 'Moose';
#MooseImageSetupCommandLineHandler asClass new activateWithoutSaving.
And now to your suggestion.
Where do the package sources for 5.1 reside? I assume this 5.1 image does
not work within a 5.0 folder, does it?
The package sources are on Smalltalkhub (
A 5.1 image should work if you put it in the folder from the 5.0
distribution. The vm needed to run them is the same.
In the 5.1 I can't even load a model! I am on Windows 7 64Bit
What error do you get?
Unit tests are great! But ui tests need to be done, too!
Am 22.01.2015 um 13:00 schrieb Andrei Chis:
Why not use the prebuild image of Moose 5.1 from Pharo 4? You can
download it here: https://ci.inria.fr/moose/job/moose-5.1/
Moose 5.0 is already way behind Moose 5.1 regarding the tools from
On Thu, Jan 22, 2015 at 7:51 PM, Sebastian Heidbrink <sheidev(a)yahoo.de>
> I wanted to familiarize myself with Moose and the GlamourToolkit.
> Since 2 days I try to load a stable and fully working environment but it
> is not poassible no matter how many combinations of version ans
> repositories I use.
> Here are the steps I would expect to result in a working Moose-Image
> based on a Pharo 3.0 virgin image.
> Download a Pharo 3.0 installation.
> Sytem - Software update (with and without this step... no different
> Open Workspace and execute this:
> Gofer new
> smalltalkhubUser: 'Moose' project: 'Moose';
> loadStable. (or loadDevelopment but both have the same results)
> While loading the Moose package, I get several warnings about missing
> prerequisites or application that are about to be modified (mainly
> GTSpotter and Context related issues). I guess the load order is not right
> Now here are my bugs:
> - Pharo Critic Browser is broken after loading Moose. I attached the
> stack. No I didn't it is 8mb,... too much for the forum, I guess
> - On a small netbook screen one can't import smalltalk code into Moose.
> The final import form/widget is so big, that the "finish" button can not
> pressed and the widget can't be moved. A different layout might be helpful.
> The taskbar overlays and intercapts mouse events.
> - When I want to close a Model in Moose Panel and I close the main tab I
> get a massive amount of debuggers and it is better to shutdown the image.
> - Roassal widgets with text overlays show a red background debugger on
> mouse over events. StrikeFont dnu.... (LocalFont glyphRendererOn:). I
> meanwhile know that I can solve this by changing the Font settings of my
> - The Moose Panel's tabs behaves wierd. On mouse over they change the
> size of the tab's labels and one can't read and localize the desired tab
> anymore. This gets worse when you have many tabs opened
> - When I just close one of many tabs in Moose panel, I get errors
> regarding doLayout is not understood by undefined Object and the whole
> image freezes or after a further clicks,... the image is swamped with
> Now, even when Pharo seems to have issues already. I go on an try this:
> Gofer new
> smalltalkhubUser: 'Moose' project: 'GToolkit';
> #GTImageSetupCommandLineHandler asClass new activateWithoutSaving
> - it is unclear to me how I can start the gtspotter....
> - Open playground do a 1 inspect and get a Debugger saying SmallInteger
> class dnu allSLots
> Okay this is the last thing that makes the most enthusiastic user go away
> from .... I hope not Smalltalk.
> I started a software night here in town last Tuesday and I want to add
> Smalltalk flavour. So far they where amazed about it but I used VASmalltalk
> to show a "real live development system" sinceI know that it is bullit
> proof. And it was.
> But I also want to introduce the aspect of Smalltalk as tool and that is
> where Phaor and Moose come in... it would be great if I had a stable image
> that I could use for future nights.
> It would be great if somebody could look into that.
> Moose-dev mailing list
Moose-dev mailing list