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

Re: [Pharo-project] Alien & (using Gofer and Flair)

by Mariano Martinez Peck

On Mon, Jan 11, 2010 at 11:36 AM, Fernando olivero <oliverof(a)lu.unisi.ch>wrote: > Yes, the web page is outdated. Thanks for pointing that out, i will modify > the info now. > > We are working together with Tudor on ConfigurationOfAlien, as soon as > it's finished i'll publish it. > > Cool. Please do it in MetacelloRepository ;) > Fernando > > > > > indeed flair is dead. "le roi est mort vive le roi" > > Fernando could u update the Alien loader? > > > > Stef > > On Jan 11, 2010, at 10:36 AM, John M McIntosh wrote: > > > >> Whoever is looking after the Alien Gofer & Flair loader needs to revisit > the logic since Flair fights and > >> loses against the current Gofer. Which then prevents Alien from loading > as per the instructions supplied > >> on: http://www.squeaksource.com/Alien.html > >> > >> -- > >> > =========================================================================== > >> John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: > squeaker68882 > >> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.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 >

Jan. 11, 2010

Re: [Pharo-project] Alien & (using Gofer and Flair)

by Fernando olivero

Yes, the web page is outdated. Thanks for pointing that out, i will modify the info now. We are working together with Tudor on ConfigurationOfAlien, as soon as it's finished i'll publish it. Fernando > indeed flair is dead. "le roi est mort vive le roi" > Fernando could u update the Alien loader? > > Stef > On Jan 11, 2010, at 10:36 AM, John M McIntosh wrote: > >> Whoever is looking after the Alien Gofer & Flair loader needs to revisit the logic since Flair fights and >> loses against the current Gofer. Which then prevents Alien from loading as per the instructions supplied >> on: http://www.squeaksource.com/Alien.html >> >> -- >> =========================================================================== >> John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 >> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.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

Jan. 11, 2010

Re: [Pharo-project] Interim build server

by Damien Cassou

On Tue, Jan 5, 2010 at 10:27 PM, Michael Roberts <mike(a)mjr104.co.uk> wrote: > -started to publish images at http://pharo.gforge.inria.fr/experimental/ take care that INRIA GForge admins don't like too much stuffs in the web folders. These folders should only be used to host a website. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Jan. 11, 2010

Re: [Pharo-project] inspector and auto-update

by Henrik Johansen

NewInspector is not in Core. What I've noticed is AutoUpdating of inspector values stopping to work under certain circumstances, like a halt raising a debugger while the inspector is selected. Rather certain this has to do with terminated threads caused by debugger opening, similar to a MessageTally never popping up if you encounter a halt in code after MT is started. Cheers, Henry On Jan 11, 2010, at 11:16 14AM, Damien Cassou wrote: > On Wed, Jan 6, 2010 at 9:41 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> However this behaviour is lacking in a >>> PharoCore1.0rc1 >>> Latest update: #10502 >>> >>> So is that what is expected? >>> >> >> auto-update is supposed to work with the inspector... if not, it's a bug. > > the NewInspector does not support this feature if I remember correctly. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 11, 2010

[Pharo-project] Presenter and Project will die aren't they ?

by Mariano Martinez Peck

I mean, the classes will be completely removed ? Just to be sure what I can cleanUp from ImageSegment cheers Mariano

Jan. 11, 2010

Re: [Pharo-project] inspector and auto-update

by Damien Cassou

On Wed, Jan 6, 2010 at 9:41 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> However this behaviour is lacking in a >> PharoCore1.0rc1 >> Latest update: #10502 >> >> So is that what is expected? >> > > auto-update is supposed to work with the inspector... if not, it's a bug. the NewInspector does not support this feature if I remember correctly. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Jan. 11, 2010

Re: [Pharo-project] [ANN] ClaseUseDiscovery tool

by Mariano Martinez Peck

> > This approach of swapping out inactive classes have two big problems: > > - The granularity is too high: the class. As soon as only one method is > invoked, the whole class is recovered. > - It is very common to recover all classes doing a simple action. For > example, searching for implementors or senders of a certain method. Because > of this, when you are developing in your Smalltalk image is very likely that > all classes are recovered in less than 5 minutes of work. It is not useful. > Browsing or editing code seems not to be a problem, thus. Maybe this > approach has more sense in production images rather than development. > > > I guess the next tool you'll make is CUDMethodUseDiscover? ;) > > :) I hope so ;) But it will be MUDMethodUseDiscover hahahaha > Good job, and good luck! > > Cheers, > Henry > > PS. like in MessageTally, maybe a useful constructor method would be one > taking a block as argument, and running trace during its execution? > > Thanks Henrik for the excellent suggestion. Committed in ClassesUseDiscover-MarianoMartinezPeck.33 Now you can do for example: aDiscoverer := CUDClassesUseDiscoverer discoverOn: [Transcript show: 'testDiscoveryOnBlocks']. aDiscoverer activeClassesDuringDiscovery Or aDiscoverer := CUDClassesUseDiscoverer discoverWithTraceOn: [Transcript show: 'testDiscoveryOnBlocks']. aDiscoverer activeClassesDuringDiscovery :) > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 11, 2010

Re: [Pharo-project] Alien & (using Gofer and Flair)

by StÃ©phane Ducasse

Thanks john indeed flair is dead. "le roi est mort vive le roi" Fernando could u update the Alien loader? Stef On Jan 11, 2010, at 10:36 AM, John M McIntosh wrote: > Whoever is looking after the Alien Gofer & Flair loader needs to revisit the logic since Flair fights and > loses against the current Gofer. Which then prevents Alien from loading as per the instructions supplied > on: http://www.squeaksource.com/Alien.html > > -- > =========================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 11, 2010

Re: [Pharo-project] [update 1.1] #11151

by Michael Rueger

On 1/11/2010 9:29 AM, Marcus Denker wrote: > 11150 > ----- > > Issue 1593 : Packages: strange MC packages in need of cleanup (again) > > MC lost lots of classes... so this loads all affected packages (the settings ones). to avoid occurences like this use configuration maps, the only way to get MC to move classes between packages. Michael

Jan. 11, 2010

Re: [Pharo-project] [ANN] ClaseUseDiscovery tool

by Henrik Johansen

On Jan 11, 2010, at 9:59 13AM, Mariano Martinez Peck wrote: > Hi folks: As part of my PhD I started to work with ImageSegment. This week I clean up all the stuff related to class discovery from there. I then wanted to put that extracted code in a separate class. I didn't like that code at all, so at the end I finished rewriting completely this stuff. > > The cool thing is that: > > - I remove all that stuff from ImageSegment (which has nothing to do with that) > - I remove that stuff from classes like Behavior and ClassDescription > - I put all these as an external package that can be perfectly loaded in core > - I rewrote that in style that I like much more. At least for me, it is much more easy to understand and to use now > - I wrote test cases > - I wrote good class comment. > > The repository is: http://www.squeaksource.com/ClaseUseDiscovery > and the license is MIT. > > It is a little project, but maybe someone find it useful. This project only works with Pharo images newer than 1.1 version 11142 > > I paste here the class comment of CUDClassesUseDiscoverer: > > Cheers > > Mariano > > > > > This approach of swapping out inactive classes have two big problems: > > - The granularity is too high: the class. As soon as only one method is invoked, the whole class is recovered. > - It is very common to recover all classes doing a simple action. For example, searching for implementors or senders of a certain method. Because of this, when you are developing in your Smalltalk image is very likely that all classes are recovered in less than 5 minutes of work. It is not useful. Browsing or editing code seems not to be a problem, thus. Maybe this approach has more sense in production images rather than development. I guess the next tool you'll make is CUDMethodUseDiscover? ;) Good job, and good luck! Cheers, Henry PS. like in MessageTally, maybe a useful constructor method would be one taking a block as argument, and running trace during its execution?

Jan. 11, 2010