[Pharo-project] OComplection

Esteban Lorenzano estebanlm at gmail.com
Mon Aug 6 12:34:07 CEST 2012

OCompletion works fine for me. And is much more valuable for me than EC... yes we can (and need) improve it, but I don't want to drop OC.
Is the same case of nautilus many-methods and tabs. Just because you don't find the function valuable, that does not means that it is not worthy for anybody :)


On Aug 6, 2012, at 12:15 AM, Camillo Bruni <camillobruni at gmail.com> wrote:

> the more time I spend with OCompletion the more I think it's the wrong model:
> NECompletion provides in many cases way better / quicker results
> NOCompletion does tons of magic to increase the chances of a correct hit,
> neglecting
> - self sends
> - super sends
> - ClassSends
> which is basically the main source for getting nice input...
> I think NOCompletion should be removed. The only thing that might maintain
> is a Database which will give back a date for a given selector so we can
> sort them accordingly. But IMO that can be solved muuuuch easier.
> Things against NOCompletion:
> - not documentation whatsoever (no class comments no comments no categories... nada)
> - totally breaks type completion (self sends usw...)
> - duplication of NECompletion...
> Since I don't see anybody maintaining this dead body we should remove it
> from the system!

More information about the Pharo-project mailing list