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

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

by Gary Chambers

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

Jan. 20, 2009

[Pharo-project] using pharo dev I got backgroundcolor crashes

by StÃ©phane Ducasse

in OBPluggableTreeItemwithParentNode>>backgroundcolor OBIndentingListItemMorph>>drawOn: argh!

Jan. 20, 2009

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

by Gary Chambers

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

Jan. 20, 2009

Re: [Pharo-project] [Pharo-Project] Exceptions handling at startUp

by StÃ©phane Ducasse

thanks, excellent. can you add an issue in the bugtracker so that we can keep track of its way to light :) On Jan 20, 2009, at 10:54 AM, Gwenael Casaccio wrote: > Hi, > > I've made a small SLICE (SLICE-ExceptionHandlingAtStartUp- > Gwenael_Casaccio.5) > which capture the exceptions emitted when the startUp methods are > invoked. > If you launch pharo without the display the error is shown on the > console and > on the classical SqueakDebug.log. > > Cheers, > Gwenael > > > _______________________________________________ > 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

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 >

Jan. 20, 2009

[Pharo-project] [Pharo-Project] Exceptions handling at startUp

by Gwenael Casaccio

Hi, I've made a small SLICE (SLICE-ExceptionHandlingAtStartUp-Gwenael_Casaccio.5) which capture the exceptions emitted when the startUp methods are invoked. If you launch pharo without the display the error is shown on the console and on the classical SqueakDebug.log. Cheers, Gwenael

Jan. 20, 2009

Re: [Pharo-project] Workspace Enhancement

by Alexandre Bergel

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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 20, 2009

Re: [Pharo-project] Workspace Enhancement

by Damien Cassou

On Tue, Jan 20, 2009 at 10:15 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > I would prefer to have a better inspector/explorer Lukas reimplemented most Squeak tools using OB (inspector, explorer, debugger, workspace, transcript...). Dale fixed a lot of things in the debugger and things are going very well now. -- Damien Cassou http://damiencassou.seasidehosting.st

Jan. 20, 2009

Re: [Pharo-project] Workspace Enhancement

by StÃ©phane Ducasse

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 >

Jan. 20, 2009

Re: [Pharo-project] Workspace Enhancement

by StÃ©phane Ducasse

yeap! I would prefer to have a better inspector/explorer Stef On Jan 20, 2009, at 9:30 AM, Torsten Bergmann wrote: > Why bother, a simple > > Smalltalk at: #MyVar put: anObject > > will do the job for you if required. Yes, this can lead to a leak if > forgotten - but > typically you will do this for testing purposes and you should not > deploy your > development image (use a clean image and a defined build process). > > SmalltalkMT always provided Workspace variables - but I never used > them > really. Less is sometimes more... > > Bye > Torsten > -- > Psssst! Schon vom neuen GMX MultiMessenger gehÃ¶rt? Der kann`s mit > allen: http://www.gmx.net/de/go/multimessenger > > _______________________________________________ > 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