Thanks Johan,

this is indeed a Pharo/Squeak problem. Time to times, the morph  
causing an error is not draw in red but loops. Could be that  
WorldState>>displayWorldSafely: does not find the guilty morph.

Cheers,
Alexandre

On 30 Nov 2009, at 15:57, Johan Fabry wrote:

> 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 [email protected]
>> 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
>>> [email protected]
>>> 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
>> [email protected]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> --
> Johan Fabry
> [email protected] - http://dcc.uchile.cl/~jfabry
> PLEIAD Lab - Computer Science Department (DCC) - University of Chile
>
>
>
>
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

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






_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to