ConfigurationOfMetacello and OB

Hi all,

Installing ConfigurationOfMetacello requires the installation of OB.  
However, OB does not properly install in Core 1.1.
Is there something we can do against that? It would be great to do so.

Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.





_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Yeah, twice the same day. I sincerely appology for this.

Cheers,
Alexandre


On 4 Mar 2010, at 15:31, Alexandre Bergel wrote:

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.





_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

I am looking into this. I reply to the Pharo list, I think the Moose
list is the wrong one.

The refactoring engine seems to work well. All tests pass.

OmniBrowser is more difficult. There are 7 tests failing, and there
are 8 errors.

There is a large number of deprecated code that OB is calling. What am
I supposed to do so that OB continues to work in Pharo 1.0 and 1.1?
Can I expect that people have the deprecated warnings disabled?

- How are menus registered? TheWorldMenu does not exist any longer.

- What is the replacement for #intialExtent?

Cheers,
Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Sorry, forgot to add the Pharo list ...

---------- Forwarded message ----------
From: Lukas Renggli <[hidden email]>
Date: 4 March 2010 20:13
Subject: Re: [Moose-dev] Re: ConfigurationOfMetacello and OB
To: Related to the development of Moose and other related tools
<[hidden email]>


I am looking into this. I reply to the Pharo list, I think the Moose
list is the wrong one.

The refactoring engine seems to work well. All tests pass.

OmniBrowser is more difficult. There are 7 tests failing, and there
are 8 errors.

There is a large number of deprecated code that OB is calling. What am
I supposed to do so that OB continues to work in Pharo 1.0 and 1.1?
Can I expect that people have the deprecated warnings disabled?

- How are menus registered? TheWorldMenu does not exist any longer.

- What is the replacement for #intialExtent?

Cheers,
Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch



--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Lukas,

Doesn't this enter into the same territory that you are in with Seaside ... you are dealing with multiple platforms 1.0 and 1.1.

The code can to be partitioned into "platform-specific" and "common" packages or you can monkey-patch for one of the platforms (presumably 1.0 should be monkey patched) and then merge on a regular basis.

Metacello can be taught to distinguish between different Pharo versions, so the technicalities of having different sets of packages to load based on which version of Pharo you are running is straightforward (I do this for GemStone already).

Dale
----- "Lukas Renggli" <[hidden email]> wrote:

| Sorry, forgot to add the Pharo list ...
|
| ---------- Forwarded message ----------
| From: Lukas Renggli <[hidden email]>
| Date: 4 March 2010 20:13
| Subject: Re: [Moose-dev] Re: ConfigurationOfMetacello and OB
| To: Related to the development of Moose and other related tools
| <[hidden email]>
|
|
| I am looking into this. I reply to the Pharo list, I think the Moose
| list is the wrong one.
|
| The refactoring engine seems to work well. All tests pass.
|
| OmniBrowser is more difficult. There are 7 tests failing, and there
| are 8 errors.
|
| There is a large number of deprecated code that OB is calling. What
| am
| I supposed to do so that OB continues to work in Pharo 1.0 and 1.1?
| Can I expect that people have the deprecated warnings disabled?
|
| - How are menus registered? TheWorldMenu does not exist any longer.
|
| - What is the replacement for #intialExtent?
|
| Cheers,
| Lukas
|
| --
| Lukas Renggli
| http://www.lukas-renggli.ch
|
|
|
| --
| Lukas Renggli
| http://www.lukas-renggli.ch
|
| _______________________________________________
| Pharo-project mailing list
| [hidden email]
| http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

> Doesn't this enter into the same territory that you are in with Seaside ... you are dealing with multiple platforms 1.0 and 1.1.

You mean I need to do an OBPlatform for Pharo 1 and Pharo 1.1? Or what
are you referring too?

Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

>
> There is a large number of deprecated code that OB is calling. What am
> I supposed to do so that OB continues to work in Pharo 1.0 and 1.1?
> Can I expect that people have the deprecated warnings disabled?
>
> - How are menus registered? TheWorldMenu does not exist any longer.

alain will reply
have a look at the <worldmenu> pragma

menuCommandOn: aBuilder
        <worldMenu>
        (aBuilder group: #SystemChanges)
                parent: #CodeRecoveringTools;  
                with: [
                        (aBuilder item: #'Change Sorter')
                                action:[self new morphicWindow openInWorld];
                                icon: self taskbarIcon.
                        (aBuilder item: #'Recover lost changes...')
                                action: [ChangeList browseRecentLog]]

We should start writing a doc.

> - What is the replacement for #intialExtent?

defining it in the model ?

Stef
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

----- "Lukas Renggli" <[hidden email]> wrote:

| > Doesn't this enter into the same territory that you are in with
| Seaside ... you are dealing with multiple platforms 1.0 and 1.1.
|
| You mean I need to do an OBPlatform for Pharo 1 and Pharo 1.1? Or
| what
| are you referring too?

Yes, an OBPlatform for each major version...


Dale
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev