[Pharo-project] OCompletion is broken in 1.3

Schwab,Wilhelm K bschwab at anest.ufl.edu
Sun Jun 12 10:56:01 EDT 2011

It works now, but can't be disabled by settings.  Please see Issue 4390 with attached fix:


The fix adds a condition on ECPreferences class>>enabled to disallow completion when appropriate.  The relevant line is the following:

    completionAllowed := ECPreferences enabled and:[ ECController allowModel: stringHolder ].


From: pharo-project-bounces at lists.gforge.inria.fr [pharo-project-bounces at lists.gforge.inria.fr] On Behalf Of Mariano Martinez Peck [marianopeck at gmail.com]
Sent: Friday, June 10, 2011 8:30 AM
To: Pharo-project at lists.gforge.inria.fr
Subject: Re: [Pharo-project] OCompletion is broken in 1.3

THanks ben for all your help. It is fixed now.

On Fri, Jun 10, 2011 at 12:22 PM, Benjamin <benjamin.vanryseghem.pharo at gmail.com<mailto:benjamin.vanryseghem.pharo at gmail.com>> wrote:
In fact, I have posted two things:
- a little improvement in OCompletion (not related to the bug)
- then I take a look at OCompletionPharoCompatibility, but I have done a mistake because the package is OcompletionPharoCompatibility (with a minus "c")

So finally, the only thing I have done to fix the bug is to change the ConfigurationOfOCompletion which now call a post load method to reset the default toolset and take in account the registry method.

I hope I haven't done too many stupid things :)


On Jun 10, 2011, at 12:05 PM, Mariano Martinez Peck wrote:

so...I saw you commit in OCompletion and then rollback the pharo-ish part. So..can that be put instead to OCompletionPharoCompatibilty and we are done?
then we update ConfigurationOfOCompletion and we fix it :)

On Fri, Jun 10, 2011 at 11:59 AM, Mariano Martinez Peck <marianopeck at gmail.com<mailto:marianopeck at gmail.com>> wrote:

On Thu, Jun 9, 2011 at 12:45 PM, Benjamin Van Ryseghem <benjamin.vanryseghem.pharo at gmail.com<mailto:benjamin.vanryseghem.pharo at gmail.com>> wrote:
It's fixed, I am looking where to post the fix :)


Put it somewhere please :)

OCompletionPharoCompatibilty  is not enough?  you have commit rights there....


2011/6/9 Benjamin Van Ryseghem <benjamin.vanryseghem.pharo at gmail.com<mailto:benjamin.vanryseghem.pharo at gmail.com>>
It comes from Toolset change.

OCompletion should be registered as a Completion tool (but I do not remember the magic formula ^^)


2011/6/9 Marcus Denker <marcus.denker at inria.fr<mailto:marcus.denker at inria.fr>>

On Jun 9, 2011, at 12:21 PM, Benjamin Van Ryseghem wrote:

> It happened between 13217 and 13234 ...
> Maybe the Paragraph changes ?

The Dev vs. Core is killing us. We need *one* image. We should really try to do that with 1.4, it will
make everything simpler and easier to manage.


Marcus Denker  -- http://www.marcusdenker.de<http://www.marcusdenker.de/>
INRIA Lille -- Nord Europe. Team RMoD.




More information about the Pharo-dev mailing list