- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue #684 Recent Morphic Changesets

by StÃ©phane Ducasse

ok excellent I'm doing it right now On Mar 30, 2009, at 11:08 PM, Henrik Sperre Johansen wrote: > HaloMorphRefactoring was the changeset from Gary (which you > mentioned in mail 17.3 you'd integrate ;) ), so shouldn't need any > licence from Rob. > He also mentioned PluggableTextMorph was a .cs from some while back > (I don't remember from whom it came). > > And yes, I'll check if the update will remove the BorderedMorph > areasRemainingToFill: completely :) > > Cheers, > Henry > > On 30.03.2009 22:48, StÃ©phane Ducasse wrote: >> Hi rob >> >> did you sign the license agreement? >> If not please do it >> Thanks >> >> Stef >> On Mar 22, 2009, at 6:22 PM, Rob Rothwell wrote: >> >> >>> Hi all, >>> >>> I got tired of filing in HaloMorphRefactoring and >>> PluggableTextMorph- >>> scrollSelectionIntoView with every new update, so I published a >>> Morphic package Morphic-rob_rothwell.290 in the inbox with these >>> changes after upgrading to version 10259. >>> >>> Just fixes the non-transparent HaloMorph and non-scrolling edit >>> window when selecting text. >>> >>> Take care, >>> >>> Rob >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 30, 2009

[Pharo-project] [ANN] 10262

by StÃ©phane Ducasse

hi tomorrow closures! Issue 648: Opening protocol browser results in a MessageNotUnderstood: CompiledMethod>>category CompiledMethod>>category by eric Issue 684: Recent Morphic Changesets Removed BorderedMorph>>areasRemainingToFill: Issue 691: integrate Setting System-Setting Issue 696: SuniGUi showing coverage SUnit coverage enhancement Issue 697: New Socket IPv6 new socket primitive and IPv6 changes Alain for setting it would be good - to have a bit more explanation of the design - to know if some of the widgets are setting specific Now we can start having a real layer for preference instead of spaghetti code and also remove the old browser. Stef

March 30, 2009

Re: [Pharo-project] about the closure

by StÃ©phane Ducasse

Thanks! On Mar 30, 2009, at 11:40 PM, Lukas Renggli wrote: > Eliots code comes with additional tests. > > Furthermore I wrote an set of tests (see attachement). These tests > especially make sure that none of the optimizations destroy the > closure behavior. All existing Smalltalk implementations have some > bugs, even the commercial ones. > > Another test is that the image can be completely recompiled and no > additional test fails. > > Then the Seaside tests are another good candidate, they depend heavily > on block behavior. And continuations extensively stress the context > implementation. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > <ClosureTests.st>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 30, 2009

Re: [Pharo-project] about the closure

by Lukas Renggli

Eliots code comes with additional tests. Furthermore I wrote an set of tests (see attachement). These tests especially make sure that none of the optimizations destroy the closure behavior. All existing Smalltalk implementations have some bugs, even the commercial ones. Another test is that the image can be completely recompiled and no additional test fails. Then the Seaside tests are another good candidate, they depend heavily on block behavior. And continuations extensively stress the context implementation. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

March 30, 2009

Re: [Pharo-project] about the closure

by StÃ©phane Ducasse

- do all kind of things with the system - checking the tests that failed Stef On Mar 30, 2009, at 11:17 PM, Michael Roberts wrote: > Hi stef > Apart from kicking the tyres, how best do we test the closure > integration? > > Thanks > Mike > > On 3/30/09, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> hi guys >> >> we discussed a bit with marcus and we arrived to the conclusion that >> we want to push the changes >> in the stream and that we will fix the problems when they show up. >> Now what it means is that >> - we will do probably today >> -> produce a new image >> with non dirty packages >> >> -> produce some fixes to check if we can load them with MC. >> >> and make it roll :) >> >> BTW having closure is really great. the code is so much nicer. >> >> Stef >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 30, 2009

Re: [Pharo-project] about the closure

by Michael Roberts

Hi stef Apart from kicking the tyres, how best do we test the closure integration? Thanks Mike On 3/30/09, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > hi guys > > we discussed a bit with marcus and we arrived to the conclusion that > we want to push the changes > in the stream and that we will fix the problems when they show up. > Now what it means is that > - we will do probably today > -> produce a new image > with non dirty packages > > -> produce some fixes to check if we can load them with MC. > > and make it roll :) > > BTW having closure is really great. the code is so much nicer. > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 30, 2009

Re: [Pharo-project] Issue #684 Recent Morphic Changesets

by Henrik Sperre Johansen

HaloMorphRefactoring was the changeset from Gary (which you mentioned in mail 17.3 you'd integrate ;) ), so shouldn't need any licence from Rob. He also mentioned PluggableTextMorph was a .cs from some while back (I don't remember from whom it came). And yes, I'll check if the update will remove the BorderedMorph areasRemainingToFill: completely :) Cheers, Henry On 30.03.2009 22:48, StÃ©phane Ducasse wrote: > Hi rob > > did you sign the license agreement? > If not please do it > Thanks > > Stef > On Mar 22, 2009, at 6:22 PM, Rob Rothwell wrote: > > >> Hi all, >> >> I got tired of filing in HaloMorphRefactoring and PluggableTextMorph- >> scrollSelectionIntoView with every new update, so I published a >> Morphic package Morphic-rob_rothwell.290 in the inbox with these >> changes after upgrading to version 10259. >> >> Just fixes the non-transparent HaloMorph and non-scrolling edit >> window when selecting text. >> >> Take care, >> >> Rob >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>

March 30, 2009

[Pharo-project] [ANN] Unicode part two integrated

by StÃ©phane Ducasse

please check and add the plugin ClipboardExtendedPlugin in your plugin repository

March 30, 2009

Re: [Pharo-project] Fwd: [ANN] 10254

by StÃ©phane Ducasse

Henrik I'm preparing a new update. Can you check that this will be fixed :) Stef On Mar 23, 2009, at 10:31 AM, Henrik Johansen wrote: > Short answer: Yes. > Long answer: > The implementation in BorderedMorph was fixed in Polymorph-Overrides, > then that version was promoted to Morph, then BorderedMorph reverted > to > pre-Polymorph-Overrides functionality from the removeSelector: in my > cs. > So the "correct" thing to do would be to remove all versions of the > method from BorderedMorph, as it's former (correct) version is now > used > by Morph. > > Cheers, > Henry > > StÃ©phane Ducasse wrote: >> so henrik >> is is ok if I remove areasRemainingToFill: from BorderedMorph? >> >> Stef >> >> On Mar 19, 2009, at 1:46 PM, Henrik Johansen wrote: >> >> >>> I know, which is why I thought it was strange, the .cs contained: >>> !BorderedMorph removeSelector: #areasRemainingToFill:! >>> which when I file it in, results in no areasRemainingToFill: method >>> for >>> BorderedMorph in the image. >>> >>> I really have no idea how the update process makes it revert to an >>> older >>> version instead, nor how one would go about fixing it... :/ >>> >>> Cheers, >>> Henrik >>> >>> StÃ©phane Ducasse wrote: >>> >>>> henrik I just integrated the file you gave me. >>>> If you have a new version that fixes the problem I will do a new >>>> version. >>>> >>>> Stef >>>> >>>> On Mar 19, 2009, at 12:20 PM, Henrik Johansen wrote: >>>> >>>> >>>>> It seems BorderedMorph's areasRemainingToFill: method got reverted >>>>> to >>>>> the version in use prior to the override by PolyMorph (which has >>>>> now >>>>> been promoted to Morph), instead of removed completely. >>>>> (This is the state my image is in after updating a released 248, >>>>> at >>>>> least) >>>>> >>>>> Cheers, >>>>> Henry >>>>> >>>>> StÃ©phane Ducasse wrote: >>>>> >>>>>> Issue 655: Overlapping Graphics on World do not Properly >>>>>> Repaint >>>>>> Issue 658: Preferences resetHaloSpecifications >>>>>> Issue 664: unimplemented errorCantGoBack >>>>>> Closed 665 >>>>>> >>>>>> now we will focus on the closures. >>>>>> >>>>>> Stef >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Pharo-project mailing list >>>>>> Pharo-project(a)lists.gforge.inria.fr >>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>>> >>>>>> >>>>>> >>>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- >>>>> project >>>>> >>>>> >>>> ------------------------------------------------------------------------ >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 30, 2009

Re: [Pharo-project] Issue #684 Recent Morphic Changesets

by StÃ©phane Ducasse

Hi rob did you sign the license agreement? If not please do it Thanks Stef On Mar 22, 2009, at 6:22 PM, Rob Rothwell wrote: > Hi all, > > I got tired of filing in HaloMorphRefactoring and PluggableTextMorph- > scrollSelectionIntoView with every new update, so I published a > Morphic package Morphic-rob_rothwell.290 in the inbox with these > changes after upgrading to version 10259. > > Just fixes the non-transparent HaloMorph and non-scrolling edit > window when selecting text. > > Take care, > > Rob > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 30, 2009