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

Re: [Pharo-project] [ANN] - New SqueakDBX release

by StÃ©phane Ducasse

this is what I really think :)

Jan. 20, 2009

Re: [Pharo-project] [ANN] - New SqueakDBX release

by Mariano Martinez Peck

On Tue, Jan 20, 2009 at 6:01 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Thanks. > I'm not expert but I appreciate your dedication because this is > difficult to obtain > robust software, and it deserves care and time. > So keep your good job. > Thanks for the nice words Stef. > > Stef > On Jan 20, 2009, at 3:11 AM, Mariano Martinez Peck wrote: > > > As promise, here are new benchmarks: http://wiki.squeak.org/squeak/ > > 6063 > > > > Till now, we only have benchmarks for PostgreSQL. Now we have for > > all the supported backends. > > > > Cheers, > > > > Mariano > > > > On Tue, Dec 23, 2008 at 3:52 PM, Mariano Martinez Peck < > marianopeck(a)gmail.com > > > wrote: > > We are very glad to announce our second beta release of SqueakDBX. > > > > The aim of this project is to build an OpenDBX > > (http://www.linuxnetworks.de/doc/index.php/OpenDBX/) plugin which will > > allow users to perform relational database operations (DDL, DML and > > SQL) through a truly open source library. > > > > The features for this release are: > > > > Bugs fixed: > > > > - Bug in odbx_query(), odbx_result() and odbx_result_finish() > > execution order. > > - Timeout in DBXPlatform #nextResultSet: was wrong mapped with FFI. > > Now, it is nil. > > - Some bugs in OpenDBXWin32 with apiCalls. > > > > New Features: > > > > -Support for SQLite in Linux > > -Support for MSSQL in linux and windows (with MinGW) > > -Support for PostgreSQL in Windows (with MinGW). > > -Better error handling. See http://wiki.squeak.org/squeak/6076 > > -New non-blocking plugin to replace FFI (just a proof of concept, but > > running). See OpenDBX-Plugin package in Monticello. > > -New SqueakDBX tutorial: how to compile openDBX in linux and windwos, > > common problems and solutions. You can download it from: > > > http://www.assembla.com/spaces/Proyecto-Proyecto/documents/a0bKPg0qCr3Aeaab… > > . > > However this pdf will be converted into "wiki format" and put there. > > -Configurable Log. See http://wiki.squeak.org/squeak/6099 > > -Refactorized and updated wiki: http://wiki.squeak.org/squeak/6052 > > > > > > - We will be adding benchmarks on different backends and OS soon in > > the wiki: http://wiki.squeak.org/squeak/6063. > > - You must use openDBX 1.3.10 version. > > > > Useful links from wiki: > > > > - Current supported backends, operating system and squeak images here: > > http://wiki.squeak.org/squeak/6108 > > - ChangeLog: http://wiki.squeak.org/squeak/6109 > > - Targets and Features: http://wiki.squeak.org/squeak/6106 > > > > > > Again, help wanted. We are really convinced about open source > > projects. A software project is better when people share opinions, > > work, advice, comments, etc. > > We would really appreciate if you: > > > > -Give us opinions, comments, ideas, new features, complaints and so > > on. > > -tell us if you find a bug. > > -tell us if you test SqueakDBX with other RDMBS or OS different from > > the ones we tested. Just to know if it works or not :) > > > > Full documentation, installation and getting started instructions can > > be found at wiki page: http://wiki.squeak.org/squeak/6052 > > > > Packages can be installed from Universe (3.10) or SqueakMap. Current > > version is 0.8 > > Sources can be download from SqueakSource > > http://www.squeaksource.com/SqueakDBX (it requires FFI installed) > > > > Cheers, > > > > SqueakDBX team > > > > _______________________________________________ > > 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 >

Jan. 20, 2009

Re: [Pharo-project] [ANN] 10208

by Alexandre Bergel

Was able to update without problem. Alexandre On 19 Jan 2009, at 21:44, StÃ©phane Ducasse wrote: > - Enh Tool diff. > - Issue 444: Simple Morphic cleanup: Clean up Morph Remove > ownerThatIsA:orA: from Morph. > - more collection tests. > - Issue 445: AligmentMorphBob1 should be merged into AligmentMorph > - Minor cleaning of Bergel on StringHolder > > > More to come soon. > watch it > network > traits adrian fixes > smalldictionary fixes > > - I will try :) > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 20, 2009

Re: [Pharo-project] uiTheme Standard Squeak uses ~96% CPU

by StÃ©phane Ducasse

excellent I will do an update stef On Jan 20, 2009, at 12:56 PM, Gary Chambers wrote: > An erroneous "self changed" was being performed when the splitter > should > not be drawn (not needed since transparent with no handles). > > Fixed in Polymorph-Widgets-gvc.29. > > Regards, Gary. > > ----- Original Message ----- > From: "Gary Chambers" <gazzaguru2(a)btinternet.com> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Tuesday, January 20, 2009 11:42 AM > Subject: Re: [Pharo-project] uiTheme Standard Squeak uses ~96% CPU > > > It appears to be the case that for StandardSqueak the pane splitters > are > constantly showing damage and, hence, being redrawn... > > Regards, Gary. > > ----- Original Message ----- > From: "Gary Chambers" <gazzaguru2(a)btinternet.com> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Tuesday, January 20, 2009 11:31 AM > Subject: Re: [Pharo-project] uiTheme Standard Squeak uses ~96% CPU > > > Confirmed and investigating... > > Regards, Gary. > > ----- Original Message ----- > From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > To: "Pharo Development" <Pharo-project(a)lists.gforge.inria.fr> > Sent: Tuesday, January 20, 2009 8:31 AM > Subject: [Pharo-project] uiTheme Standard Squeak uses ~96% CPU > > > http://code.google.com/p/pharo/issues/detail?id=454&can=1&colspec=ID%20Type… > > Issue 454: > uiTheme Standard Squeak uses ~96% CPU > â¹ Prev 454 of 454 > 1 person starred this issue and may be notified of changes. > Back to list > Status: > New > Owner: > ---- > > > Add a comment andmake changes below > Reported by wsgibson1967, Today (5 hours ago) > I know. As much as I really like the Watery 2 uiTheme theme I also > really like to use the Standard Squeak theme. I have found on both my > Mac and Windows systems that when using the Standard Squeak theme with > Pharo (core or dev) that the CPU usage will go very high. If a normal > amount of windows are open the CPU usage goes upwards to 96%. I do not > get this with the Watery 2 or Soft Squeak themes. In case this is > useful, I am using TrueType fonts that are standard to each platform. > To reproduce: 1) Change to Standard Squeak theme 2) Open two code > browsers and select methods from any class (just opening browsers > without drilling down to methods do not produce as much of an effect) > 3) Open a Test Runner window 4) Open a Monticello Browser The CPU will > increase to roughly 96%. I also would like to mention that you guys > have done an INCREDIBLE job with Pharo! I am totally impressed with > the amount of work done with Pharo as well as its quality. Thank you > for stepping up to the challenge! > > > _______________________________________________ > 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 >

Jan. 20, 2009

Re: [Pharo-project] Workspace Enhancement

by StÃ©phane Ducasse

i see and I have the impression that with a counter and modulo you would not have to copy. On Jan 20, 2009, at 12:54 PM, Alexandre Bergel wrote: > What I currently do, is something like: > > history addFirst: workspace content. > history := history copyFrom: 1 to: (history size min: 5). > > Alexandre > > On 20 Jan 2009, at 11:15, StÃ©phane Ducasse wrote: > >> yes >> so you always add to your collection but you do not have to have 5 >> instance variables >> and have a counter and also always add at the icunter value or simply >> do a modulo: 5 + 1 >> >> stef >> >> On Jan 20, 2009, at 10:24 AM, Alexandre Bergel wrote: >> >>> Humm... Ideally, the history should contains the most recent >>> workspace >>> contents doesn't it? >>> >>> Alexandre >>> >>> >>> On 20 Jan 2009, at 10:17, StÃ©phane Ducasse wrote: >>> >>>> why don't you use a "circular" array using atWrap >>>> >>>> atWrap: index put: value >>>> "Store value into the index'th element of the receiver. If index >>>> is >>>> out >>>> of bounds, let it wrap around from the end to the beginning until >>>> it >>>> is in bounds. Answer value." >>>> >>>> ^ self at: index - 1 \\ self size + 1 put: value >>>> >>>> :) >>>> >>>> On Jan 20, 2009, at 9:44 AM, Alexandre Bergel wrote: >>>> >>>>>>>> Neat behaviour - I'll have to try it out (like, what happens >>>>>>>> when >>>>>>>> you have 5 open workspaces - do they all have access to the >>>>>>>> same >>>>>>>> list of history? Just something to try). >>>>>>>> >>>>>>>> What about contents of workspace variables? Are those stored >>>>>>>> in >>>>>>>> the >>>>>>>> history as well? >>>>>>> >>>>>>> Actually, I seldom reuse variables across workspaces and have no >>>>>>> more >>>>>>> than 2 or 3 workspace at the same time. >>>>>>> What would be the ideal scenario for variables? >>>>>>> >>>>>>> Thanks for your words, >>>>>>> Alexandre >>>>> >>>>> The history for workspace contents has 5 slots. Slots are filled >>>>> upon >>>>> workspace deletion: when you close a workspace, its content is >>>>> inserted in the history. Only the last 5 contents are remembered. >>>>> Other are forgotten. >>>>> >>>>> It is easy to increase this limit although. >>>>> >>>>> Cheers, >>>>> Alexandre >>>>> -- >>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>> Alexandre Bergel http://www.bergel.eu >>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> 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 >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 20, 2009

Re: [Pharo-project] Merging tool and class var

by StÃ©phane Ducasse

thanks I will check On Jan 20, 2009, at 12:19 PM, Gary Chambers wrote: > Should be ok merging Polymorph-Widgets-gvc.28 now. > > Regards, Gary. > > ----- Original Message ----- > From: "Gary Chambers" <gazzaguru2(a)btinternet.com> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Tuesday, January 20, 2009 11:07 AM > Subject: Re: [Pharo-project] Merging tool and class var > > > Aye. Is down to the (structure) changes for focus indicator morphs. > Will put in a compatability check... > > Regards, Gary. > > ----- Original Message ----- > From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Monday, January 19, 2009 8:12 PM > Subject: Re: [Pharo-project] Merging tool and class var > > >> gary while loading >> >> Polymorph-Widgets-gvc.26 >> crashed on BorderedMorph>>key >> >> In addition doing the alignmentMorph cleanup that I will integrate we >> got some polymorph overrides >> could you check that? >> >> Stef >> >> On Jan 14, 2009, at 4:07 PM, Gary Chambers wrote: >> >>> >>> ----- Original Message ----- >>> From: "Gary Chambers" <gazzaguru2(a)btinternet.com> >>> To: <Pharo-project(a)lists.gforge.inria.fr> >>> Sent: Wednesday, January 14, 2009 2:35 PM >>> Subject: Re: [Pharo-project] Merging tool and class var >>> >>> >>>> On SqueakSource. Polymorph-Widgets-gvc.26 (mostly Watery2 >>>> enhancements) >>>> and >>>> Polymorph-Tools-Diff-gvc.8 (should deal with all the current >>>> feedback). >>> >>> With the exception of labelling each side of the diff ;-) >>> Gary. >>> >>> >>>> >>>> Regards, Gary. >>>> >>>> ----- Original Message ----- >>>> From: "Lukas Renggli" <renggli(a)gmail.com> >>>> To: <Pharo-project(a)lists.gforge.inria.fr> >>>> Sent: Wednesday, January 14, 2009 2:15 PM >>>> Subject: Re: [Pharo-project] Merging tool and class var >>>> >>>> >>>>>> Indeed. Just finished for class-side definition changes, comment >>>>>> and >>>>>> commentStamp... >>>>>> Putting up on SqueakSource shortly. >>>>> >>>>> Great! >>>>> >>>>> Lukas >>>>> >>>>> -- >>>>> Lukas Renggli >>>>> http://www.lukas-renggli.ch >>>>> >>>>> _______________________________________________ >>>>> 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 >

Jan. 20, 2009

Re: [Pharo-project] uiTheme Standard Squeak uses ~96% CPU

by Gary Chambers

An erroneous "self changed" was being performed when the splitter should not be drawn (not needed since transparent with no handles). Fixed in Polymorph-Widgets-gvc.29. Regards, Gary. ----- Original Message ----- From: "Gary Chambers" <gazzaguru2(a)btinternet.com> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Tuesday, January 20, 2009 11:42 AM Subject: Re: [Pharo-project] uiTheme Standard Squeak uses ~96% CPU It appears to be the case that for StandardSqueak the pane splitters are constantly showing damage and, hence, being redrawn... Regards, Gary. ----- Original Message ----- From: "Gary Chambers" <gazzaguru2(a)btinternet.com> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Tuesday, January 20, 2009 11:31 AM Subject: Re: [Pharo-project] uiTheme Standard Squeak uses ~96% CPU Confirmed and investigating... Regards, Gary. ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: "Pharo Development" <Pharo-project(a)lists.gforge.inria.fr> Sent: Tuesday, January 20, 2009 8:31 AM Subject: [Pharo-project] uiTheme Standard Squeak uses ~96% CPU http://code.google.com/p/pharo/issues/detail?id=454&can=1&colspec=ID%20Type… Issue 454: uiTheme Standard Squeak uses ~96% CPU â¹ Prev 454 of 454 1 person starred this issue and may be notified of changes. Back to list Status: New Owner: ---- Add a comment andmake changes below Reported by wsgibson1967, Today (5 hours ago) I know. As much as I really like the Watery 2 uiTheme theme I also really like to use the Standard Squeak theme. I have found on both my Mac and Windows systems that when using the Standard Squeak theme with Pharo (core or dev) that the CPU usage will go very high. If a normal amount of windows are open the CPU usage goes upwards to 96%. I do not get this with the Watery 2 or Soft Squeak themes. In case this is useful, I am using TrueType fonts that are standard to each platform. To reproduce: 1) Change to Standard Squeak theme 2) Open two code browsers and select methods from any class (just opening browsers without drilling down to methods do not produce as much of an effect) 3) Open a Test Runner window 4) Open a Monticello Browser The CPU will increase to roughly 96%. I also would like to mention that you guys have done an INCREDIBLE job with Pharo! I am totally impressed with the amount of work done with Pharo as well as its quality. Thank you for stepping up to the challenge! _______________________________________________ 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

Jan. 20, 2009

Re: [Pharo-project] Workspace Enhancement

by Alexandre Bergel

What I currently do, is something like: history addFirst: workspace content. history := history copyFrom: 1 to: (history size min: 5). Alexandre On 20 Jan 2009, at 11:15, StÃ©phane Ducasse wrote: > yes > so you always add to your collection but you do not have to have 5 > instance variables > and have a counter and also always add at the icunter value or simply > do a modulo: 5 + 1 > > stef > > On Jan 20, 2009, at 10:24 AM, Alexandre Bergel wrote: > >> Humm... Ideally, the history should contains the most recent >> workspace >> contents doesn't it? >> >> Alexandre >> >> >> On 20 Jan 2009, at 10:17, StÃ©phane Ducasse wrote: >> >>> why don't you use a "circular" array using atWrap >>> >>> atWrap: index put: value >>> "Store value into the index'th element of the receiver. If index >>> is >>> out >>> of bounds, let it wrap around from the end to the beginning until >>> it >>> is in bounds. Answer value." >>> >>> ^ self at: index - 1 \\ self size + 1 put: value >>> >>> :) >>> >>> On Jan 20, 2009, at 9:44 AM, Alexandre Bergel wrote: >>> >>>>>>> Neat behaviour - I'll have to try it out (like, what happens >>>>>>> when >>>>>>> you have 5 open workspaces - do they all have access to the same >>>>>>> list of history? Just something to try). >>>>>>> >>>>>>> What about contents of workspace variables? Are those stored in >>>>>>> the >>>>>>> history as well? >>>>>> >>>>>> Actually, I seldom reuse variables across workspaces and have no >>>>>> more >>>>>> than 2 or 3 workspace at the same time. >>>>>> What would be the ideal scenario for variables? >>>>>> >>>>>> Thanks for your words, >>>>>> Alexandre >>>> >>>> The history for workspace contents has 5 slots. Slots are filled >>>> upon >>>> workspace deletion: when you close a workspace, its content is >>>> inserted in the history. Only the last 5 contents are remembered. >>>> Other are forgotten. >>>> >>>> It is easy to increase this limit although. >>>> >>>> Cheers, >>>> Alexandre >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 >>> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> _______________________________________________ >> 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 > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 20, 2009

Re: [Pharo-project] uiTheme Standard Squeak uses ~96% CPU

by Gary Chambers

It appears to be the case that for StandardSqueak the pane splitters are constantly showing damage and, hence, being redrawn... Regards, Gary. ----- Original Message ----- From: "Gary Chambers" <gazzaguru2(a)btinternet.com> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Tuesday, January 20, 2009 11:31 AM Subject: Re: [Pharo-project] uiTheme Standard Squeak uses ~96% CPU Confirmed and investigating... Regards, Gary. ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: "Pharo Development" <Pharo-project(a)lists.gforge.inria.fr> Sent: Tuesday, January 20, 2009 8:31 AM Subject: [Pharo-project] uiTheme Standard Squeak uses ~96% CPU http://code.google.com/p/pharo/issues/detail?id=454&can=1&colspec=ID%20Type… Issue 454: uiTheme Standard Squeak uses ~96% CPU â¹ Prev 454 of 454 1 person starred this issue and may be notified of changes. Back to list Status: New Owner: ---- Add a comment andmake changes below Reported by wsgibson1967, Today (5 hours ago) I know. As much as I really like the Watery 2 uiTheme theme I also really like to use the Standard Squeak theme. I have found on both my Mac and Windows systems that when using the Standard Squeak theme with Pharo (core or dev) that the CPU usage will go very high. If a normal amount of windows are open the CPU usage goes upwards to 96%. I do not get this with the Watery 2 or Soft Squeak themes. In case this is useful, I am using TrueType fonts that are standard to each platform. To reproduce: 1) Change to Standard Squeak theme 2) Open two code browsers and select methods from any class (just opening browsers without drilling down to methods do not produce as much of an effect) 3) Open a Test Runner window 4) Open a Monticello Browser The CPU will increase to roughly 96%. I also would like to mention that you guys have done an INCREDIBLE job with Pharo! I am totally impressed with the amount of work done with Pharo as well as its quality. Thank you for stepping up to the challenge! _______________________________________________ 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

Jan. 20, 2009

Re: [Pharo-project] uiTheme Standard Squeak uses ~96% CPU

by Gary Chambers

Confirmed and investigating... Regards, Gary. ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: "Pharo Development" <Pharo-project(a)lists.gforge.inria.fr> Sent: Tuesday, January 20, 2009 8:31 AM Subject: [Pharo-project] uiTheme Standard Squeak uses ~96% CPU http://code.google.com/p/pharo/issues/detail?id=454&can=1&colspec=ID%20Type… Issue 454: uiTheme Standard Squeak uses ~96% CPU â¹ Prev 454 of 454 1 person starred this issue and may be notified of changes. Back to list Status: New Owner: ---- Add a comment andmake changes below Reported by wsgibson1967, Today (5 hours ago) I know. As much as I really like the Watery 2 uiTheme theme I also really like to use the Standard Squeak theme. I have found on both my Mac and Windows systems that when using the Standard Squeak theme with Pharo (core or dev) that the CPU usage will go very high. If a normal amount of windows are open the CPU usage goes upwards to 96%. I do not get this with the Watery 2 or Soft Squeak themes. In case this is useful, I am using TrueType fonts that are standard to each platform. To reproduce: 1) Change to Standard Squeak theme 2) Open two code browsers and select methods from any class (just opening browsers without drilling down to methods do not produce as much of an effect) 3) Open a Test Runner window 4) Open a Monticello Browser The CPU will increase to roughly 96%. I also would like to mention that you guys have done an INCREDIBLE job with Pharo! I am totally impressed with the amount of work done with Pharo as well as its quality. Thank you for stepping up to the challenge! _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 20, 2009