>Try the very latest Pharo (please stop using the name pharo-dev (I
>know I'm still doing it but that's a mistake :-))

ups... I'm confused... in previous mails I read that one image is Pharo-core, another pharo-dev and another pharo-web...�
Why should we not make that�distinction? sorry but I do not understand....

On Fri, May 15, 2009 at 12:06 PM, Damien Cassou <damien.cassou@gmail.com> wrote:
2009/5/15 Hernan Wilkinson <hernan.wilkinson@gmail.com>:
> Yes, I tried it on a pharo-dev image. I thought that there could be a
> conflict between ecomp and ocomp but I also thought that ocomp would disable
> ecomp when loading... anyway, I did not have the time to check that so I
> went to the previous image.

Try the very latest Pharo (please stop using the name pharo-dev (I
know I'm still doing it but that's a mistake :-))(this looks like
Lisp)) which now has OCompletion installed:
http://pharo-project.org/download.

> (BTW I also tried to load ocomp on a pharo-core image and I could not
> because there is no Installer class. I could not either with the monticello
> brower... )

Installer is not installed by default. ScriptLoader new installingInstaller.

> So, the performance issue was when typing class names. For example, I typed
> 'Ar' press tab and it took a lot to show the valid names. Selected Array and
> the started to delete it and it also took a lot of time to delete each
> character. I tried the same thing on an pharo-dev image without ocomp and
> worked fine... so there must be something going on.

Can't reproduce on latest Pharo.


--
Damien Cassou
http://damiencassou.seasidehosting.st

"Lambdas are relegated to relative obscurity until Java makes them
popular by not having them." James Iry

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