22 Jan
2015
22 Jan
'15
7:51 p.m.
Hi!
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 result)
Open Workspace and execute this:
Gofer new
smalltalkhubUser: 'Moose' project: 'Moose';
configuration;
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 there.
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
be 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
image.
- 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
debuggers.
Now, even when Pharo seems to have issues already. I go on an try this:
Gofer new
smalltalkhubUser: 'Moose' project: 'GToolkit';
configuration;
loadStable.
#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.
Cheers!
Sebastian
22 Jan
22 Jan
9:16 p.m.
New subject: Trouble loading a stable Moose environment in a Pharo 3.0 image
Hi,
welcome
everybody uses a pre-built Moose image, it's easier and faster
look at http://moosetechnology.org/
nicolas
On 22/01/2015 19:51, Sebastian Heidbrink wrote:
Hi!
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
result)
Open Workspace and execute this:
Gofer new
smalltalkhubUser: 'Moose' project: 'Moose';
configuration;
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 there.
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 be 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 image.
- 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
debuggers.
Now, even when Pharo seems to have issues already. I go on an try this:
Gofer new
smalltalkhubUser: 'Moose' project: 'GToolkit';
configuration;
loadStable.
#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.
Cheers!
Sebastian
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
9:32 p.m.
New subject: Trouble loading a stable Moose environment in a Pharo 3.0 image
Hi Nicholas,
that is what I originally did.
The only difference is that Roassal font related issues are "pre" fixed.
The same errors apply
Sebastian
Am 22.01.2015 um 12:16 schrieb Nicolas Anquetil:
Hi,
welcome
everybody uses a pre-built Moose image, it's easier and faster
look at http://moosetechnology.org/
nicolas
On 22/01/2015 19:51, Sebastian Heidbrink wrote:
Hi!
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
result)
Open Workspace and execute this:
Gofer new
smalltalkhubUser: 'Moose' project: 'Moose';
configuration;
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 there.
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 be 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 image.
- 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 debuggers.
Now, even when Pharo seems to have issues already. I go on an try this:
Gofer new
smalltalkhubUser: 'Moose' project: 'GToolkit';
configuration;
loadStable.
#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.
Cheers!
Sebastian
_______________________________________________
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 p.m.
New subject: Trouble loading a stable Moose environment in a Pharo 3.0 image
Hi Sebastian,
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 GToolkit.
Cheers,
Andrei
On Thu, Jan 22, 2015 at 7:51 PM, Sebastian Heidbrink <sheidev(a)yahoo.de>
wrote:
Hi!
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 result)
Open Workspace and execute this:
Gofer new
smalltalkhubUser: 'Moose' project: 'Moose';
configuration;
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
there.
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 be
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
image.
- 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
debuggers.
Now, even when Pharo seems to have issues already. I go on an try this:
Gofer new
smalltalkhubUser: 'Moose' project: 'GToolkit';
configuration;
loadStable.
#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.
Cheers!
Sebastian
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
10:17 p.m.
New subject: Trouble loading a stable Moose environment in a Pharo 3.0 image
4.0 is not official, or is it?
I want to present Pharo and Moose to newbies,... I want to make sure
that they go home, download Pharo and have fun with the PharoTutorial.
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?
In the 5.1 I can't even load a model! I am on Windows 7 64Bit english
Unit tests are great! But ui tests need to be done, too!
Sebastian
Am 22.01.2015 um 13:00 schrieb Andrei Chis:
Hi Sebastian,
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
GToolkit.
Cheers,
Andrei
On Thu, Jan 22, 2015 at 7:51 PM, Sebastian Heidbrink <sheidev(a)yahoo.de
<mailto:sheidev@yahoo.de>> wrote:
Hi!
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 result)
Open Workspace and execute this:
Gofer new
smalltalkhubUser: 'Moose' project: 'Moose';
configuration;
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 there.
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 be 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 image.
- 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 debuggers.
Now, even when Pharo seems to have issues already. I go on an try
this:
Gofer new
smalltalkhubUser: 'Moose' project: 'GToolkit';
configuration;
loadStable.
#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.
Cheers!
Sebastian
_______________________________________________
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
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
10:33 p.m.
New subject: Trouble loading a stable Moose environment in a Pharo 3.0 image
On Thu, Jan 22, 2015 at 10:17 PM, Sebastian Heidbrink <sheidev(a)yahoo.de>
wrote:
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 that
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
finder)
Gofer new
smalltalkhubUser: 'Moose' project: 'GToolkit';
configuration;
loadStable.
#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:
Gofer new
smalltalkhubUser: 'Moose' project: 'Moose';
configuration;
loadStable.
#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 (
http://www.smalltalkhub.com/#!/~Moose).
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 english
What error do you get?
Unit tests are great! But ui tests need to be done, too!
Indeed :)
Cheers,
Andrei
Sebastian
Am 22.01.2015 um 13:00 schrieb Andrei Chis:
Hi Sebastian,
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
GToolkit.
Cheers,
Andrei
On Thu, Jan 22, 2015 at 7:51 PM, Sebastian Heidbrink <sheidev(a)yahoo.de>
wrote:
Hi!
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
result)
Open Workspace and execute this:
Gofer new
smalltalkhubUser: 'Moose' project: 'Moose';
configuration;
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
there.
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 be
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
image.
- 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
debuggers.
Now, even when Pharo seems to have issues already. I go on an try this:
Gofer new
smalltalkhubUser: 'Moose' project: 'GToolkit';
configuration;
loadStable.
#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.
Cheers!
Sebastian
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing
listMoose-dev@iam.unibe.chhttps://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:59 p.m.
New subject: Trouble loading a stable Moose environment in a Pharo 3.0 image
Thank you very much for the fast change, Andrei.
I will have a look this afternoon.
The error.... I just wanted to take a screenshot but I can't reproduce
it. It might be a package related issue. I must check this with more time.
I can only remember that a "self changed" was not understood by some
kind of Brick list thing... :-D Sorry.
I open Moose Panel and opened the ST menue to import a package. Then I
selected one and hit the "Next" button.
Then the Debugger showed up.
I'll let you know as soon as I have tested all of this.
Sebastian
Am 22.01.2015 um 13:33 schrieb Andrei Chis:
On Thu, Jan 22, 2015 at 10:17 PM, Sebastian Heidbrink
<sheidev(a)yahoo.de <mailto:sheidev@yahoo.de>> wrote:
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 that 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 finder)
Gofer new
smalltalkhubUser: 'Moose' project: 'GToolkit';
configuration;
loadStable.
#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:
Gofer new
smalltalkhubUser: 'Moose' project: 'Moose';
configuration;
loadStable.
#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
(http://www.smalltalkhub.com/#!/~Moose
<http://www.smalltalkhub.com/#%21/%7EMoose>).
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 english
What error do you get?
Unit tests are great! But ui tests need to be done, too!
Indeed :)
Cheers,
Andrei
Sebastian
Am 22.01.2015 um 13:00 schrieb Andrei Chis:
Hi Sebastian,
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 GToolkit.
Cheers,
Andrei
On Thu, Jan 22, 2015 at 7:51 PM, Sebastian Heidbrink
<sheidev(a)yahoo.de <mailto:sheidev@yahoo.de>> wrote:
Hi!
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 result)
Open Workspace and execute this:
Gofer new
smalltalkhubUser: 'Moose' project: 'Moose';
configuration;
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 there.
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 be 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 image.
- 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 debuggers.
Now, even when Pharo seems to have issues already. I go on an
try this:
Gofer new
smalltalkhubUser: 'Moose' project: 'GToolkit';
configuration;
loadStable.
#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.
Cheers!
Sebastian
_______________________________________________
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
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
23 Jan
23 Jan
4:17 p.m.
New subject: Trouble loading a stable Moose environment in a Pharo 3.0 image
Okay,
here you are some of my new results.
5.1 image in a pharo 4.0 installation:
- Moose pane tabs strange resize upon mouse over.
- Moose pane tabs sometimes won't disappear after closing them. One
hast to click on them "anywhere" and then they disappear.
- managed to make Moose pane freeze after selecting a different
entry in the main model entry level list. I can't relaibly reprdocuce it
yet.
- The Finish button of the Pharo ST model import is out of sight.
One needs to resize Pharo to access it.
- The label of the tab on top of the loaded model list is
shortended and not readable...
Other than that that is the best combination so far. Thank you!
Pharo 3.0 virgin install with:
Gofer new
smalltalkhubUser: 'Moose' project: 'Moose';
configuration;
loadStable.
Code critics Browser of Pharo is broken.
I did not even activate Moose yet.
This is the official combination and release on the web sites. You
should change that.
Sebastian
Am 22.01.2015 um 13:33 schrieb Andrei Chis:
On Thu, Jan 22, 2015 at 10:17 PM, Sebastian Heidbrink
<sheidev(a)yahoo.de <mailto:sheidev@yahoo.de>> wrote:
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 that 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 finder)
Gofer new
smalltalkhubUser: 'Moose' project: 'GToolkit';
configuration;
loadStable.
#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:
Gofer new
smalltalkhubUser: 'Moose' project: 'Moose';
configuration;
loadStable.
#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
(http://www.smalltalkhub.com/#!/~Moose
<http://www.smalltalkhub.com/#%21/%7EMoose>).
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 english
What error do you get?
Unit tests are great! But ui tests need to be done, too!
Indeed :)
Cheers,
Andrei
Sebastian
Am 22.01.2015 um 13:00 schrieb Andrei Chis:
Hi Sebastian,
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 GToolkit.
Cheers,
Andrei
On Thu, Jan 22, 2015 at 7:51 PM, Sebastian Heidbrink
<sheidev(a)yahoo.de <mailto:sheidev@yahoo.de>> wrote:
Hi!
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 result)
Open Workspace and execute this:
Gofer new
smalltalkhubUser: 'Moose' project: 'Moose';
configuration;
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 there.
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 be 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 image.
- 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 debuggers.
Now, even when Pharo seems to have issues already. I go on an
try this:
Gofer new
smalltalkhubUser: 'Moose' project: 'GToolkit';
configuration;
loadStable.
#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.
Cheers!
Sebastian
_______________________________________________
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
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev 
12:34 a.m.
New subject: Trouble loading a stable Moose environment in a Pharo 3.0 image
The loadStable is supposed to work in Pharo3. Development might only
work with Pharo 4,
which is mostly perfectly fine and sometimes undergoing major surgery.
If you ever find yourself having to fix these issues, this is where I
would start:
- download the latest green builds of moose5.1 and 5.0 to see if the
problems are there too.
- take a look at the configuration of the ci build of moose to see what
is supposed to happen.
- try to do a loadStable and check the package cache for multiple
versions of the same
package.
- compare the current ConfigurationOfMoose (364) with that at release
and look at the
different package versions (Moose-Finder 515 vs 516, PetitJava 158 vs
160)
- take a look at the configurations of the dependencies to see which
ones changed their stable
since the moose50 release (2014-12-23)
That is at top-level:
spec
project: 'Metanool' with: #stable;
project: 'Fame' with: #stable;
project: 'RoelTyper' with: #stable;
project: 'MooseAlgos' with: #stable;
project: 'PetitParser' with: #stable;
project: 'SmallDude for Moose' with: #stable;
project: 'PetitSQL' with: #stable;
project: 'Glamour' with: #stable;
project: 'Roassal2' with: #stable;
project: 'XMLParser' with: #stable;
project: 'Pastell' with: #stable;
project: 'Merlin' with: #stable;
project: 'GToolkit' with: #stable;
project: 'OSProcess' with: #stable.
Of those, Glamour changed: 197 -> 202, Roassal2 15 -> 25,
XMLParser 102 -> 109, GToolkit 64 -> 69
I'm happy to see that fixing the #stable definition
in ConfigurationOfGlamour should be enough to make things work again.
Stephan
3620
days inactive
3621
days old
8 comments
4 participants
participants (4)
-
Andrei Chis -
Nicolas Anquetil -
Sebastian Heidbrink -
stephan