load moose in Pharo1.2

List overview All Threads
Download

newer

older

completion in MOEasel

branch path ?

Cyrille Delaunay

1 Sep 2010 1 Sep '10

11:12 a.m.

Hello, Is moose loadable in Pharo 1.2 ? Is there a special script somwhere to that?

Attachments:

attachment.htm (text/html — 95 bytes)

Show replies by thread

Tudor Girba

1 Sep 1 Sep

2:29 p.m.

What do you mean by script? Did you try with the configuration? Doru On Sep 1, 2010, at 11:12, Cyrille Delaunay <cy.delaunay(a)gmail.com> wrote:

...

Hello, Is moose loadable in Pharo 1.2 ? Is there a special script somwhere to that? _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Cyrille Delaunay

2:48 p.m.

...

What do you mean by script? Did you try with the configuration? Doru On Sep 1, 2010, at 11:12, Cyrille Delaunay <cy.delaunay(a)gmail.com> wrote:

Hello, Is moose loadable in Pharo 1.2 ? Is there a special script somwhere to

that?

_______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Tudor Girba

4:10 p.m.

Hi Cyrille, That means that OB needs to be fixed :). Could you raise the issue on the pharo mailing list? Cheers, Doru On 1 Sep 2010, at 14:48, Cyrille Delaunay wrote:

...

When I try with the configuration, I get an error when loading the class OBMercuryPanel (from the package OB-Standard, that seems to be loaded with ConfigurationOfMetacello): The initialize method is using the old class "Preferences" (that is no longer present in Pharo 1.2). 2010/9/1 Tudor Girba <tudor.girba(a)gmail.com> What do you mean by script? Did you try with the configuration? Doru On Sep 1, 2010, at 11:12, Cyrille Delaunay <cy.delaunay(a)gmail.com> wrote:

Hello, Is moose loadable in Pharo 1.2 ? Is there a special script

somwhere to that?

_______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- www.tudorgirba.com "When people care, great things can happen."

Lukas Renggli

4:16 p.m.

Metacello is loading an ancient version of OB. References to Preferences have been removed a long time ago. However there is still a problem with the highlighting in Pharo 1.2. You only get a working environment if you do not load the package OB-Shout. Lukas On 1 September 2010 16:10, Tudor Girba <tudor.girba(a)gmail.com> wrote:

...

Hi Cyrille, That means that OB needs to be fixed :). Could you raise the issue on the pharo mailing list? Cheers, Doru On 1 Sep 2010, at 14:48, Cyrille Delaunay wrote:

-- www.tudorgirba.com "When people care, great things can happen." _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- Lukas Renggli www.lukas-renggli.ch

Cyrille Delaunay

2 Sep 2 Sep

12:20 p.m.

So a solution is to load in a version of OmniBrowser that is compatible with 1.2, before loading moose: (ConfigurationOfOmniBrowser project version: '1.1-baseline') load. Now, I have another error: The class MOEaselTextEditor from Mondrian-Easel re-declare the instance variable 'styler', which is already defined in its superclass PluggableTextMorph. 2010/9/1 Lukas Renggli <renggli(a)gmail.com>

...

with

> ConfigurationOfMetacello): > The initialize method is using the old class "Preferences" (that is no > longer present in Pharo 1.2). > > 2010/9/1 Tudor Girba <tudor.girba(a)gmail.com> > What do you mean by script? Did you try with the configuration? > > Doru > > > > On Sep 1, 2010, at 11:12, Cyrille Delaunay <cy.delaunay(a)gmail.com>

wrote:

-- Lukas Renggli www.lukas-renggli.ch _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Cyrille Delaunay

12:25 p.m.

...

Preferences have been removed a long time ago. However there is still a problem with the highlighting in Pharo 1.2. You only get a working environment if you do not load the package OB-Shout. Lukas On 1 September 2010 16:10, Tudor Girba <tudor.girba(a)gmail.com> wrote:

Hi Cyrille, That means that OB needs to be fixed :). Could you raise the issue on

the

pharo mailing list? Cheers, Doru On 1 Sep 2010, at 14:48, Cyrille Delaunay wrote: > When I try with the configuration, I get an error when loading the

class

> OBMercuryPanel (from the package OB-Standard, that seems to be loaded

with

wrote:

> > > Hello, > > Is moose loadable in Pharo 1.2 ? Is there a special script somwhere

> that? > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- Lukas Renggli www.lukas-renggli.ch _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Tudor Girba

12:54 p.m.

Yes, please rename it to shoutStyler. Cheers, Doru On 2 Sep 2010, at 12:25, Cyrille Delaunay wrote:

...

So that means that a 'styler' instance variable has been defined in PluggableTextMorph between pharo 1.1 and Pharo 1.2? Should we rename the Mondrian instance variable? 2010/9/2 Cyrille Delaunay <cy.delaunay(a)gmail.com> So a solution is to load in a version of OmniBrowser that is compatible with 1.2, before loading moose: (ConfigurationOfOmniBrowser project version: '1.1-baseline') load. Now, I have another error: The class MOEaselTextEditor from Mondrian-Easel re-declare the instance variable 'styler', which is already defined in its superclass PluggableTextMorph. 2010/9/1 Lukas Renggli <renggli(a)gmail.com> Metacello is loading an ancient version of OB. References to Preferences have been removed a long time ago. However there is still a problem with the highlighting in Pharo 1.2. You only get a working environment if you do not load the package OB-Shout. Lukas On 1 September 2010 16:10, Tudor Girba <tudor.girba(a)gmail.com> wrote:

Hi Cyrille, That means that OB needs to be fixed :). Could you raise the issue

on the

pharo mailing list? Cheers, Doru On 1 Sep 2010, at 14:48, Cyrille Delaunay wrote: > When I try with the configuration, I get an error when loading

the class

> OBMercuryPanel (from the package OB-Standard, that seems to be

loaded with

> ConfigurationOfMetacello): > The initialize method is using the old class "Preferences" (that

is no

> longer present in Pharo 1.2). > > 2010/9/1 Tudor Girba <tudor.girba(a)gmail.com> > What do you mean by script? Did you try with the configuration? > > Doru > > > > On Sep 1, 2010, at 11:12, Cyrille Delaunay

<cy.delaunay(a)gmail.com> wrote:

> > > Hello, > > Is moose loadable in Pharo 1.2 ? Is there a special script

somwhere to

that? _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- www.tudorgirba.com "When people care, great things can happen."

Cyrille Delaunay

1:08 p.m.

done 2010/9/2 Tudor Girba <tudor.girba(a)gmail.com>

...

Yes, please rename it to shoutStyler. Cheers, Doru On 2 Sep 2010, at 12:25, Cyrille Delaunay wrote: So that means that a 'styler' instance variable has been defined in

PluggableTextMorph between pharo 1.1 and Pharo 1.2? Should we rename the Mondrian instance variable? 2010/9/2 Cyrille Delaunay <cy.delaunay(a)gmail.com> So a solution is to load in a version of OmniBrowser that is compatible with 1.2, before loading moose: (ConfigurationOfOmniBrowser project version: '1.1-baseline') load. Now, I have another error: The class MOEaselTextEditor from Mondrian-Easel re-declare the instance variable 'styler', which is already defined in its superclass PluggableTextMorph. 2010/9/1 Lukas Renggli <renggli(a)gmail.com> Metacello is loading an ancient version of OB. References to Preferences have been removed a long time ago. However there is still a problem with the highlighting in Pharo 1.2. You only get a working environment if you do not load the package OB-Shout. Lukas On 1 September 2010 16:10, Tudor Girba <tudor.girba(a)gmail.com> wrote:

Hi Cyrille, That means that OB needs to be fixed :). Could you raise the issue on

the

pharo mailing list? Cheers, Doru On 1 Sep 2010, at 14:48, Cyrille Delaunay wrote: > When I try with the configuration, I get an error when loading the

class

> OBMercuryPanel (from the package OB-Standard, that seems to be loaded

with

wrote:

> > > Hello, > > Is moose loadable in Pharo 1.2 ? Is there a special script somwhere

Tudor Girba

1:17 p.m.

And does the loading work now? Doru On 2 Sep 2010, at 13:08, Cyrille Delaunay wrote:

...

done 2010/9/2 Tudor Girba <tudor.girba(a)gmail.com> Yes, please rename it to shoutStyler. Cheers, Doru On 2 Sep 2010, at 12:25, Cyrille Delaunay wrote: So that means that a 'styler' instance variable has been defined in PluggableTextMorph between pharo 1.1 and Pharo 1.2? Should we rename the Mondrian instance variable? 2010/9/2 Cyrille Delaunay <cy.delaunay(a)gmail.com> So a solution is to load in a version of OmniBrowser that is compatible with 1.2, before loading moose: (ConfigurationOfOmniBrowser project version: '1.1-baseline') load. Now, I have another error: The class MOEaselTextEditor from Mondrian-Easel re-declare the instance variable 'styler', which is already defined in its superclass PluggableTextMorph. 2010/9/1 Lukas Renggli <renggli(a)gmail.com> Metacello is loading an ancient version of OB. References to Preferences have been removed a long time ago. However there is still a problem with the highlighting in Pharo 1.2. You only get a working environment if you do not load the package OB-Shout. Lukas On 1 September 2010 16:10, Tudor Girba <tudor.girba(a)gmail.com> wrote:

Hi Cyrille, That means that OB needs to be fixed :). Could you raise the issue

on the

pharo mailing list? Cheers, Doru On 1 Sep 2010, at 14:48, Cyrille Delaunay wrote: > When I try with the configuration, I get an error when loading

the class

> OBMercuryPanel (from the package OB-Standard, that seems to be

loaded with

> ConfigurationOfMetacello): > The initialize method is using the old class "Preferences" (that

is no

<cy.delaunay(a)gmail.com> wrote:

> > > Hello, > > Is moose loadable in Pharo 1.2 ? Is there a special script

somwhere to

that? _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- www.tudorgirba.com "Being happy is a matter of choice."

Cyrille Delaunay

1:21 p.m.

No, same problem now with 'unstyledAcceptText' 2010/9/2 Tudor Girba <tudor.girba(a)gmail.com>

...

And does the loading work now? Doru On 2 Sep 2010, at 13:08, Cyrille Delaunay wrote: done

2010/9/2 Tudor Girba <tudor.girba(a)gmail.com> Yes, please rename it to shoutStyler. Cheers, Doru On 2 Sep 2010, at 12:25, Cyrille Delaunay wrote: So that means that a 'styler' instance variable has been defined in PluggableTextMorph between pharo 1.1 and Pharo 1.2? Should we rename the Mondrian instance variable? 2010/9/2 Cyrille Delaunay <cy.delaunay(a)gmail.com> So a solution is to load in a version of OmniBrowser that is compatible with 1.2, before loading moose: (ConfigurationOfOmniBrowser project version: '1.1-baseline') load. Now, I have another error: The class MOEaselTextEditor from Mondrian-Easel re-declare the instance variable 'styler', which is already defined in its superclass PluggableTextMorph. 2010/9/1 Lukas Renggli <renggli(a)gmail.com> Metacello is loading an ancient version of OB. References to Preferences have been removed a long time ago. However there is still a problem with the highlighting in Pharo 1.2. You only get a working environment if you do not load the package OB-Shout. Lukas On 1 September 2010 16:10, Tudor Girba <tudor.girba(a)gmail.com> wrote:

Hi Cyrille, That means that OB needs to be fixed :). Could you raise the issue on

the

pharo mailing list? Cheers, Doru On 1 Sep 2010, at 14:48, Cyrille Delaunay wrote: > When I try with the configuration, I get an error when loading the

class

> OBMercuryPanel (from the package OB-Standard, that seems to be loaded

with

wrote:

> > > Hello, > > Is moose loadable in Pharo 1.2 ? Is there a special script somwhere

-- www.tudorgirba.com "Being happy is a matter of choice." _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Cyrille Delaunay

2:22 p.m.

What is strange, is that there is only one reference to unstyledAcceptText, without affecting it a value. 2010/9/2 Cyrille Delaunay <cy.delaunay(a)gmail.com>

...

No, same problem now with 'unstyledAcceptText' 2010/9/2 Tudor Girba <tudor.girba(a)gmail.com>

And does the loading work now? Doru On 2 Sep 2010, at 13:08, Cyrille Delaunay wrote: done

Hi Cyrille, That means that OB needs to be fixed :). Could you raise the issue on

the

pharo mailing list? Cheers, Doru On 1 Sep 2010, at 14:48, Cyrille Delaunay wrote: > When I try with the configuration, I get an error when loading the

class

> OBMercuryPanel (from the package OB-Standard, that seems to be loaded

with

wrote:

> > > Hello, > > Is moose loadable in Pharo 1.2 ? Is there a special script somwhere

> > that? > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)iam.unibe.ch > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com "When people care, great things can happen." _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Alexandre Bergel

2:55 p.m.

Strange indeed. This method is apparently never called. This is related somehow to the completion (which does not work for me. I will contact Lukas). Alexandre On 2 Sep 2010, at 08:22, Cyrille Delaunay wrote:

...

What is strange, is that there is only one reference to unstyledAcceptText, without affecting it a value. 2010/9/2 Cyrille Delaunay <cy.delaunay(a)gmail.com> No, same problem now with 'unstyledAcceptText' 2010/9/2 Tudor Girba <tudor.girba(a)gmail.com> And does the loading work now? Doru On 2 Sep 2010, at 13:08, Cyrille Delaunay wrote: done 2010/9/2 Tudor Girba <tudor.girba(a)gmail.com> Yes, please rename it to shoutStyler. Cheers, Doru On 2 Sep 2010, at 12:25, Cyrille Delaunay wrote: So that means that a 'styler' instance variable has been defined in PluggableTextMorph between pharo 1.1 and Pharo 1.2? Should we rename the Mondrian instance variable? 2010/9/2 Cyrille Delaunay <cy.delaunay(a)gmail.com> So a solution is to load in a version of OmniBrowser that is compatible with 1.2, before loading moose: (ConfigurationOfOmniBrowser project version: '1.1-baseline') load. Now, I have another error: The class MOEaselTextEditor from Mondrian-Easel re-declare the instance variable 'styler', which is already defined in its superclass PluggableTextMorph. 2010/9/1 Lukas Renggli <renggli(a)gmail.com> Metacello is loading an ancient version of OB. References to Preferences have been removed a long time ago. However there is still a problem with the highlighting in Pharo 1.2. You only get a working environment if you do not load the package OB-Shout. Lukas On 1 September 2010 16:10, Tudor Girba <tudor.girba(a)gmail.com> wrote:

Hi Cyrille, That means that OB needs to be fixed :). Could you raise the issue on the pharo mailing list? Cheers, Doru On 1 Sep 2010, at 14:48, Cyrille Delaunay wrote:

-- Lukas Renggli www.lukas-renggli.ch _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com "When people care, great things can happen." _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com "Being happy is a matter of choice." _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

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

Cyrille Delaunay

3:47 p.m.

Now I have exactly the same problem with 'PluggableShoutMorph' in the package Shout (This package is loaded with ConfigurationOfPetitParser). PluggableShoutMorph (like MOEaselTextEditor) declare the two instance variables 'styler' and 'unstyledAcceptText' which are already declared in the superclass PluggableTextMorph (in Pharo 1.2). Maybe those variable have been integrated in the superclass for pharo 1.2 and are no longer usefull ? Anyone know? 2010/9/2 Alexandre Bergel <alexandre(a)bergel.eu>

...

What is strange, is that there is only one reference to

unstyledAcceptText, without affecting it a value.

2010/9/2 Cyrille Delaunay <cy.delaunay(a)gmail.com> No, same problem now with 'unstyledAcceptText' 2010/9/2 Tudor Girba <tudor.girba(a)gmail.com> And does the loading work now? Doru On 2 Sep 2010, at 13:08, Cyrille Delaunay wrote: done 2010/9/2 Tudor Girba <tudor.girba(a)gmail.com> Yes, please rename it to shoutStyler. Cheers, Doru On 2 Sep 2010, at 12:25, Cyrille Delaunay wrote: So that means that a 'styler' instance variable has been defined in

PluggableTextMorph between pharo 1.1 and Pharo 1.2? Should we rename the Mondrian instance variable?

2010/9/2 Cyrille Delaunay <cy.delaunay(a)gmail.com> So a solution is to load in a version of OmniBrowser that is compatible

with 1.2, before loading moose:

(ConfigurationOfOmniBrowser project version: '1.1-baseline') load. Now, I have another error: The class MOEaselTextEditor from Mondrian-Easel re-declare the instance

variable 'styler', which is already defined in its superclass PluggableTextMorph.

2010/9/1 Lukas Renggli <renggli(a)gmail.com> Metacello is loading an ancient version of OB. References to Preferences have been removed a long time ago. However there is still a problem with the highlighting in Pharo 1.2. You only get a working environment if you do not load the package OB-Shout. Lukas On 1 September 2010 16:10, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Hi Cyrille, > > That means that OB needs to be fixed :). Could you raise the issue on

the

> pharo mailing list? > > Cheers, > Doru > > > On 1 Sep 2010, at 14:48, Cyrille Delaunay wrote: > >> When I try with the configuration, I get an error when loading the

class

>> OBMercuryPanel (from the package OB-Standard, that seems to be loaded

with

>> ConfigurationOfMetacello): >> The initialize method is using the old class "Preferences" (that is no >> longer present in Pharo 1.2). >> >> 2010/9/1 Tudor Girba <tudor.girba(a)gmail.com> >> What do you mean by script? Did you try with the configuration? >> >> Doru >> >> >> >> On Sep 1, 2010, at 11:12, Cyrille Delaunay <cy.delaunay(a)gmail.com>

wrote:

>> >> > Hello, >> > Is moose loadable in Pharo 1.2 ? Is there a special script somwhere

Cyrille Delaunay

4:43 p.m.

...

somehow to the completion (which does not work for me. I will contact Lukas). Alexandre On 2 Sep 2010, at 08:22, Cyrille Delaunay wrote:

What is strange, is that there is only one reference to

unstyledAcceptText, without affecting it a value.

PluggableTextMorph between pharo 1.1 and Pharo 1.2? Should we rename the Mondrian instance variable?

2010/9/2 Cyrille Delaunay <cy.delaunay(a)gmail.com> So a solution is to load in a version of OmniBrowser that is compatible

with 1.2, before loading moose:

(ConfigurationOfOmniBrowser project version: '1.1-baseline') load. Now, I have another error: The class MOEaselTextEditor from Mondrian-Easel re-declare the instance

variable 'styler', which is already defined in its superclass PluggableTextMorph.

the

> pharo mailing list? > > Cheers, > Doru > > > On 1 Sep 2010, at 14:48, Cyrille Delaunay wrote: > >> When I try with the configuration, I get an error when loading the

class

>> OBMercuryPanel (from the package OB-Standard, that seems to be loaded

with

>> ConfigurationOfMetacello): >> The initialize method is using the old class "Preferences" (that is

>> longer present in Pharo 1.2). >> >> 2010/9/1 Tudor Girba <tudor.girba(a)gmail.com> >> What do you mean by script? Did you try with the configuration? >> >> Doru >> >> >> >> On Sep 1, 2010, at 11:12, Cyrille Delaunay <cy.delaunay(a)gmail.com>

wrote:

>> >> > Hello, >> > Is moose loadable in Pharo 1.2 ? Is there a special script somwhere

Tudor Girba

4:46 p.m.

No, because if you remove it you break 1.1. I would suggest to just rename those variables. Cheers, Doru On 2 Sep 2010, at 16:43, Cyrille Delaunay wrote:

...

There is already an issue for that: http://code.google.com/p/pharo/issues/detail?id=2734&q=PluggableShoutMo… Should we (I) remove those variables from PluggableShoutMorph? 2010/9/2 Cyrille Delaunay <cy.delaunay(a)gmail.com> Now I have exactly the same problem with 'PluggableShoutMorph' in the package Shout (This package is loaded with ConfigurationOfPetitParser). PluggableShoutMorph (like MOEaselTextEditor) declare the two instance variables 'styler' and 'unstyledAcceptText' which are already declared in the superclass PluggableTextMorph (in Pharo 1.2). Maybe those variable have been integrated in the superclass for pharo 1.2 and are no longer usefull ? Anyone know? 2010/9/2 Alexandre Bergel <alexandre(a)bergel.eu> Strange indeed. This method is apparently never called. This is related somehow to the completion (which does not work for me. I will contact Lukas). Alexandre On 2 Sep 2010, at 08:22, Cyrille Delaunay wrote:

What is strange, is that there is only one reference to

unstyledAcceptText, without affecting it a value.

in PluggableTextMorph between pharo 1.1 and Pharo 1.2? Should we rename the Mondrian instance variable?

2010/9/2 Cyrille Delaunay <cy.delaunay(a)gmail.com> So a solution is to load in a version of OmniBrowser that is

compatible with 1.2, before loading moose:

(ConfigurationOfOmniBrowser project version: '1.1-baseline') load. Now, I have another error: The class MOEaselTextEditor from Mondrian-Easel re-declare the

instance variable 'styler', which is already defined in its superclass PluggableTextMorph.

2010/9/1 Lukas Renggli <renggli(a)gmail.com> Metacello is loading an ancient version of OB. References to Preferences have been removed a long time ago. However there is

still

a problem with the highlighting in Pharo 1.2. You only get a working environment if you do not load the package OB-Shout. Lukas On 1 September 2010 16:10, Tudor Girba <tudor.girba(a)gmail.com>

wrote:

> Hi Cyrille, > > That means that OB needs to be fixed :). Could you raise the

issue on the

> pharo mailing list? > > Cheers, > Doru > > > On 1 Sep 2010, at 14:48, Cyrille Delaunay wrote: > >> When I try with the configuration, I get an error when loading

the class

>> OBMercuryPanel (from the package OB-Standard, that seems to be

loaded with

>> ConfigurationOfMetacello): >> The initialize method is using the old class

"Preferences" (that is no

<cy.delaunay(a)gmail.com> wrote:

>> >> > Hello, >> > Is moose loadable in Pharo 1.2 ? Is there a special script

somwhere to

-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- www.tudorgirba.com "If you interrupt the barber while he is cutting your hair, you will end up with a messy haircut."

Simon Denier

4:51 p.m.

On 2 sept. 2010, at 16:46, Tudor Girba wrote:

...

No, because if you remove it you break 1.1. I would suggest to just rename those variables.

mmm, since 1.1 is out, it should not depend on the latest Shout package but on a specific version. Thus, removing these variables seems the way to go as indicated in the issue.

...

Cheers, Doru On 2 Sep 2010, at 16:43, Cyrille Delaunay wrote:

Hi Cyrille, That means that OB needs to be fixed :). Could you raise the issue on the pharo mailing list? Cheers, Doru On 1 Sep 2010, at 14:48, Cyrille Delaunay wrote: > When I try with the configuration, I get an error when loading the class > OBMercuryPanel (from the package OB-Standard, that seems to be loaded with > ConfigurationOfMetacello): > The initialize method is using the old class "Preferences" (that is no > longer present in Pharo 1.2). > > 2010/9/1 Tudor Girba <tudor.girba(a)gmail.com> > What do you mean by script? Did you try with the configuration? > > Doru > > > > On Sep 1, 2010, at 11:12, Cyrille Delaunay <cy.delaunay(a)gmail.com> wrote: > > > Hello, > > Is moose loadable in Pharo 1.2 ? Is there a special script somwhere to > > that? > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)iam.unibe.ch > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com "When people care, great things can happen." _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- www.tudorgirba.com "If you interrupt the barber while he is cutting your hair, you will end up with a messy haircut." _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- Simon

4978

days inactive

4979

days old

moose-dev@list.inf.unibe.ch

Manage subscription

16 comments

5 participants

tags (0)

participants (5)

Alexandre Bergel
Cyrille Delaunay
Lukas Renggli
Simon Denier
Tudor Girba