May 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [ANN] Relicensing IV

by StÃ©phane Ducasse

Hi gabriel can you try to load your slice from the inbox but put the image in another place on your file disc (else the package cache will be used) because some other files are missing stef On May 30, 2009, at 9:23 PM, Gabriel Cotelli wrote: > I uploaded to Pharo Inbox... (hope this time works :) ) > > On Sat, May 30, 2009 at 1:22 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > > wrote: > Hi gabriel > > I cannot get CollectionsTests-Gabir....353 > could publish it in the inbox? > > Stef > On May 30, 2009, at 6:35 AM, Gabriel Cotelli wrote: > > > Hi, > > continuing with licensing issues I push on Pharo-Inbox: SLICE- > > RelicensingIV-GabrielOmarCotelli.2 > > > > Including the next: > > > > Added check for negative to Character>>value: for raising a better > > error message and a test case covering this > > > > Removed: > > - StandardFileMenu class>>oldFileFrom:withPattern: (no senders on > > any pharo image, the only one that appears is a sender to the > > instance message of same name) > > - Form class>>rgbMul (no senders) > > - ExternalStructureInspector (no references) > > - ServerDirectory class>>transferServerDefinitionsToExternal (no > > senders) > > > > Several changes from Yoshiki in Squeak relicensing (reverted to > > clean versions or reimplemented) (If someone needs the exact list of > > methods I can generate this) > > > > Now the dirty methods count should be 46 (I don't run the audit > > however). > > > > Please review. > > > > Thanks, > > Gabriel > > _______________________________________________ > > 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

May 30, 2009

Re: [Pharo-project] [ANN] Relicensing IV

by Gabriel Cotelli

I uploaded to Pharo Inbox... (hope this time works :) ) On Sat, May 30, 2009 at 1:22 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Hi gabriel > > I cannot get CollectionsTests-Gabir....353 > could publish it in the inbox? > > Stef > On May 30, 2009, at 6:35 AM, Gabriel Cotelli wrote: > > > Hi, > > continuing with licensing issues I push on Pharo-Inbox: SLICE- > > RelicensingIV-GabrielOmarCotelli.2 > > > > Including the next: > > > > Added check for negative to Character>>value: for raising a better > > error message and a test case covering this > > > > Removed: > > - StandardFileMenu class>>oldFileFrom:withPattern: (no senders on > > any pharo image, the only one that appears is a sender to the > > instance message of same name) > > - Form class>>rgbMul (no senders) > > - ExternalStructureInspector (no references) > > - ServerDirectory class>>transferServerDefinitionsToExternal (no > > senders) > > > > Several changes from Yoshiki in Squeak relicensing (reverted to > > clean versions or reimplemented) (If someone needs the exact list of > > methods I can generate this) > > > > Now the dirty methods count should be 46 (I don't run the audit > > however). > > > > Please review. > > > > Thanks, > > Gabriel > > _______________________________________________ > > 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 >

May 30, 2009

Re: [Pharo-project] Fwd: preferences to settings refactoring: #colorWhenPrettyPrinting case

by Henrik Sperre Johansen

On 30.05.2009 18:18, StÃ©phane Ducasse wrote: > > >> I belive the "higherPerformance" preference can also be removed, the >> only thing it does it is increase the max possible GUI fps from the >> default 50 to 1000. >> > This is not that simple. Marcus told me that for server this is > important since it can suck all cpu. > I believe we are in agreement, just using different words: - Server mode: Gives 50ms between redraws for non-GUI activity. - Normal mode: Gives (20ms - Time spent in last redraw) for non-GUI activity. - "higher"Performace: Gives (1ms - Time spent in last redraw) for non-GUI activity. If there's no new damage rects, no redrawing happens in updateCycle. For say, a server app with f.ex. a monitoring GUI which sends out dmg rects once one of it's models values that are displayed in the GUI changes, normal can be painful, and downright nasty with higherPerformance enabled when it comes to time left to do actual application stuff... (Especially if GUI contains complex elements, damage rects are somewhat off, + a plethora of other things that are, at the moment, quite likely). So server mode setting is a must-have, higherPerformance not much so. Cheers, Henry

May 30, 2009

Re: [Pharo-project] [ANN] Relicensing IV

by StÃ©phane Ducasse

Hi gabriel I cannot get CollectionsTests-Gabir....353 could publish it in the inbox? Stef On May 30, 2009, at 6:35 AM, Gabriel Cotelli wrote: > Hi, > continuing with licensing issues I push on Pharo-Inbox: SLICE- > RelicensingIV-GabrielOmarCotelli.2 > > Including the next: > > Added check for negative to Character>>value: for raising a better > error message and a test case covering this > > Removed: > - StandardFileMenu class>>oldFileFrom:withPattern: (no senders on > any pharo image, the only one that appears is a sender to the > instance message of same name) > - Form class>>rgbMul (no senders) > - ExternalStructureInspector (no references) > - ServerDirectory class>>transferServerDefinitionsToExternal (no > senders) > > Several changes from Yoshiki in Squeak relicensing (reverted to > clean versions or reimplemented) (If someone needs the exact list of > methods I can generate this) > > Now the dirty methods count should be 46 (I don't run the audit > however). > > Please review. > > Thanks, > Gabriel > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 30, 2009

Re: [Pharo-project] Fwd: preferences to settings refactoring: #colorWhenPrettyPrinting case

by StÃ©phane Ducasse

On May 30, 2009, at 6:12 PM, Henrik Sperre Johansen wrote: > In Pharo-Core, you used to be able to right-click the method > selector pane in System Browser, and in the "What to show..." menu- > option select colorPrint to get syntax highlighting in core. > Don't know if it's ever been related to the setting though, it broke > anyways sometime between 262 and the 281cl image. Not a big loss > anyways. Yes apparently. and we will remove colorPrinting from the core and let Ecompletion do the job. > I belive the "higherPerformance" preference can also be removed, the > only thing it does it is increase the max possible GUI fps from the > default 50 to 1000. This is not that simple. Marcus told me that for server this is important since it can suck all cpu. > > You're VERY unlikely to ever hit 50 fps with any kind of updating > going on, and even if you do, 50 fps is usually more than enough. > > Preferences serverMode setting is somewhat releated, but instead > caps GUI cycles at 20/second (assuming 0ms rendering speed), so > should be kept. thanks this is important that we get feedback. > > > Cheers, > Henry > > On 30.05.2009 16:14, StÃ©phane Ducasse wrote: >> >> I could not believe so I checked :) >> and indeed this preference was totally not working :) >> >> I think that using shout for code colorizing is much better. >> >> Now could you deprecated the most important methods instead of simply >> removing them? >> I can integrate you changes if you want and after you publish a >> deprecate method slice. >> >> Stef >> >> >>>>> This slice removes the preference from the core, so it has nothing >>>>> to do with Shout. >>>>> As noticed in the issue comment, because colorWhenPrettyPretting >>>>> has already no effect when set this slice consists more in a >>>>> clean- >>>>> up. >>>>> >>>>>> do you always color? >>>>>> >>>>> so, never in core >>>>> >>>>>> or do you rely on shout? >>>>>> >>>>> and color in pharo (aka pharo-dev) relies on shout as always. >>>>> >>>> ok this is what I wanted to know. >>>> >>>> Stef >>>> >>>>> alain >>>>> >>>>>> Stef >>>>>> >>>>>> On May 29, 2009, at 9:39 AM, Alain Plantec wrote: >>>>>> >>>>>> >>>>>>> Hi, >>>>>>> A slice is upload in pharoInbox. >>>>>>> Cheers >>>>>>> Alain >>>>>>> >>>>>>> Name: SLICE-colorWhenPrettyPrintingRemoval-alain_plantec.2 >>>>>>> Dependencies: Compiler-alain_plantec.104, >>>>>>> Kernel-alain_plantec.renggli.335, KernelTests-alain_plantec.109, >>>>>>> Polymorph-Tools-Diff-alain_plantec.21, >>>>>>> System-FilePackage-alain_plantec.6, System-Support- >>>>>>> alain_plantec. >>>>>>> 27, >>>>>>> Tools-alain_plantec.154, Traits-alain_plantec.279 >>>>>>> >>>>>>> Remove the #colorWhenPrettyPrinting preference. >>>>>>> As a consequence, some code formatting methods are refactored >>>>>>> (The major remodelling is the >>>>>>> Compiler>>#format:in:notifying:decorated: >>>>>>> removal, replaced by Compiler>>#format:in:notifying:) >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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

May 30, 2009

Re: [Pharo-project] Fwd: preferences to settings refactoring: #colorWhenPrettyPrinting case

by Henrik Sperre Johansen

In Pharo-Core, you used to be able to right-click the method selector pane in System Browser, and in the "What to show..." menu-option select colorPrint to get syntax highlighting in core. Don't know if it's ever been related to the setting though, it broke anyways sometime between 262 and the 281cl image. Not a big loss anyways. I belive the "higherPerformance" preference can also be removed, the only thing it does it is increase the max possible GUI fps from the default 50 to 1000. You're VERY unlikely to ever hit 50 fps with any kind of updating going on, and even if you do, 50 fps is usually more than enough. Preferences serverMode setting is somewhat releated, but instead caps GUI cycles at 20/second (assuming 0ms rendering speed), so should be kept. Cheers, Henry On 30.05.2009 16:14, StÃ©phane Ducasse wrote: > I could not believe so I checked :) > and indeed this preference was totally not working :) > > I think that using shout for code colorizing is much better. > > Now could you deprecated the most important methods instead of simply > removing them? > I can integrate you changes if you want and after you publish a > deprecate method slice. > > Stef > > >>>> This slice removes the preference from the core, so it has nothing >>>> to do with Shout. >>>> As noticed in the issue comment, because colorWhenPrettyPretting >>>> has already no effect when set this slice consists more in a clean- >>>> up. >>>> >>>>> do you always color? >>>>> >>>> so, never in core >>>> >>>>> or do you rely on shout? >>>>> >>>> and color in pharo (aka pharo-dev) relies on shout as always. >>>> >>> ok this is what I wanted to know. >>> >>> Stef >>> >>>> alain >>>> >>>>> Stef >>>>> >>>>> On May 29, 2009, at 9:39 AM, Alain Plantec wrote: >>>>> >>>>> >>>>>> Hi, >>>>>> A slice is upload in pharoInbox. >>>>>> Cheers >>>>>> Alain >>>>>> >>>>>> Name: SLICE-colorWhenPrettyPrintingRemoval-alain_plantec.2 >>>>>> Dependencies: Compiler-alain_plantec.104, >>>>>> Kernel-alain_plantec.renggli.335, KernelTests-alain_plantec.109, >>>>>> Polymorph-Tools-Diff-alain_plantec.21, >>>>>> System-FilePackage-alain_plantec.6, System-Support-alain_plantec. >>>>>> 27, >>>>>> Tools-alain_plantec.154, Traits-alain_plantec.279 >>>>>> >>>>>> Remove the #colorWhenPrettyPrinting preference. >>>>>> As a consequence, some code formatting methods are refactored >>>>>> (The major remodelling is the >>>>>> Compiler>>#format:in:notifying:decorated: >>>>>> removal, replaced by Compiler>>#format:in:notifying:) >>>>>> >>>>>> _______________________________________________ >>>>>> 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 > > >

May 30, 2009

[Pharo-project] XML query engine

by Alexandre Bergel

Dear List, I have been using Michael's XML Parser. It makes me happy. However, a Xpath like query engine is currently missing so far. Any of you had to query XML engine? What are the tools you used? Hard to find its way among the 1500+ projects on squeaksource. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 30, 2009

Re: [Pharo-project] Fwd: preferences to settings refactoring: #colorWhenPrettyPrinting case

by StÃ©phane Ducasse

I could not believe so I checked :) and indeed this preference was totally not working :) I think that using shout for code colorizing is much better. Now could you deprecated the most important methods instead of simply removing them? I can integrate you changes if you want and after you publish a deprecate method slice. Stef >>>> >>> This slice removes the preference from the core, so it has nothing >>> to do with Shout. >>> As noticed in the issue comment, because colorWhenPrettyPretting >>> has already no effect when set this slice consists more in a clean- >>> up. >>>> do you always color? >>> so, never in core >>>> or do you rely on shout? >>> and color in pharo (aka pharo-dev) relies on shout as always. >> >> ok this is what I wanted to know. >> >> Stef >>> >>> >>> alain >>>> >>>> Stef >>>> >>>> On May 29, 2009, at 9:39 AM, Alain Plantec wrote: >>>> >>>>> Hi, >>>>> A slice is upload in pharoInbox. >>>>> Cheers >>>>> Alain >>>>> >>>>> Name: SLICE-colorWhenPrettyPrintingRemoval-alain_plantec.2 >>>>> Dependencies: Compiler-alain_plantec.104, >>>>> Kernel-alain_plantec.renggli.335, KernelTests-alain_plantec.109, >>>>> Polymorph-Tools-Diff-alain_plantec.21, >>>>> System-FilePackage-alain_plantec.6, System-Support-alain_plantec. >>>>> 27, >>>>> Tools-alain_plantec.154, Traits-alain_plantec.279 >>>>> >>>>> Remove the #colorWhenPrettyPrinting preference. >>>>> As a consequence, some code formatting methods are refactored >>>>> (The major remodelling is the >>>>> Compiler>>#format:in:notifying:decorated: >>>>> removal, replaced by Compiler>>#format:in:notifying:) >>>>> >>>>> _______________________________________________ >>>>> 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 >

May 30, 2009

Re: [Pharo-project] [ANN] Relicensing IV

by StÃ©phane Ducasse

thanks gabriel stef On May 30, 2009, at 6:35 AM, Gabriel Cotelli wrote: > Hi, > continuing with licensing issues I push on Pharo-Inbox: SLICE- > RelicensingIV-GabrielOmarCotelli.2 > > Including the next: > > Added check for negative to Character>>value: for raising a better > error message and a test case covering this > > Removed: > - StandardFileMenu class>>oldFileFrom:withPattern: (no senders on > any pharo image, the only one that appears is a sender to the > instance message of same name) > - Form class>>rgbMul (no senders) > - ExternalStructureInspector (no references) > - ServerDirectory class>>transferServerDefinitionsToExternal (no > senders) > > Several changes from Yoshiki in Squeak relicensing (reverted to > clean versions or reimplemented) (If someone needs the exact list of > methods I can generate this) > > Now the dirty methods count should be 46 (I don't run the audit > however). > > Please review. > > Thanks, > Gabriel > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 30, 2009

[Pharo-project] [ANN] Relicensing IV

by Gabriel Cotelli

Hi, continuing with licensing issues I push on Pharo-Inbox: SLICE-RelicensingIV-GabrielOmarCotelli.2 Including the next: Added check for negative to Character>>value: for raising a better error message and a test case covering this Removed: - StandardFileMenu class>>oldFileFrom:withPattern: (no senders on any pharo image, the only one that appears is a sender to the instance message of same name) - Form class>>rgbMul (no senders) - ExternalStructureInspector (no references) - ServerDirectory class>>transferServerDefinitionsToExternal (no senders) Several changes from Yoshiki in Squeak relicensing (reverted to clean versions or reimplemented) (If someone needs the exact list of methods I can generate this) Now the dirty methods count should be 46 (I don't run the audit however). Please review. Thanks, Gabriel

May 30, 2009