load moose in Pharo1.2

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
19 messages Options
Reply | Threaded
Open this post in threaded view
|

load moose in Pharo1.2

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

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: load moose in Pharo1.2

Tudor Girba
What do you mean by script? Did you try with the configuration?

Doru



On Sep 1, 2010, at 11:12, Cyrille Delaunay <[hidden email]> wrote:

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

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: load moose in Pharo1.2

cdelaunay
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 <[hidden email]>
What do you mean by script? Did you try with the configuration?

Doru



On Sep 1, 2010, at 11:12, Cyrille Delaunay <[hidden email]> wrote:

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

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


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: load moose in Pharo1.2

Tudor Girba
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 <[hidden email]>
> What do you mean by script? Did you try with the configuration?
>
> Doru
>
>
>
> On Sep 1, 2010, at 11:12, Cyrille Delaunay <[hidden email]>  
> wrote:
>
> > Hello,
> > Is moose loadable in Pharo 1.2 ? Is there a special script  
> somwhere to that?
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"When people care, great things can happen."



_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: load moose in Pharo1.2

Lukas Renggli
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 <[hidden email]> 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 <[hidden email]>
>> What do you mean by script? Did you try with the configuration?
>>
>> Doru
>>
>>
>>
>> On Sep 1, 2010, at 11:12, Cyrille Delaunay <[hidden email]> wrote:
>>
>> > Hello,
>> > Is moose loadable in Pharo 1.2 ? Is there a special script somwhere to
>> > that?
>> > _______________________________________________
>> > Moose-dev mailing list
>> > [hidden email]
>> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "When people care, great things can happen."
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>



--
Lukas Renggli
www.lukas-renggli.ch
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: load moose in Pharo1.2

cdelaunay
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 <[hidden email]>
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 <[hidden email]> 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 <[hidden email]>
>> What do you mean by script? Did you try with the configuration?
>>
>> Doru
>>
>>
>>
>> On Sep 1, 2010, at 11:12, Cyrille Delaunay <[hidden email]> wrote:
>>
>> > Hello,
>> > Is moose loadable in Pharo 1.2 ? Is there a special script somwhere to
>> > that?
>> > _______________________________________________
>> > Moose-dev mailing list
>> > [hidden email]
>> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "When people care, great things can happen."
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>



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


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: load moose in Pharo1.2

cdelaunay
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 <[hidden email]>
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 <[hidden email]>

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 <[hidden email]> 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 <[hidden email]>
>> What do you mean by script? Did you try with the configuration?
>>
>> Doru
>>
>>
>>
>> On Sep 1, 2010, at 11:12, Cyrille Delaunay <[hidden email]> wrote:
>>
>> > Hello,
>> > Is moose loadable in Pharo 1.2 ? Is there a special script somwhere to
>> > that?
>> > _______________________________________________
>> > Moose-dev mailing list
>> > [hidden email]
>> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "When people care, great things can happen."
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>



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



_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: load moose in Pharo1.2

Tudor Girba
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 <[hidden email]>
> 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 <[hidden email]>
>
> 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 <[hidden email]> 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 <[hidden email]>
> >> What do you mean by script? Did you try with the configuration?
> >>
> >> Doru
> >>
> >>
> >>
> >> On Sep 1, 2010, at 11:12, Cyrille Delaunay  
> <[hidden email]> wrote:
> >>
> >> > Hello,
> >> > Is moose loadable in Pharo 1.2 ? Is there a special script  
> somwhere to
> >> > that?
> >> > _______________________________________________
> >> > Moose-dev mailing list
> >> > [hidden email]
> >> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >>
> >> _______________________________________________
> >> Moose-dev mailing list
> >> [hidden email]
> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >>
> >> _______________________________________________
> >> Moose-dev mailing list
> >> [hidden email]
> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> > --
> > www.tudorgirba.com
> >
> > "When people care, great things can happen."
> >
> >
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
>
>
>
> --
> Lukas Renggli
> www.lukas-renggli.ch
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"When people care, great things can happen."



_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: load moose in Pharo1.2

cdelaunay
done

2010/9/2 Tudor Girba <[hidden email]>
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 <[hidden email]>
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 <[hidden email]>

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 <[hidden email]> 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 <[hidden email]>
>> What do you mean by script? Did you try with the configuration?
>>
>> Doru
>>
>>
>>
>> On Sep 1, 2010, at 11:12, Cyrille Delaunay <[hidden email]> wrote:
>>
>> > Hello,
>> > Is moose loadable in Pharo 1.2 ? Is there a special script somwhere to
>> > that?
>> > _______________________________________________
>> > Moose-dev mailing list
>> > [hidden email]
>> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "When people care, great things can happen."
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>



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


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

--
www.tudorgirba.com

"When people care, great things can happen."



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


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: load moose in Pharo1.2

Tudor Girba
And does the loading work now?

Doru

On 2 Sep 2010, at 13:08, Cyrille Delaunay wrote:

> done
>
> 2010/9/2 Tudor Girba <[hidden email]>
> 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 <[hidden email]>
> 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 <[hidden email]>
>
> 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 <[hidden email]> 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 <[hidden email]>
> >> What do you mean by script? Did you try with the configuration?
> >>
> >> Doru
> >>
> >>
> >>
> >> On Sep 1, 2010, at 11:12, Cyrille Delaunay  
> <[hidden email]> wrote:
> >>
> >> > Hello,
> >> > Is moose loadable in Pharo 1.2 ? Is there a special script  
> somwhere to
> >> > that?
> >> > _______________________________________________
> >> > Moose-dev mailing list
> >> > [hidden email]
> >> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >>
> >> _______________________________________________
> >> Moose-dev mailing list
> >> [hidden email]
> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >>
> >> _______________________________________________
> >> Moose-dev mailing list
> >> [hidden email]
> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> > --
> > www.tudorgirba.com
> >
> > "When people care, great things can happen."
> >
> >
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
>
>
>
> --
> Lukas Renggli
> www.lukas-renggli.ch
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "When people care, great things can happen."
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"Being happy is a matter of choice."



_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: load moose in Pharo1.2

cdelaunay
No, same problem now with 'unstyledAcceptText'

2010/9/2 Tudor Girba <[hidden email]>
And does the loading work now?

Doru


On 2 Sep 2010, at 13:08, Cyrille Delaunay wrote:

done

2010/9/2 Tudor Girba <[hidden email]>
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 <[hidden email]>
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 <[hidden email]>

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 <[hidden email]> 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 <[hidden email]>
>> What do you mean by script? Did you try with the configuration?
>>
>> Doru
>>
>>
>>
>> On Sep 1, 2010, at 11:12, Cyrille Delaunay <[hidden email]> wrote:
>>
>> > Hello,
>> > Is moose loadable in Pharo 1.2 ? Is there a special script somwhere to
>> > that?
>> > _______________________________________________
>> > Moose-dev mailing list
>> > [hidden email]
>> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "When people care, great things can happen."
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>



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


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

--
www.tudorgirba.com

"When people care, great things can happen."



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

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

--
www.tudorgirba.com

"Being happy is a matter of choice."




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


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: load moose in Pharo1.2

cdelaunay
What is strange, is that there is only one reference to unstyledAcceptText, without affecting it a value.

2010/9/2 Cyrille Delaunay <[hidden email]>
No, same problem now with 'unstyledAcceptText'


2010/9/2 Tudor Girba <[hidden email]>
And does the loading work now?

Doru


On 2 Sep 2010, at 13:08, Cyrille Delaunay wrote:

done

2010/9/2 Tudor Girba <[hidden email]>
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 <[hidden email]>
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 <[hidden email]>

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 <[hidden email]> 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 <[hidden email]>
>> What do you mean by script? Did you try with the configuration?
>>
>> Doru
>>
>>
>>
>> On Sep 1, 2010, at 11:12, Cyrille Delaunay <[hidden email]> wrote:
>>
>> > Hello,
>> > Is moose loadable in Pharo 1.2 ? Is there a special script somwhere to
>> > that?
>> > _______________________________________________
>> > Moose-dev mailing list
>> > [hidden email]
>> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "When people care, great things can happen."
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>



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


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

--
www.tudorgirba.com

"When people care, great things can happen."



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

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

--
www.tudorgirba.com

"Being happy is a matter of choice."




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



_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: load moose in Pharo1.2

Alexandre Bergel
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 <[hidden email]>
> No, same problem now with 'unstyledAcceptText'
>
>
> 2010/9/2 Tudor Girba <[hidden email]>
> And does the loading work now?
>
> Doru
>
>
> On 2 Sep 2010, at 13:08, Cyrille Delaunay wrote:
>
> done
>
> 2010/9/2 Tudor Girba <[hidden email]>
> 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 <[hidden email]>
> 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 <[hidden email]>
>
> 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 <[hidden email]> 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 <[hidden email]>
> >> What do you mean by script? Did you try with the configuration?
> >>
> >> Doru
> >>
> >>
> >>
> >> On Sep 1, 2010, at 11:12, Cyrille Delaunay <[hidden email]> wrote:
> >>
> >> > Hello,
> >> > Is moose loadable in Pharo 1.2 ? Is there a special script somwhere to
> >> > that?
> >> > _______________________________________________
> >> > Moose-dev mailing list
> >> > [hidden email]
> >> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >>
> >> _______________________________________________
> >> Moose-dev mailing list
> >> [hidden email]
> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >>
> >> _______________________________________________
> >> Moose-dev mailing list
> >> [hidden email]
> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> > --
> > www.tudorgirba.com
> >
> > "When people care, great things can happen."
> >
> >
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
>
>
>
> --
> Lukas Renggli
> www.lukas-renggli.ch
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "When people care, great things can happen."
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "Being happy is a matter of choice."
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

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






_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: load moose in Pharo1.2

cdelaunay
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 <[hidden email]>
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 <[hidden email]>
> No, same problem now with 'unstyledAcceptText'
>
>
> 2010/9/2 Tudor Girba <[hidden email]>
> And does the loading work now?
>
> Doru
>
>
> On 2 Sep 2010, at 13:08, Cyrille Delaunay wrote:
>
> done
>
> 2010/9/2 Tudor Girba <[hidden email]>
> 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 <[hidden email]>
> 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 <[hidden email]>
>
> 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 <[hidden email]> 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 <[hidden email]>
> >> What do you mean by script? Did you try with the configuration?
> >>
> >> Doru
> >>
> >>
> >>
> >> On Sep 1, 2010, at 11:12, Cyrille Delaunay <[hidden email]> wrote:
> >>
> >> > Hello,
> >> > Is moose loadable in Pharo 1.2 ? Is there a special script somwhere to
> >> > that?
> >> > _______________________________________________
> >> > Moose-dev mailing list
> >> > [hidden email]
> >> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >>
> >> _______________________________________________
> >> Moose-dev mailing list
> >> [hidden email]
> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >>
> >> _______________________________________________
> >> Moose-dev mailing list
> >> [hidden email]
> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> > --
> > www.tudorgirba.com
> >
> > "When people care, great things can happen."
> >
> >
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
>
>
>
> --
> Lukas Renggli
> www.lukas-renggli.ch
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "When people care, great things can happen."
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "Being happy is a matter of choice."
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

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






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


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: load moose in Pharo1.2

cdelaunay
There is already an issue for that:


Should we (I) remove those variables from PluggableShoutMorph?

2010/9/2 Cyrille Delaunay <[hidden email]>
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 <[hidden email]>

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 <[hidden email]>
> No, same problem now with 'unstyledAcceptText'
>
>
> 2010/9/2 Tudor Girba <[hidden email]>
> And does the loading work now?
>
> Doru
>
>
> On 2 Sep 2010, at 13:08, Cyrille Delaunay wrote:
>
> done
>
> 2010/9/2 Tudor Girba <[hidden email]>
> 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 <[hidden email]>
> 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 <[hidden email]>
>
> 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 <[hidden email]> 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 <[hidden email]>
> >> What do you mean by script? Did you try with the configuration?
> >>
> >> Doru
> >>
> >>
> >>
> >> On Sep 1, 2010, at 11:12, Cyrille Delaunay <[hidden email]> wrote:
> >>
> >> > Hello,
> >> > Is moose loadable in Pharo 1.2 ? Is there a special script somwhere to
> >> > that?
> >> > _______________________________________________
> >> > Moose-dev mailing list
> >> > [hidden email]
> >> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >>
> >> _______________________________________________
> >> Moose-dev mailing list
> >> [hidden email]
> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >>
> >> _______________________________________________
> >> Moose-dev mailing list
> >> [hidden email]
> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> > --
> > www.tudorgirba.com
> >
> > "When people care, great things can happen."
> >
> >
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
>
>
>
> --
> Lukas Renggli
> www.lukas-renggli.ch
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "When people care, great things can happen."
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "Being happy is a matter of choice."
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

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






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



_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: load moose in Pharo1.2

Tudor Girba
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=PluggableShoutMorph&colspec=ID%20Type%20Status%20Summary%20Milestone%20Difficulty
>
> Should we (I) remove those variables from PluggableShoutMorph?
>
> 2010/9/2 Cyrille Delaunay <[hidden email]>
> 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 <[hidden email]>
>
> 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 <[hidden email]>
> > No, same problem now with 'unstyledAcceptText'
> >
> >
> > 2010/9/2 Tudor Girba <[hidden email]>
> > And does the loading work now?
> >
> > Doru
> >
> >
> > On 2 Sep 2010, at 13:08, Cyrille Delaunay wrote:
> >
> > done
> >
> > 2010/9/2 Tudor Girba <[hidden email]>
> > 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 <[hidden email]>
> > 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 <[hidden email]>
> >
> > 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 <[hidden email]>  
> 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 <[hidden email]>
> > >> What do you mean by script? Did you try with the configuration?
> > >>
> > >> Doru
> > >>
> > >>
> > >>
> > >> On Sep 1, 2010, at 11:12, Cyrille Delaunay  
> <[hidden email]> wrote:
> > >>
> > >> > Hello,
> > >> > Is moose loadable in Pharo 1.2 ? Is there a special script  
> somwhere to
> > >> > that?
> > >> > _______________________________________________
> > >> > Moose-dev mailing list
> > >> > [hidden email]
> > >> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> > >>
> > >> _______________________________________________
> > >> Moose-dev mailing list
> > >> [hidden email]
> > >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> > >>
> > >> _______________________________________________
> > >> Moose-dev mailing list
> > >> [hidden email]
> > >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> > >
> > > --
> > > www.tudorgirba.com
> > >
> > > "When people care, great things can happen."
> > >
> > >
> > >
> > > _______________________________________________
> > > Moose-dev mailing list
> > > [hidden email]
> > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> > >
> >
> >
> >
> > --
> > Lukas Renggli
> > www.lukas-renggli.ch
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> > --
> > www.tudorgirba.com
> >
> > "When people care, great things can happen."
> >
> >
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> > --
> > www.tudorgirba.com
> >
> > "Being happy is a matter of choice."
> >
> >
> >
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> 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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: load moose in Pharo1.2

Simon Denier-3

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:
>
>> There is already an issue for that:
>>
>> http://code.google.com/p/pharo/issues/detail?id=2734&q=PluggableShoutMorph&colspec=ID%20Type%20Status%20Summary%20Milestone%20Difficulty
>>
>> Should we (I) remove those variables from PluggableShoutMorph?
>>
>> 2010/9/2 Cyrille Delaunay <[hidden email]>
>> 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 <[hidden email]>
>>
>> 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 <[hidden email]>
>> > No, same problem now with 'unstyledAcceptText'
>> >
>> >
>> > 2010/9/2 Tudor Girba <[hidden email]>
>> > And does the loading work now?
>> >
>> > Doru
>> >
>> >
>> > On 2 Sep 2010, at 13:08, Cyrille Delaunay wrote:
>> >
>> > done
>> >
>> > 2010/9/2 Tudor Girba <[hidden email]>
>> > 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 <[hidden email]>
>> > 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 <[hidden email]>
>> >
>> > 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 <[hidden email]> 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 <[hidden email]>
>> > >> What do you mean by script? Did you try with the configuration?
>> > >>
>> > >> Doru
>> > >>
>> > >>
>> > >>
>> > >> On Sep 1, 2010, at 11:12, Cyrille Delaunay <[hidden email]> wrote:
>> > >>
>> > >> > Hello,
>> > >> > Is moose loadable in Pharo 1.2 ? Is there a special script somwhere to
>> > >> > that?
>> > >> > _______________________________________________
>> > >> > Moose-dev mailing list
>> > >> > [hidden email]
>> > >> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>> > >>
>> > >> _______________________________________________
>> > >> Moose-dev mailing list
>> > >> [hidden email]
>> > >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>> > >>
>> > >> _______________________________________________
>> > >> Moose-dev mailing list
>> > >> [hidden email]
>> > >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>> > >
>> > > --
>> > > www.tudorgirba.com
>> > >
>> > > "When people care, great things can happen."
>> > >
>> > >
>> > >
>> > > _______________________________________________
>> > > Moose-dev mailing list
>> > > [hidden email]
>> > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>> > >
>> >
>> >
>> >
>> > --
>> > Lukas Renggli
>> > www.lukas-renggli.ch
>> > _______________________________________________
>> > Moose-dev mailing list
>> > [hidden email]
>> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>> >
>> >
>> > _______________________________________________
>> > Moose-dev mailing list
>> > [hidden email]
>> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>> >
>> > --
>> > www.tudorgirba.com
>> >
>> > "When people care, great things can happen."
>> >
>> >
>> >
>> > _______________________________________________
>> > Moose-dev mailing list
>> > [hidden email]
>> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>> >
>> > _______________________________________________
>> > Moose-dev mailing list
>> > [hidden email]
>> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>> >
>> > --
>> > www.tudorgirba.com
>> >
>> > "Being happy is a matter of choice."
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > Moose-dev mailing list
>> > [hidden email]
>> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>> >
>> >
>> > _______________________________________________
>> > Moose-dev mailing list
>> > [hidden email]
>> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel  http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> 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
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
 Simon




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-project] Re: load moose in Pharo1.2

Tudor Girba
In reply to this post by Tudor Girba
I was more considering the issue from a transitory point of view. But,  
indeed, given that 1.1 is out, there is no point in being backward  
compatible anymore.

Cheers,
Doru


On 2 Sep 2010, at 16:51, Guillermo Polito wrote:

> But, that's why we have metacello configs? don't we?  We have to use  
> a specific version for 1.1 and another one for 1.2.
>
> If we want to download the lastVersion always, It's not going to  
> work never :).
>
> On Thu, Sep 2, 2010 at 11:46 AM, Tudor Girba <[hidden email]>  
> wrote:
> 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=PluggableShoutMorph&colspec=ID%20Type%20Status%20Summary%20Milestone%20Difficulty
>
> Should we (I) remove those variables from PluggableShoutMorph?
>
> 2010/9/2 Cyrille Delaunay <[hidden email]>
> 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 <[hidden email]>
>
> 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 <[hidden email]>
> > No, same problem now with 'unstyledAcceptText'
> >
> >
> > 2010/9/2 Tudor Girba <[hidden email]>
> > And does the loading work now?
> >
> > Doru
> >
> >
> > On 2 Sep 2010, at 13:08, Cyrille Delaunay wrote:
> >
> > done
> >
> > 2010/9/2 Tudor Girba <[hidden email]>
> > 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 <[hidden email]>
> > 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 <[hidden email]>
> >
> > 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 <[hidden email]>  
> 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 <[hidden email]>
> > >> What do you mean by script? Did you try with the configuration?
> > >>
> > >> Doru
> > >>
> > >>
> > >>
> > >> On Sep 1, 2010, at 11:12, Cyrille Delaunay  
> <[hidden email]> wrote:
> > >>
> > >> > Hello,
> > >> > Is moose loadable in Pharo 1.2 ? Is there a special script  
> somwhere to
> > >> > that?
> > >> > _______________________________________________
> > >> > Moose-dev mailing list
> > >> > [hidden email]
> > >> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> > >>
> > >> _______________________________________________
> > >> Moose-dev mailing list
> > >> [hidden email]
> > >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> > >>
> > >> _______________________________________________
> > >> Moose-dev mailing list
> > >> [hidden email]
> > >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> > >
> > > --
> > > www.tudorgirba.com
> > >
> > > "When people care, great things can happen."
> > >
> > >
> > >
> > > _______________________________________________
> > > Moose-dev mailing list
> > > [hidden email]
> > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> > >
> >
> >
> >
> > --
> > Lukas Renggli
> > www.lukas-renggli.ch
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> > --
> > www.tudorgirba.com
> >
> > "When people care, great things can happen."
> >
> >
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> > --
> > www.tudorgirba.com
> >
> > "Being happy is a matter of choice."
> >
> >
> >
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> 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."
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

--
www.tudorgirba.com

"When people care, great things can happen."



_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-project] Re: load moose in Pharo1.2

cdelaunay
I removed them. Tell me if there is any problem

2010/9/2 Tudor Girba <[hidden email]>
I was more considering the issue from a transitory point of view. But, indeed, given that 1.1 is out, there is no point in being backward compatible anymore.

Cheers,
Doru



On 2 Sep 2010, at 16:51, Guillermo Polito wrote:

But, that's why we have metacello configs? don't we?  We have to use a specific version for 1.1 and another one for 1.2.

If we want to download the lastVersion always, It's not going to work never :).

On Thu, Sep 2, 2010 at 11:46 AM, Tudor Girba <[hidden email]> wrote:
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=PluggableShoutMorph&colspec=ID%20Type%20Status%20Summary%20Milestone%20Difficulty

Should we (I) remove those variables from PluggableShoutMorph?

2010/9/2 Cyrille Delaunay <[hidden email]>
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 <[hidden email]>

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 <[hidden email]>
> No, same problem now with 'unstyledAcceptText'
>
>
> 2010/9/2 Tudor Girba <[hidden email]>
> And does the loading work now?
>
> Doru
>
>
> On 2 Sep 2010, at 13:08, Cyrille Delaunay wrote:
>
> done
>
> 2010/9/2 Tudor Girba <[hidden email]>
> 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 <[hidden email]>
> 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 <[hidden email]>
>
> 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 <[hidden email]> 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 <[hidden email]>
> >> What do you mean by script? Did you try with the configuration?
> >>
> >> Doru
> >>
> >>
> >>
> >> On Sep 1, 2010, at 11:12, Cyrille Delaunay <[hidden email]> wrote:
> >>
> >> > Hello,
> >> > Is moose loadable in Pharo 1.2 ? Is there a special script somwhere to
> >> > that?
> >> > _______________________________________________
> >> > Moose-dev mailing list
> >> > [hidden email]
> >> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >>
> >> _______________________________________________
> >> Moose-dev mailing list
> >> [hidden email]
> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >>
> >> _______________________________________________
> >> Moose-dev mailing list
> >> [hidden email]
> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> > --
> > www.tudorgirba.com
> >
> > "When people care, great things can happen."
> >
> >
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
>
>
>
> --
> Lukas Renggli
> www.lukas-renggli.ch
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "When people care, great things can happen."
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "Being happy is a matter of choice."
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

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






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


_______________________________________________
Moose-dev mailing list
[hidden email]
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."


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

--
www.tudorgirba.com

"When people care, great things can happen."



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


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