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

[Pharo-project] [ANN] TDDFacilities

by Hernan Wilkinson

Hi, I uploaded the project TDDFacilities to squeaksource for you to try it. This package provides the following features: 1. It allows to run/step tests from the browsers code panel. No need to save the method, it will save it automatically 2. It disables the Notifier and goes directly to the Debugger 3. It adds a new button to the debugger to create a method when doesNotUndertand is sent. 4. The debugger's size is 3/4 of the screen by default 5. It does not ask for unknown selectors or unused variables when a method is saved 6. The OB test status is always updated, even when debugging a test * To run a test from the code panel: ctr+t * To step a test from the code panel: ctr+r ATTENTION: TO EXECUTE THE TEST FROM THE CODE PANEL, YOU HAVE TO EVALUATE FIRST: OBTextMorphEditorWithShout initialize When using the OTDebugger, The "Create Method" button sometimes generates another debugger. I could no find out why, so help from people that understand how the OTDebugger works will be appreciated. I hope you like it. Any questions just let me know. Bye, Hernan.

June 22, 2009

Re: [Pharo-project] Fwd: SLICE-MovingPointersToExcept in PharoInbox

by Michael Roberts

I can see http://code.google.com/p/pharo/issues/detail?id=899, but only a single entry? cheers, Mike On Mon, Jun 22, 2009 at 3:27 PM, Alexandre Bergel<Alexandre.Bergel(a)inria.fr> wrote: > Hi! > > When I enter my name in the google website, the issue 889 that I > authored is not listed. > Any google code wizard ? > > Cheers, > Alexandre > > > Begin forwarded message: > >> From: Alexandre Bergel <abergel(a)dcc.uchile.cl> >> Date: 18 June 2009 00:56:51 CEDT >> To: Pharo Development <Pharo-project(a)lists.gforge.inria.fr> >> Subject: SLICE-MovingPointersToExcept in PharoInbox >> >> Moved Utilities>>pointersTo: anObject except: objectsToExclude Â into >> Object>>pointersToMeExcept: objectsToExclude. >> The method in Utilities is deprecated. >> >> This is more OO that way. >> >> ISSUE #899 >> >> OB-Tools is impacted, where should I put the new version ? In the >> inbox? >> >> Cheers, >> Alexandre >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel Â http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > 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 >

June 22, 2009

[Pharo-project] Fwd: SLICE-MovingPointersToExcept in PharoInbox

by Alexandre Bergel

Hi! When I enter my name in the google website, the issue 889 that I authored is not listed. Any google code wizard ? Cheers, Alexandre Begin forwarded message: > From: Alexandre Bergel <abergel(a)dcc.uchile.cl> > Date: 18 June 2009 00:56:51 CEDT > To: Pharo Development <Pharo-project(a)lists.gforge.inria.fr> > Subject: SLICE-MovingPointersToExcept in PharoInbox > > Moved Utilities>>pointersTo: anObject except: objectsToExclude into > Object>>pointersToMeExcept: objectsToExclude. > The method in Utilities is deprecated. > > This is more OO that way. > > ISSUE #899 > > OB-Tools is impacted, where should I put the new version ? In the > inbox? > > Cheers, > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

June 22, 2009

Re: [Pharo-project] [update] 10343

by Adrian Lienhard

Ouch. Thanks, Nicolas for finding this. When I rewrote the method last evening I thought PMM only changed _ to :=. I created the following issue: http://code.google.com/p/pharo/issues/detail?id=900 Cheers, Adrian On Jun 22, 2009, at 10:33 , Nicolas Cellier wrote: > Beware: you are re-introducing bugs, at least > http://bugs.squeak.org/view.php?id=6584 in: > CodeLoader>>#exportCodeSegment:classes:keepSource: > > No code should call Symbol allInstances anymore. It is an abstract > class... > Please replace with Symbol allSymbols. > > Nicolas > > 2009/6/22 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > >> this is cool!!!!! >> Thanks a lot gabriel for your help!!!! >> >> Stef >> >> On Jun 22, 2009, at 12:34 AM, Adrian Lienhard wrote: >> >>> Final license cleaning... >>> >>> - Network-Url-GabrielOmarCotelli.7 >>> HTTPUrl>>retrieveContentArgs: >>> - Morphic-GabrielOmarCotelli.326 >>> TransformMorph >> numberOfItemsPotentiallyInViewWith: >>> PluggableListMorph >> numSelectionsInView >>> WorldState class >> deferredExecutionTimeLimit >>> WorldState >> runStepMethodsIn: >>> - Cleaning of PMM methods >>> Object >> isTrait >>> Set class >> rehashAllSets >>> Set class >> new >>> CodeLoader class >> exportCodeSegment:classes:keepSource: >>> FloatTest >> testInfinity3 (deleted) >>> FloatTest >> testZero2 (deleted) >>> >>> >>> This should make Pharo MIT license clean. Will do an audit to be >>> sure >>> tomorrow. >>> >>> Adrian >>> ___________________ >>> http://www.adrian-lienhard.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

June 22, 2009

Re: [Pharo-project] [update] 10343

by Nicolas Cellier

Beware: you are re-introducing bugs, at least http://bugs.squeak.org/view.php?id=6584 in: CodeLoader>>#exportCodeSegment:classes:keepSource: No code should call Symbol allInstances anymore. It is an abstract class... Please replace with Symbol allSymbols. Nicolas 2009/6/22 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > this is cool!!!!! > Thanks a lot gabriel for your help!!!! > > Stef > > On Jun 22, 2009, at 12:34 AM, Adrian Lienhard wrote: > > > Final license cleaning... > > > > - Network-Url-GabrielOmarCotelli.7 > > HTTPUrl>>retrieveContentArgs: > > - Morphic-GabrielOmarCotelli.326 > > TransformMorph >> numberOfItemsPotentiallyInViewWith: > > PluggableListMorph >> numSelectionsInView > > WorldState class >> deferredExecutionTimeLimit > > WorldState >> runStepMethodsIn: > > - Cleaning of PMM methods > > Object >> isTrait > > Set class >> rehashAllSets > > Set class >> new > > CodeLoader class >> exportCodeSegment:classes:keepSource: > > FloatTest >> testInfinity3 (deleted) > > FloatTest >> testZero2 (deleted) > > > > > > This should make Pharo MIT license clean. Will do an audit to be sure > > tomorrow. > > > > Adrian > > ___________________ > > http://www.adrian-lienhard.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 >

June 22, 2009

Re: [Pharo-project] Making GUI'S

by StÃ©phane Ducasse

On Jun 22, 2009, at 9:09 AM, Norbert Hartl wrote: > Hi Bill, > > no need to argue here. I'm on the same track. I think pharo is doing > it really well. I welcome all of these changes, too. My biggest > problem with pharo is that I don't have enough time to participate > more. > > I just thought I heard something like "Absolutely now reason to look > back..." and to this I can't agree. Me too. We look back. I'm sad to see the state of image segment and a lot of cool infrastructure. I think that the infrastructure is key to help improving (for example the notification system introduced by roel...) having a more agile system should help idea and project to come to live and create a rich biotop. For example a real mop could be good for persistency, magritte like meta model..... > But I think I was a bit to > sensible in hearing anything bad :) And of course I don't want to > sound like any of these old complaints that made this project come > to live. So this shall be my excuse if it was taken as such. Don't worry. I think that on a regular basis we will raise the point to make sure people got the idea that we want the better for the better :) :) > > Norbert > > On Sun, 2009-06-21 at 18:21 -0400, Schwab,Wilhelm K wrote: >> Norbert, >> >> There were many reasons to fork from Squeak, and the improvements >> in Pharo would not have been possible any other way. I share your >> frustration at the lack of compatibility between dialects. >> Necessity being the mother of invention (and in this case the >> motiviation for same), I have started chipping away at the problem >> between Dolphin and Pharo. So far, it is little more than a >> collection of facades and helper methods that should reduce the >> hassles of getting my Dolphin code to run on Pharo. When that is >> all that is required, I think we should strive to make such layers >> available. Being different merely for its own sake buys us little. >> >> Bill >> >> >> >> -----Original Message----- >> From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr >> ] On Behalf Of Norbert Hartl >> Sent: Sunday, June 21, 2009 5:27 AM >> To: Pharo-project(a)lists.gforge.inria.fr >> Subject: Re: [Pharo-project] Making GUI'S >> >> On Sat, 2009-06-20 at 21:46 +0200, StÃ©phane Ducasse wrote: >>> + 100000000 :) >>> >>> I want to invent a reasonable future :) >>> >> Your (Marcus and yours) mails sound a bit strange to me. Please let >> us not do this separation between academia and industria again. I >> don't think there is any option but to try to have both: stability >> and improvements. There should be a core that is as common as >> possible. And no, having a common core is not _the_ reason for not >> be able to change anything. For me that were the reasons to fork >> off from squeak. >> >> This dialect thing in smalltalk is really ridiculous. You cannot >> use such basic things like networking even across two different >> dialects. >> So you have to stay inside your own world/box. That is IMHO highly >> in- appropriate for these times. But I know some reasons why it is >> like this and that's the reason I can live with it. But there is >> room for improvement we should not miss. And I hope you can see >> that the support for basic technologies in smalltalk is way behind. >> The beauty and the strength of the language of smalltalk only lays >> within itself. >> >> Maybe I got you wrong but this mails triggered something in me so >> hence the more harsh tone :) >> >> Norbert >> >> On Jun 20, 2009, at 5:22 PM, Marcus Denker wrote: >>> >>>> >>>> On 20.06.2009, at 10:52, Cameron Sanders wrote: >>>> >>>>> They could probably all learn from the other flavors. In fact, the >>>>> cross-smalltalk portability is a negative for smalltalk. >>>>> >>>>> I believe I tried smalltalk/X... that's the natively-compiled one, >>>>> right? So it feels like C++ if you change a root class -- or am I >>>>> confusing it with another? I'm on a new platform and can't check >>>>> what all I installed last year, at the moment. >>>>> >>>>> I like the idea of a compiled version!! And there would be a place >>>>> for it in my world, *if* I could take code from Pharo and load it >>>>> into say, Smalltalk/X, and have it work without a month-long >>>>> debugging session. >>>> >>>> One huge problem with compatibility is always that it reduces any >>>> possibility in evolving/improving the system. If the goal is to be >>>> compatible to e.g. >>>> all of Smalltalk X, Visualworks, Squeak, Gemstone.... than, in the >>>> end, this means we can not do anything anymore, and, most >>>> importantly: we can not do any *fun* things anymore. >>>> >>>> Beeing compatible means reducing what you do to the subset of all >>>> the dialects, and than stop doing anything. >>>> >>>> If I you should choose between a) "inventing the future" and b) "be >>>> compatible to VisualWorks", what would you take? >>>> >>>> And I personally have already choosen for the "inventing the >>>> future" >>>> route, I guess. It makes >>>> no sense to be in Research (and beeing payed those wonderful tiny >>>> salaries) and than do boring stuff. >>>> That makes no sense. >>>> >>>> I personally think that the possibility and duty of working on >>>> interesting things is part of the overall compensation package of >>>> people in Research. >>>> >>>> Marcus >>>> >>>> -- >>>> Marcus Denker - http://marcusdenker.de PLEIAD Lab - Computer >>>> Science >>>> Department (DCC) - University of Chile >>>> >>>> >>>> _______________________________________________ >>>> 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

June 22, 2009

Re: [Pharo-project] [update] 10343

by StÃ©phane Ducasse

this is cool!!!!! Thanks a lot gabriel for your help!!!! Stef On Jun 22, 2009, at 12:34 AM, Adrian Lienhard wrote: > Final license cleaning... > > - Network-Url-GabrielOmarCotelli.7 > HTTPUrl>>retrieveContentArgs: > - Morphic-GabrielOmarCotelli.326 > TransformMorph >> numberOfItemsPotentiallyInViewWith: > PluggableListMorph >> numSelectionsInView > WorldState class >> deferredExecutionTimeLimit > WorldState >> runStepMethodsIn: > - Cleaning of PMM methods > Object >> isTrait > Set class >> rehashAllSets > Set class >> new > CodeLoader class >> exportCodeSegment:classes:keepSource: > FloatTest >> testInfinity3 (deleted) > FloatTest >> testZero2 (deleted) > > > This should make Pharo MIT license clean. Will do an audit to be sure > tomorrow. > > Adrian > ___________________ > http://www.adrian-lienhard.ch/ > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 22, 2009

Re: [Pharo-project] Making GUI'S

by Norbert Hartl

Hi Bill, no need to argue here. I'm on the same track. I think pharo is doing it really well. I welcome all of these changes, too. My biggest problem with pharo is that I don't have enough time to participate more. I just thought I heard something like "Absolutely now reason to look back..." and to this I can't agree. But I think I was a bit to sensible in hearing anything bad :) And of course I don't want to sound like any of these old complaints that made this project come to live. So this shall be my excuse if it was taken as such. Norbert On Sun, 2009-06-21 at 18:21 -0400, Schwab,Wilhelm K wrote: > Norbert, > > There were many reasons to fork from Squeak, and the improvements in Pharo would not have been possible any other way. I share your frustration at the lack of compatibility between dialects. Necessity being the mother of invention (and in this case the motiviation for same), I have started chipping away at the problem between Dolphin and Pharo. So far, it is little more than a collection of facades and helper methods that should reduce the hassles of getting my Dolphin code to run on Pharo. When that is all that is required, I think we should strive to make such layers available. Being different merely for its own sake buys us little. > > Bill > > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Norbert Hartl > Sent: Sunday, June 21, 2009 5:27 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Making GUI'S > > On Sat, 2009-06-20 at 21:46 +0200, StÃ©phane Ducasse wrote: > > + 100000000 :) > > > > I want to invent a reasonable future :) > > > Your (Marcus and yours) mails sound a bit strange to me. Please let us not do this separation between academia and industria again. I don't think there is any option but to try to have both: stability and improvements. There should be a core that is as common as possible. And no, having a common core is not _the_ reason for not be able to change anything. For me that were the reasons to fork off from squeak. > > This dialect thing in smalltalk is really ridiculous. You cannot use such basic things like networking even across two different dialects. > So you have to stay inside your own world/box. That is IMHO highly in- appropriate for these times. But I know some reasons why it is like this and that's the reason I can live with it. But there is room for improvement we should not miss. And I hope you can see that the support for basic technologies in smalltalk is way behind. The beauty and the strength of the language of smalltalk only lays within itself. > > Maybe I got you wrong but this mails triggered something in me so hence the more harsh tone :) > > Norbert > > On Jun 20, 2009, at 5:22 PM, Marcus Denker wrote: > > > > > > > > On 20.06.2009, at 10:52, Cameron Sanders wrote: > > > > > >> They could probably all learn from the other flavors. In fact, the > > >> cross-smalltalk portability is a negative for smalltalk. > > >> > > >> I believe I tried smalltalk/X... that's the natively-compiled one, > > >> right? So it feels like C++ if you change a root class -- or am I > > >> confusing it with another? I'm on a new platform and can't check > > >> what all I installed last year, at the moment. > > >> > > >> I like the idea of a compiled version!! And there would be a place > > >> for it in my world, *if* I could take code from Pharo and load it > > >> into say, Smalltalk/X, and have it work without a month-long > > >> debugging session. > > > > > > One huge problem with compatibility is always that it reduces any > > > possibility in evolving/improving the system. If the goal is to be > > > compatible to e.g. > > > all of Smalltalk X, Visualworks, Squeak, Gemstone.... than, in the > > > end, this means we can not do anything anymore, and, most > > > importantly: we can not do any *fun* things anymore. > > > > > > Beeing compatible means reducing what you do to the subset of all > > > the dialects, and than stop doing anything. > > > > > > If I you should choose between a) "inventing the future" and b) "be > > > compatible to VisualWorks", what would you take? > > > > > > And I personally have already choosen for the "inventing the future" > > > route, I guess. It makes > > > no sense to be in Research (and beeing payed those wonderful tiny > > > salaries) and than do boring stuff. > > > That makes no sense. > > > > > > I personally think that the possibility and duty of working on > > > interesting things is part of the overall compensation package of > > > people in Research. > > > > > > Marcus > > > > > > -- > > > Marcus Denker - http://marcusdenker.de PLEIAD Lab - Computer Science > > > Department (DCC) - University of Chile > > > > > > > > > _______________________________________________ > > > 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

June 22, 2009

Re: [Pharo-project] [update] 10343

by Rob Rothwell

Looks like maybe OCompletion quit working in a Workspace with this update? Rob On Sun, Jun 21, 2009 at 6:34 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > Final license cleaning... > > - Network-Url-GabrielOmarCotelli.7 > HTTPUrl>>retrieveContentArgs: > - Morphic-GabrielOmarCotelli.326 > TransformMorph >> numberOfItemsPotentiallyInViewWith: > PluggableListMorph >> numSelectionsInView > WorldState class >> deferredExecutionTimeLimit > WorldState >> runStepMethodsIn: > - Cleaning of PMM methods > Object >> isTrait > Set class >> rehashAllSets > Set class >> new > CodeLoader class >> exportCodeSegment:classes:keepSource: > FloatTest >> testInfinity3 (deleted) > FloatTest >> testZero2 (deleted) > > > This should make Pharo MIT license clean. Will do an audit to be sure > tomorrow. > > Adrian > ___________________ > http://www.adrian-lienhard.ch/ > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 22, 2009

[Pharo-project] [update] 10343

by Adrian Lienhard

Final license cleaning... - Network-Url-GabrielOmarCotelli.7 HTTPUrl>>retrieveContentArgs: - Morphic-GabrielOmarCotelli.326 TransformMorph >> numberOfItemsPotentiallyInViewWith: PluggableListMorph >> numSelectionsInView WorldState class >> deferredExecutionTimeLimit WorldState >> runStepMethodsIn: - Cleaning of PMM methods Object >> isTrait Set class >> rehashAllSets Set class >> new CodeLoader class >> exportCodeSegment:classes:keepSource: FloatTest >> testInfinity3 (deleted) FloatTest >> testZero2 (deleted) This should make Pharo MIT license clean. Will do an audit to be sure tomorrow. Adrian ___________________ http://www.adrian-lienhard.ch/

June 21, 2009