...and btw, you shouldn't install newocompletion. It is integrated with pharocore now. nd the versions in repository are not updated (my fault, completely forget about that :P). If you want to re-load it, you can install packages in pharo repository (NECompletion and NOCompletion, in that order) best, Esteban On Apr 19, 2012, at 7:58 PM, Stéphane Ducasse wrote:
Yes people should fix the configurations. We will start to work on the process described in the PharoVision so that all the Configurations get tested.
Stef
On Apr 18, 2012, at 6:35 PM, Sean P. DeNigris wrote:
The Welcome window points to the config browser, which loads basic OB (no refactoring). I was expecting to have refactoring installed, which is done via (per http://forum.world.st/ANN-new-stable-version-of-omnibrowser-td4525968.html#a...): (ConfigurationOfOmniBrowser project version: #stable) load: #( 'Dev' 'Dev Tests').
This scripts installs OmniBrowser + OCompletion + Refactoring Browser
The above works, but maybe this is a problem because it's using the old OCompletion?
Then I tried to load NewOCompletion to see if it played nicely with OB, and got: "Error: Could not resolve: ConfigurationOfNewECompletion [ConfigurationOfNewECompletion] in /.../Pharo-1.4/package-cache".
So I loaded ConfigurationOfNewECompletion manually in the MC browser, and then ran into "MessageNotUnderstood: NOCCompletionTable class>>methodChanged:"
So there are some problems with the configs for the new completion work... and if these new tools work with OB, maybe the config for OB should be updated to use them, and then maybe the default group of the OB config should load 'Dev'...
Sean
Sean
-- View this message in context: http://forum.world.st/OB-Refactoring-and-OCompletion-in-1-4-tp4568254p456825... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.