- Pharo-dev - lists.pharo.org

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

by Guillermo Polito

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 <tudor.girba(a)gmail.com> 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&… >> >> 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. >> > >> > 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 >> 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 >> > > >> > >> > >> > >> > -- >> > 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 >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> _______________________________________________ >> 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." > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 2, 2010

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

by 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&… > > 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. > > > > 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 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 > > > > > > > > > > > -- > > 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 > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > 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."

Sept. 2, 2010

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

by Cyrille Delaunay

There is already an issue for that: http://code.google.com/p/pharo/issues/detail?id=2734&q=PluggableShoutMorph&… 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. >> > >> > 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 >> 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 >> > > >> > >> > >> > >> > -- >> > 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 >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> > >

Sept. 2, 2010

[Pharo-project] Object visitor

by Martin Dias

Hi, We want to do some processing over the graph of object references. Do you recommend an implementation of visitor pattern to iterate object instance variables? Best regards, Martin and Tristan

Sept. 2, 2010

Re: [Pharo-project] seaside3+pharo1.1+cog?

by Tudor Girba

Hi, I used this since a couple of weeks and it looks to be working just fine. Cheers, Doru On 2 Sep 2010, at 16:31, Esteban Lorenzano wrote: > Hi, > I wonder if this combination is working... I need to do a quick > prototype and I want to make it using this combination. > I know there were some problems with seaside+cog... but maybe they > are fixed now :) > > Cheers, > Esteban > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "Every thing has its own flow."

Sept. 2, 2010

[Pharo-project] seaside3+pharo1.1+cog?

by Esteban Lorenzano

Hi, I wonder if this combination is working... I need to do a quick prototype and I want to make it using this combination. I know there were some problems with seaside+cog... but maybe they are fixed now :) Cheers, Esteban

Sept. 2, 2010

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

by Cyrille Delaunay

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. > > > > 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 > 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 > > > > > > > > > > > -- > > 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 > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >

Sept. 2, 2010

[Pharo-project] TextLint questions and feedback

by Mariano Martinez Peck

Hi. First, please let me know if this is the correct place to talk about TextLint. I've just used for one paper I am writing and I have some questions/feedback. I am using the one click image. 1) The "An Rule" could be a little more smart and detects commands. For example, in my latex I have " an \emph{inner object}" and that was detected by the rule, althought I shouldn't. So...detecting the slash and ignore what it surrounded by {} would be nice for this rule. 2) When I edit the code inside TextLint and I save it, two bad things happens: 2.a) I lost focus of the text, as it moves when it finishing saving. The line I edited goes to the end of the text area. It would be great if nothing moves nor to loose focus when saving. 2.b) sometimes (I cannot reproduce) the order of the rules changes...and this is not good because I was going in order, one by one, and suddenly they are re-ordered. Maybe you are using a Set for that? using a simple OrderedCollection could help. 3) If you edit the text (and it differs in the amount of characters), and DO NOT save it, the following color highlighting are moved. It seems you keep the position in the file, and until it is saved, rules results are pointing to "unupdated" file. Of course, when I save the file, they are correct. I guess this is from a performance point of view, but maybe you have a little hack to do and make it better. 4) The rule "no white space before punctuation mark" showed me things I didn't understand. For example, it says this line there is a "," (comma) : \item[ Shared object ] In the case of the \emph{shared objects}, it is almost the same as in the \emph{inner objects}. An ..... 5) Rules comments clearer. For example, when you say "Avoid using a lot, it weakens the sentence" It would be better to put "Avoid using "a lot", it weakens the sentence" or "Avoid using *a lot*, it weakens the sentence" or something to clearly mark the words not to use. Because sometimes the words are confused with the context. Or this one: "After an only words beginning with a vowel are allowed. " should be "After "an" only words beginning with a vowel are allowed." 6) For the rules of long sentences/paragraph it would be nice to ignore \fotenote{} 7) Maybe this link is of interest for you: http://matt.might.net/articles/shell-scripts-for-passive-voice-weasel-words… Apart from all these things, the tool is very useful and I like it. thanks Mariano

Sept. 2, 2010

[Pharo-project] EntryFieldMorph enhancements

by Fernando olivero

SLICE-Issue-2903-EntryFieldHasErrorAndGrayedLabel-FernandoOlivero.1 The idea is to have specialized Editors that know the validity of the contents being edited. For example i'm working on a CompletionEditor, which knows if the contents are a valid class of the system. For now i've added the method Editor>>hasError ^ false. I will push the CompletionEditor, and the CompletionEntryFieldMorph in a new issue. I've also added the grayed out background label , setted by sending #initialContents. Fernando

Sept. 2, 2010

Re: [Pharo-project] [Moose-dev] Re: Problems in loading GLORP

by Mariano Martinez Peck

On Thu, Sep 2, 2010 at 1:23 PM, Alberto Bacchelli <alberto.bacchelli(a)usi.ch>wrote: > > BTW, last week I wrote a metacello configuration group to load GlorpDBX >> with the native postgres driver. You can evaluate first: >> >> >> Gofer new >> squeaksource: 'MetacelloRepository'; >> package: 'ConfigurationOfGlorpDBX'; >> load. >> >> and then >> >> (ConfigurationOfGlorpDBX project version: '1.2') load: 'All with >> PostgreSQL native >> >> > Hi, > > I followed your instructions and I've been able to load GLORP > on a Moose Nightly Built image [1]. > > I run the 844 tests. 839 of them passed (wow), > 4 failed and 1 generated an error. > These are the problematic ones: > > GlorpManyToManyDBTest>>#testReadNodeAndDeleteChildWithSaveAndContinue > GlorpRowMapForMementosCollectionTest>>#testRBSmallDictionary > GlorpDateTest>>#testDate > GlorpObjectMappedToImaginaryTableTest>>#testReadBackEntireExample > GlorpUnitOfWorkTest>>#testRollbackOneToManyAfterAdd > > Are these tests failing also on other Pharo images > (i.e., they are known "problems")? > Yes. And I don't know how to fix them. If anyone can help, excellent. > Do you know the impact of these failures? > No > will GLORP be reliable without them? > > I really don't know, but I guess that yes. > > Moose developers, would you include > GLORP in the images built by hudson? > I don't think this is a good idea. I think Glorp has nothing to do with Moose on most cases. This is one of the reasons of having a conf, that with one line of code you can load it...So it is not so complicated if you need to do it manually on a normal Moose image. > I think 839 passing tests are good enough for > the development image. > > Ciao, > Alberto > > > [1] http://hudson.moosetechnology.org/job/moose-with-glamour-seaside/ > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >

Sept. 2, 2010