January 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3440 in pharo: Cycle in Monticello removed

by pharo＠googlecode.com

Updates: Status: Fixed Labels: Milestone-1.3 Comment #2 on issue 3440 by marcus.d...(a)gmail.com: Cycle in Monticello removed http://code.google.com/p/pharo/issues/detail?id=3440 (No comment was entered for this change.)

Jan. 20, 2011

Re: [Pharo-project] PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled:

by Benjamin

Yes, code depends of this class, but this class inherits from PluggableTextMorph, so we can just remove everything in it, and just keep the name to keep the system working (and maybe move this class in the package Deprecated) Ben On Jan 20, 2011, at 11:09 AM, Tudor Girba wrote: > Yes, but I guess code still depends on this class. So, at the very least the class should still be preserved for one version. > > Cheers, > Doru > > > On 20 Jan 2011, at 11:05, Benjamin wrote: > >> In fact, PluggableShoutMorph shouldn't be used anymore, but PluggableTextMorph instead now that PluggableTextMorph handle the text styling :) >> >> >> Ben >> >> >> On Jan 20, 2011, at 9:34 AM, Tudor Girba wrote: >> >>> We probably need to remove that variable from PluggableShoutMorph. This variable does not exist in Pharo 1.2 12292. >>> >>> Cheers, >>> Doru >>> >>> >>> On 20 Jan 2011, at 09:11, laurent laffont wrote: >>> >>>> Other error: https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.2/71/console >>>> >>>> >>>> duplicatedVariableError: styler is already defined in PluggableTextMorph >>>> >>>> >>>> Laurent >>>> >>>> On Thu, Jan 20, 2011 at 8:38 AM, Tudor Girba <tudor.girba(a)gmail.com> wrote: >>>> Thanks Laurent and Alain for testing this. >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>> On 20 Jan 2011, at 08:21, Alain Plantec wrote: >>>> >>>>> the same here, it works. >>>>> Now I can load Petit. >>>>> Thanks >>>>> Alain >>>>> >>>>> Le 20/01/2011 08:08, laurent laffont a Ã©crit : >>>>>> It works ! It works ! >>>>>> >>>>>> Laurent >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "Live like you mean it." >>>> >>>> >>>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Presenting is storytelling." >>> >>> >> >> > > -- > www.tudorgirba.com > > "It's not how it is, it is how we see it." > >

Jan. 20, 2011

Re: [Pharo-project] Issue 3441 in pharo: Tests for Polymorph

by pharo＠googlecode.com

Updates: Status: Fixed Labels: Milestone-1.3 Comment #2 on issue 3441 by marcus.d...(a)gmail.com: Tests for Polymorph http://code.google.com/p/pharo/issues/detail?id=3441 (No comment was entered for this change.)

Jan. 20, 2011

Re: [Pharo-project] Issue 3526 in pharo: Update bug reporting instructions now that new issues are automatically posted to mailing list

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3526 by marcus.d...(a)gmail.com: Update bug reporting instructions now that new issues are automatically posted to mailing list http://code.google.com/p/pharo/issues/detail?id=3526 DONE

Jan. 20, 2011

Re: [Pharo-project] PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled:

by Tudor Girba

Yes, but I guess code still depends on this class. So, at the very least the class should still be preserved for one version. Cheers, Doru On 20 Jan 2011, at 11:05, Benjamin wrote: > In fact, PluggableShoutMorph shouldn't be used anymore, but PluggableTextMorph instead now that PluggableTextMorph handle the text styling :) > > > Ben > > > On Jan 20, 2011, at 9:34 AM, Tudor Girba wrote: > >> We probably need to remove that variable from PluggableShoutMorph. This variable does not exist in Pharo 1.2 12292. >> >> Cheers, >> Doru >> >> >> On 20 Jan 2011, at 09:11, laurent laffont wrote: >> >>> Other error: https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.2/71/console >>> >>> >>> duplicatedVariableError: styler is already defined in PluggableTextMorph >>> >>> >>> Laurent >>> >>> On Thu, Jan 20, 2011 at 8:38 AM, Tudor Girba <tudor.girba(a)gmail.com> wrote: >>> Thanks Laurent and Alain for testing this. >>> >>> Cheers, >>> Doru >>> >>> >>> On 20 Jan 2011, at 08:21, Alain Plantec wrote: >>> >>>> the same here, it works. >>>> Now I can load Petit. >>>> Thanks >>>> Alain >>>> >>>> Le 20/01/2011 08:08, laurent laffont a Ã©crit : >>>>> It works ! It works ! >>>>> >>>>> Laurent >>>>> >>>>> >>>> >>>> >>>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Live like you mean it." >>> >>> >>> >> >> -- >> www.tudorgirba.com >> >> "Presenting is storytelling." >> >> > > -- www.tudorgirba.com "It's not how it is, it is how we see it."

Jan. 20, 2011

Re: [Pharo-project] PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled:

by Benjamin

In fact, PluggableShoutMorph shouldn't be used anymore, but PluggableTextMorph instead now that PluggableTextMorph handle the text styling :) Ben On Jan 20, 2011, at 9:34 AM, Tudor Girba wrote: > We probably need to remove that variable from PluggableShoutMorph. This variable does not exist in Pharo 1.2 12292. > > Cheers, > Doru > > > On 20 Jan 2011, at 09:11, laurent laffont wrote: > >> Other error: https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.2/71/console >> >> >> duplicatedVariableError: styler is already defined in PluggableTextMorph >> >> >> Laurent >> >> On Thu, Jan 20, 2011 at 8:38 AM, Tudor Girba <tudor.girba(a)gmail.com> wrote: >> Thanks Laurent and Alain for testing this. >> >> Cheers, >> Doru >> >> >> On 20 Jan 2011, at 08:21, Alain Plantec wrote: >> >>> the same here, it works. >>> Now I can load Petit. >>> Thanks >>> Alain >>> >>> Le 20/01/2011 08:08, laurent laffont a Ã©crit : >>>> It works ! It works ! >>>> >>>> Laurent >>>> >>>> >>> >>> >>> >> >> -- >> www.tudorgirba.com >> >> "Live like you mean it." >> >> >> > > -- > www.tudorgirba.com > > "Presenting is storytelling." > >

Jan. 20, 2011

Re: [Pharo-project] Issue 3556 in pharo: PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled:

by pharo＠googlecode.com

Updates: Status: Fixed Comment #1 on issue 3556 by stephane...(a)gmail.com: PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled: http://code.google.com/p/pharo/issues/detail?id=3556 (No comment was entered for this change.)

Jan. 20, 2011

Re: [Pharo-project] About XML Support in the 1.2

by StÃ©phane Ducasse

>>>> >>> If it is not just a copy what else is implied? >> >> As Stef mentioned, there are two things to do: >> - copy the actual packages into a different repository >> - change the references to Monticello repositories from the Configurations (this should be applied both to packages and to nested configurations) >> > Thanks Doru for explaining. So this makes total sense to me packaging wise but it is a lot of re-doing while integrating. The repositories have to be changed every single time. But I think that there is a task that automatically copies the packages of a version and that metacello will have some solution for the change in repositories. But metacello has an override for looking package so normally this can be mechanically done. Dale? Stef

Jan. 20, 2011

Re: [Pharo-project] Issue 3554 in pharo: CP1252TextConverter new does not work

by StÃ©phane Ducasse

Do we need 1252 and 1250? What is the difference? I saw 1253 is for greek Right now I change Soup to work with 1250 instead of an old bogus 1252 Stef

Jan. 20, 2011

Re: [Pharo-project] Issue 3527 in pharo: Please add the following Generator code to Pharo. I need it to port a package I am writing from Squeak to Pharo

by pharo＠googlecode.com

Comment #1 on issue 3527 by marcus.d...(a)gmail.com: Please add the following Generator code to Pharo. I need it to port a package I am writing from Squeak to Pharo http://code.google.com/p/pharo/issues/detail?id=3527 can you attach code (not only a test)?

Jan. 20, 2011