OCompletion don't works on trunk image

I'm trying to check the dev tools I used to use on a daily basis, and
OCompletion don't works
neither in trunk.

After install it from Universes, opening a workspace and trying to
type something I get:

SmalltalkEditor(Object)>>doesNotUnderstand: #model

Cheers.
Germán.

On Sun, 21 Feb 2010, Germán Arduino wrote:

> I'm trying to check the dev tools I used to use on a daily basis, and
> OCompletion don't works
> neither in trunk.
>
> After install it from Universes, opening a workspace and trying to
> type something I get:

I still think that you shouldn't use Universes, since it's mostly
abandoned.

>
> SmalltalkEditor(Object)>>doesNotUnderstand: #model

Let's face it, developers who only use Pharo don't care about Squeak,
though there are people, who try to fix things, with some success.

To load OCompletion to a trunk image, do this:
(Installer ss project: 'OCompletion')
  install: 'OCLoader';
  install: 'Ocompletion' "For the latest version"

This will load Shout which has conflicts with Shout-Core (Trunk images use
Shout-Core), so later updates to the Shout-Core package will require
merging.


Levente

>
> Cheers.
> Germán.
>
>

2010/2/21 Levente Uzonyi <[hidden email]>:
Is a great loss not be able to use Universes. That means, between
other things, that
one must figure out dependencies of the packages.

And, if Universes is abandoned, what is the reason to maintain it on the image?

I was talking about this, how I can figure out that I need to build
this script to install OCompletion?

> This will load Shout which has conflicts with Shout-Core (Trunk images use
> Shout-Core), so later updates to the Shout-Core package will require
> merging.
>

Understand. This is the reason that Shout Wksp/Monticello not works
neither (as I asked in another mail)?


>
> Levente
>
>>
>> Cheers.
>> Germán.
>>

On Sun, 21 Feb 2010, Germán Arduino wrote:
It's not officially abandoned, I guess it's up to us to decide what to do
with it. Some packages are still working, so it still has some value.
Ask the package maintainer to provide installation instructions.

>> This will load Shout which has conflicts with Shout-Core (Trunk images use
>> Shout-Core), so later updates to the Shout-Core package will require
>> merging.
>>
>
> Understand. This is the reason that Shout Wksp/Monticello not works
> neither (as I asked in another mail)?

Probably yes, though there may be other reasons. We should provide a way
to have a Workspace with syntax highlighting. I think it's easy to do it
if someone knows how Shout-Core works.


Levente

2010/2/21 Levente Uzonyi <[hidden email]>:
mm, I personally think that a tool works or not......I means, the fact of
having some packages working and others not is confusing.



> We should provide a way to
> have a Workspace with syntax highlighting.

+1111111111111111111111


> I think it's easy to do it if
> someone knows how Shout-Core works.

Not me. Until the moment I saw Shout-Core on trunk I ever installed Shout from
Code Browsing categories and next Shout-Wksp/Monticello and never had
a problem.


Cheers.
Germán.