- Pharo-dev - lists.pharo.org

[Pharo-project] Integrate changes from Cuis (was Fwd: [squeak-dev] Cuis update - Separate change sets for goodies available)

by Adrian Lienhard

There probably are a couple of interesting improvements/fixes in the work of Juan. I created an issue: http://code.google.com/p/pharo/issues/detail?id=717 Adrian Begin forwarded message: > From: Juan Vuletich <juan(a)jvuletich.org> > Date: April 6, 2009 3:28:28 PM GMT+02:00 > To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org > > > Subject: [squeak-dev] Cuis update - Separate change sets for goodies > available > Reply-To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org > > > > Hi Folks, > > I've just uploaded http://www.jvuletich.org/Cuis/Cuis1.0-0169.zip . > I did some refactoring and cleanup in ScrollPane and ScrollBar. Now > Browser openBrowser takes almost half the time! I also added back > the preference for scrollbars on left. So, Klaus, you don't need to > do it. > > (These were already in previous release, 0166: I removed the Old > prefix from Morphic classes, to ease loading code from other Squeak > distributions. I also changed fonts to use just 16bpp and not 32. > The difference is invisible to my eyes, and they use half the space. > And I fixed the #isMorphic bug reported by Klaus. ) > > I also uploaded http://www.jvuletich.org/Cuis/ > CuisUpdatesUpTo0169.zip . This file includes the change sets of the > last year. I don't have older ones available in cs form, but most > goodies and tweaks that could be useful for other Squeak > distributions are here. This http://www.jvuletich.org/Cuis/CategoriesAndChangeSets.txt > is the detail of which changesets belong to which of the following > categories: > > - Rename class and update references goodie > - Process scheduling enh > - MessageTally enh > - Logging and ChangeSet enhancements > - Dan's == with SmallIntegers > - Affected class categories goodie > - Protocol Catcher goodie > - Nicer Cursors > - Chronology enh > - Parser enh > - ProgressBar enh > - Text cleanup and refactoring > - ScrollPane and ScrollBar cleanup & refacto > - NiceFonts > - Code authorship and relicensing > - Focus navigation and enh > - Pointer explorer goodie > - Code evaluation fixes > - Remote cursor sender goodie > - Semaphores, Delays and Processes > - Misc goodies and lesser tweaks > - Cleanup > - Morphic / LightWidgets > > Comments welcome. > > Cheers, > Juan Vuletich >

April 6, 2009

Re: [Pharo-project] which tests should be green with Pharo?? [WAS] tentative schedule roadmap ....

by Adrian Lienhard

Yes, to make all tests green is a task for the milestone 1.0. Currently they are dark red ;) Adrian On Apr 6, 2009, at 15:20 , Mariano Martinez Peck wrote: > On Mon, Apr 6, 2009 at 4:41 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr>wrote: > >> yes >> we open the testrunner and click run and everything should be green. >> > > Ok, thanks Stef. But this would be in a future ? I am correct ? I > mean, > RIGHT NOW they are not all green. > > Cheers, > > Mariano > > > >> >> stef >> >> On Apr 5, 2009, at 11:32 PM, Mariano Martinez Peck wrote: >> >>> When you all talk about having all tests green, which tests are you >>> talking about ? Suppose I say "Pharo will have all tests in green". >>> Which tests are them ? >>> >>> All that are in pharo core image ? >>> >>> Thanks, >>> >>> Mariano >>> >>> ---------- Forwarded message ---------- >>> From: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>> Date: Tue, Mar 31, 2009 at 3:42 AM >>> Subject: Re: [Pharo-project] Pharo tentative schedule roadmap .... >>> To: Pharo-project(a)lists.gforge.inria.fr >>> >>> >>> probably >>> We will harvest the closures and we will have to think what we >>> want to >>> do. >>> If you and other want to help the tests should be green and stop >>> popping up dialog boxes >>> >>> Stef >>> >>> >>> On Mar 31, 2009, at 12:43 AM, Geert wrote: >>> >>>> >>>> I assume the tentative (March Beta and May release) schedule on the >>>> Pharo Project website may need some minor adjustments? >>>> -- >>>> View this message in context: >> http://n2.nabble.com/Pharo-tentative-schedule-roadmap-....-tp2560092p256009… >>>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >>>> >>>> >>>> _______________________________________________ >>>> 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

April 6, 2009

Re: [Pharo-project] which tests should be green with Pharo?? [WAS] tentative schedule roadmap ....

by Mariano Martinez Peck

On Mon, Apr 6, 2009 at 4:41 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > yes > we open the testrunner and click run and everything should be green. > Ok, thanks Stef. But this would be in a future ? I am correct ? I mean, RIGHT NOW they are not all green. Cheers, Mariano > > stef > > On Apr 5, 2009, at 11:32 PM, Mariano Martinez Peck wrote: > > > When you all talk about having all tests green, which tests are you > > talking about ? Suppose I say "Pharo will have all tests in green". > > Which tests are them ? > > > > All that are in pharo core image ? > > > > Thanks, > > > > Mariano > > > > ---------- Forwarded message ---------- > > From: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > Date: Tue, Mar 31, 2009 at 3:42 AM > > Subject: Re: [Pharo-project] Pharo tentative schedule roadmap .... > > To: Pharo-project(a)lists.gforge.inria.fr > > > > > > probably > > We will harvest the closures and we will have to think what we want to > > do. > > If you and other want to help the tests should be green and stop > > popping up dialog boxes > > > > Stef > > > > > > On Mar 31, 2009, at 12:43 AM, Geert wrote: > > > > > > > > I assume the tentative (March Beta and May release) schedule on the > > > Pharo Project website may need some minor adjustments? > > > -- > > > View this message in context: > http://n2.nabble.com/Pharo-tentative-schedule-roadmap-....-tp2560092p256009… > > > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > > > > > > > _______________________________________________ > > > 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 >

April 6, 2009

Re: [Pharo-project] Unicode Problem (again) even with fix in 10266

by Michael Rueger

StÃ©phane Ducasse wrote: > this is strange because I can update without problem from 10263 The problem originates from the iteration over subclasses. Depending on the exact state of the image the iteration can provided a different order on different images. If someone could come up with a better way than this automagic allSubclasses configuration pattern, that would be most welcome. Michael

April 6, 2009

Re: [Pharo-project] SUnits and UI interaction

by Gary Chambers

Forgot to copy to squeaksource... up now (Polymorph-ToolBuilder-gvc.7). Regards, Gary ----- Original Message ----- From: "Adrian Lienhard" <adi(a)netstyle.ch> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Monday, April 06, 2009 8:51 AM Subject: Re: [Pharo-project] SUnits and UI interaction > Thanks for looking into this! > > I added the following note to the issue: > > It seems PSUIManager>>confirm: is where the ProvideAnswerNotification > is missing. There are more of those, though. I fixed another one and > now the BlockContextTest in a 10263 image are green again (see > attached changeset). We still need to check all other implementation > of confirm: and friends. > > Gary, could you maybe have a look? > > Cheers, > Adrian > > On Apr 6, 2009, at 09:27 , Michael Roberts wrote: > >> I think there must be a corresponding change not yet integrated in >> self confirm:, or has been backed out with UI theme changes perhaps. >> >> this should raise ProvideAnswerNotification. >> >> http://code.google.com/p/pharo/issues/detail?id=716 >> >> thanks >> Mike >> >> _______________________________________________ >> 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

April 6, 2009

Re: [Pharo-project] SUnits and UI interaction

by Adrian Lienhard

Thanks for looking into this! I added the following note to the issue: It seems PSUIManager>>confirm: is where the ProvideAnswerNotification is missing. There are more of those, though. I fixed another one and now the BlockContextTest in a 10263 image are green again (see attached changeset). We still need to check all other implementation of confirm: and friends. Gary, could you maybe have a look? Cheers, Adrian On Apr 6, 2009, at 09:27 , Michael Roberts wrote: > I think there must be a corresponding change not yet integrated in > self confirm:, or has been backed out with UI theme changes perhaps. > > this should raise ProvideAnswerNotification. > > http://code.google.com/p/pharo/issues/detail?id=716 > > thanks > Mike > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 6, 2009

Re: [Pharo-project] SUnits and UI interaction

by Michael Roberts

I think there must be a corresponding change not yet integrated in self confirm:, or has been backed out with UI theme changes perhaps. this should raise ProvideAnswerNotification. http://code.google.com/p/pharo/issues/detail?id=716 thanks Mike

April 6, 2009

Re: [Pharo-project] which tests should be green with Pharo?? [WAS] tentative schedule roadmap ....

by StÃ©phane Ducasse

yes we open the testrunner and click run and everything should be green. stef On Apr 5, 2009, at 11:32 PM, Mariano Martinez Peck wrote: > When you all talk about having all tests green, which tests are you > talking about ? Suppose I say "Pharo will have all tests in green". > Which tests are them ? > > All that are in pharo core image ? > > Thanks, > > Mariano > > ---------- Forwarded message ---------- > From: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Date: Tue, Mar 31, 2009 at 3:42 AM > Subject: Re: [Pharo-project] Pharo tentative schedule roadmap .... > To: Pharo-project(a)lists.gforge.inria.fr > > > probably > We will harvest the closures and we will have to think what we want to > do. > If you and other want to help the tests should be green and stop > popping up dialog boxes > > Stef > > > On Mar 31, 2009, at 12:43 AM, Geert wrote: > > > > > I assume the tentative (March Beta and May release) schedule on the > > Pharo Project website may need some minor adjustments? > > -- > > View this message in context: http://n2.nabble.com/Pharo-tentative-schedule-roadmap-....-tp2560092p256009… > > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > > > > _______________________________________________ > > 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

April 6, 2009

[Pharo-project] About readsField:

by StÃ©phane Ducasse

Hi When reading the code of readField: I have the impression that a part of this method should be moved to instructionStream. Same for writesField: Stef readsField: varIndex "Answer whether the receiver loads the instance variable indexed by the argument." "eem 5/24/2008 Rewritten to no longer assume the compiler uses the most compact encoding available (for EncoderForLongFormV3 support)." | varIndexCode scanner | varIndexCode := varIndex - 1. self isReturnField ifTrue: [^self returnField = varIndexCode]. ^(scanner := InstructionStream on: self) scanFor: [:b| b < 16 ifTrue: [b = varIndexCode] ifFalse: [b = 128 ifTrue: [scanner followingByte = varIndexCode and: [varIndexCode <= 63]] ifFalse: [b = 132 and: [(scanner followingByte between: 64 and: 95) and: [scanner thirdByte = varIndexCode]]]]]

April 6, 2009

Re: [Pharo-project] status of split join in pharo

by Keith Hodges

Oscar Nierstrasz wrote: > Oops. I made a mistake in the experiment. There is actually less > difference than I thought. > > Here we load a web site, optionally using split and join to remove all > comments. My regex version seems to be only marginally worse than > Keith's sequence splitting. > > > 5289 "ON split on regex" > 5327 > > 5165 "KH split on sequence" > 5160 > > 2153 "no splitting" > 2160 > > So regex splitting seems to be feasible. > splitOn: uses double dispatch so that it is the argument that determines who it performs the splitting. All you have to do it implement Regex-#splitUp: aString Keith

April 5, 2009