Hi Doru,

thanks for the workaround!

Thanks for pointing me to the moose google code side. Expect some moose-related bugreports from me in the issue tracker, for example in a few minutes my inability to debug Mondrian scripts in Pharo. (I leave figuring out who is the end responsible to you guys ...). http://code.google.com/p/pharo/issues/detail?id=1525

On 30 Nov 2009, at 13:55, Tudor Girba wrote:

Hi Johan,

Thanks for the report.

A better forum for Moose related problems would be the moose-dev@iam.unibe.ch mailing list. You can subscribe here: https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Also, to create an issue related to Moose, please use: http://code.google.com/p/moose-technology/issues/list

Coming to your issue, this is due to Metacello having no progress bar. However, if you open a Transcript, you will get a progress report. So, now I changed a bit the ConfigurationOfMoose and it opens it for you when you loadDefault. You can get the change in: ConfigurationOfMoose-tg.33

Cheers, Doru

On 30 Nov 2009, at 16:19, Alexandre Bergel wrote:

...

...

finally able to get going on Pharo, I wanted to load Moose. I got the ConfigurationOfMoose package, and run the loadDefault method.

Very good start!

...

I have no problem with a 'load' taking for ever, I know I am on the other side of the ocean. But please change the cursor to a 'wait' cursor while doing the load. It takes a loooooooong time before the first progress bar shows, I almost panicked. And now a progress bar just dissapeared, but there is still nothing I can do. The 'wait' cursor would go a long way in easing my mind. And it's probably just one line of code ...

Yeah, this is a well known problem.

Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

---

Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

-- www.tudorgirba.com

"One cannot do more than one can do."

---

Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

-- Johan Fabry jfabry@dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile

On 30 nov. 2009, at 13:55, Tudor Girba wrote:

Coming to your issue, this is due to Metacello having no progress bar. However, if you open a Transcript, you will get a progress report. So, now I changed a bit the ConfigurationOfMoose and it opens it for you when you loadDefault. You can get the change in: ConfigurationOfMoose-tg.33

Actually, that is an excellent idea, because the Transcript gave a glimpse at what happens during these looooooong minutes between Monticello finished loading and the Moose workspace opens. It is compiling stuff :) Maybe there is a way to get UI feedback from the compiler.

And it's finding looooots of undeclared classes and variables, as well as shadowed variable. We should take a look at this (unfortunatenly I should capture the transcript stream in a file, it is too big). Some undeclared are just work in progress which make their way in the default package, some are from yet to be ported package, some are just basic mistakes.

This one is annoying because it comes every time you manipulate a window. ScrollPane>>vScrollBarValue: (systemWindow is Undeclared)

Another surprising thing: package Famix-Tests-Aspix gets loaded, but it should not (and it's not specified in the configuration). I don't understand how.

-- Simon