On Thu, 2009-05-28 at 14:15 -0700, Dale Henrichs wrote:
> Norbert,
> 
> I would recommend using an older version of Pharo for GemTools - the 
> one-click GemTools 2.3.1 preview (based on an earlier version of Pharo) is 
> the best option, in my opinion.
> 
Yes, you told me already. I just opened a new pharo after some time
and was greedy to have all the new stuff like ocompletion. So I
just gave it a try. My one click gemtools image is totally rugged
at the moment. I cannot open a class browser on the pharo side anymore.
Usually I don't need these because I only use the gemstone ones but....

> I am waiting for the rate of change to slow down a bit, before trying 
> GemTools on the latest version of Pharo.
> 
> On the other hand if you get GemTools running, let me know and I'll take it 
> for a whirl:)
> 
Dale, that was exactly my intention! Would be great for me to do it and
tell _you_ how it works ;)

Well, at least I saw that my debugging capabilities have improved in the
last months *g*

Norbert

> Dale
> 
> ----- "Norbert Hartl" <[email protected]> wrote:
> 
> | Hi,
> | 
> | I can't really follow the mailing list so some of these might
> | already known and fixed. I just tried to install a gemtools
> | client from universe. I'm using the latest pharo-dev.
> | 
> | Installing FFI brought up an syntax error because there is
> | an attempt writing to a temp. Did this change with the 
> | closures? I think this is fixed by the version some can load
> | via the ScriptLoader.
> | 
> | Next I encountered a problem with MIMEDocument. I think it
> | is Issue-631. There is an incorrect usage of the MIMEDocument
> | interface. I changed it but wanted to store it in PharoInbox
> | but my image crashes if I try to. 
> | 
> | It is:
> | 
> | Segmentation fault
> | 
> | -1178673304 UUID>initialize
> | -1178673420 Behavior>new:
> | -1178673512 >new
> | 
> | I updated my vm to exupery-0.15.1 but still has the same behaviour.
> | 
> | I attached a patch for the MIMEDocument issue on Issue-631.
> | 
> | Than I met InputSensor. InputSensor default returns an instance
> | of InputEventSensor. This looks just strange to me. Is this right?
> | 
> | Norbert
> | 
> | 
> | _______________________________________________
> | Pharo-project mailing list
> | [email protected]
> | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> 
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


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

Reply via email to