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

Re: [Pharo-project] Package comments

by Sean P. DeNigris

laurent laffont wrote: > > Why not HelpSystem ? Works quite well to document any package. > I just played with HelpSystem in-depth for the first time and it's really cool. I'll start using it. @Steph: What's the advantage, if any, of DrDoc's approach, and could the two be integrated? Bert suggested hooking custom PackageInfo classes into HelpSystem on the Squeak list @ http://forum.world.st/Documentation-What-about-package-comments-td2062634.h…. Sean -- View this message in context: http://forum.world.st/Package-comments-tp2525056p2526295.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Sept. 3, 2010

Re: [Pharo-project] Issue 2844 in pharo: String>>#numArgs is broken

by Schwab,Wilhelm K

Stef, Does that mean that 1.1 will be patched accordingly? I have been thinking of building a new 1.1 image but can safely postpone that until this is ready if that is the intent. Bill ________________________________________ From: pharo(a)googlecode.com [pharo(a)googlecode.com] Sent: Friday, September 03, 2010 3:23 PM To: Schwab,Wilhelm K Subject: Re: Issue 2844 in pharo: String>>#numArgs is broken Comment #5 on issue 2844 by stephane.ducasse: String>>#numArgs is broken http://code.google.com/p/pharo/issues/detail?id=2844 marcus will integrate it in the 1.1.1 batch he will do soon :) -- You received this message because you starred the issue. You may adjust your notification preferences at: https://code.google.com/hosting/settings

Sept. 3, 2010

Re: [Pharo-project] systemNavigation cleaning

by Lukas Renggli

I agree that SystemNavigation is ugly, but *a lot* of existing code depends on it. Why not just use BrowserEnvironment if you need something convenient and nice? And at some point integrate that into PharoCore? Lukas On 3 September 2010 22:01, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi all > > I'm cleaning SystemNavigation (no comment). > Now I really SystemNavigation to be able to navigate a given environment (instance of SystemDictionary). > Therefore I introduced an analyzedEnvironment and I will funnel most methods to use it. > > Now some queries are doing memory scanning (allBehaviorDo:) so > I would like to use the following semantics for the method names > Â Â Â Â all* will refer to methods that are not respecting the analyzedEnvironment but could scan the complete memory > Â Â Â Â and I would like to introduce their pendant to convey the fact that they only take as input a given environment. > > Example > Â Â Â Â allClasses > Â Â Â Â vs classes > > This would allow us to have in place a nice infrastructure to load and analyse code in a separate environment and > do atomica loading. This was done like that in VW30. > > What do you think. > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli www.lukas-renggli.ch

Sept. 3, 2010

Re: [Pharo-project] systemNavigation cleaning

by James Foster

On Sep 3, 2010, at 1:01 PM, StÃ©phane Ducasse wrote: > Hi all > > I'm cleaning SystemNavigation (no comment). > Now I really SystemNavigation to be able to navigate a given environment (instance of SystemDictionary). > Therefore I introduced an analyzedEnvironment and I will funnel most methods to use it. > > Now some queries are doing memory scanning (allBehaviorDo:) so > I would like to use the following semantics for the method names > all* will refer to methods that are not respecting the analyzedEnvironment but could scan the complete memory > and I would like to introduce their pendant to convey the fact that they only take as input a given environment. > > Example > allClasses > vs classes > > This would allow us to have in place a nice infrastructure to load and analyse code in a separate environment and > do atomica loading. This was done like that in VW30. > > What do you think. This is a very good change and was one of the issues faced with the namespace work. James > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 3, 2010

Re: [Pharo-project] PharoKernel #12121

by Mariano Martinez Peck

On Fri, Sep 3, 2010 at 11:22 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > for me this is simple > - I would like to use a metacello configuration to reload everything > in between > this kernel image and the current 12121 but I do not have the time. > > I was just thinking if this really makes sense or not...Suppose I have the PharoCore image 12121. >From that image, I can shrink it and generate PharoKernel 12121. If I then have a configuration to load the core again, I will have again PharoCore 12121, which I already have, and which I can directly use. So...what is the sense of creating again PharoCore from PharoKernel? A different story is if PharoCore 12121 DOES NOT exist before...so you start from PharoKernel 12121 and THEN create PharoCore....but PharoKernel is a shrink from PharoCore...soo...? I am confused :( cheers mariano > So ... > > On Sep 2, 2010, at 11:08 PM, Lukas Renggli wrote: > > > Very impressive. Can't wait to see Pharo built from such a small image. > > > > Lukas > > > > On 2 September 2010 23:02, Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: > >> Hi, > >> > >> I uploaded the new version of PharoKernel #12121: > >> > >> > https://gforge.inria.fr/frs/download.php/27438/PharoKernel-1.2-12121.zip > >> > >> The shrinking process is now based on packages. > >> > >> Cheers > >> -- Pavel > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > > > > > > > > -- > > Lukas Renggli > > 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 >

Sept. 3, 2010

[Pharo-project] Pharocasts: Deploy Seaside with Cherokee Web Server

by laurent laffont

Hi, New screencast from Christoph: Learn how to - install Cherokee Web Server on Ubuntu Linux through Launchpad - configure Cherokee to serve static files for a Seaside application - start an headless Seaside image http://pharocasts.blogspot.com/2010/09/deploy-seaside-with-cherokee-web-ser… Note: If you have any suggestions for improvement, Cherokee + Seaside tips and tricks you want to share or saw something that is plain wrong or could be described in more detail to make it easier to understand, feel free to add a comment and we will update the screencast accordingly to improve it. Cheers, Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/

Sept. 3, 2010

Re: [Pharo-project] [OSProcess] Proposal for Pharo 1.2 compatibility

by David T. Lewis

On Fri, Sep 03, 2010 at 08:57:55PM +0200, St?phane Ducasse wrote: > Hi david > > I think that you should wait. 1.1 is stable and out. Thanks Stef, good advice, that's what I will do. Dave > 1.2 is in flux. When 1.2 gets in beta this will be time to settle down things. > Cyrille I know why you want 1.2 version else you cannot build a hudson working solution > to run top of the edge version. Now I will do the changes suggested by henrik to get a backward compatible version. > I suggest to use metacello to control version now I understand that people want to avoid branching > now it means that we (the people working on the unstable stream may lack tools but this is ok). > > Stef > > On Sep 3, 2010, at 6:30 PM, David T. Lewis wrote: > > > On Fri, Sep 03, 2010 at 01:03:31PM +0200, Cyrille Delaunay wrote: > >> Hello, > >> > >> I would suggest to replace the two methods > >> -------------------------------------------------------------- > >> OSPRocess class >> platformName > >> "After Squeak version 3.6, #platformName was moved to SmalltalkImage " > >> > >> ^ ((Smalltalk classNamed: 'SmalltalkImage') > >> ifNil: [^ Smalltalk platformName]) current platformName > >> > >> OSPRocess class >> osVersion > >> "After Squeak version 3.6, #osVersion was moved to SmalltalkImage " > >> > >> ^ ((Smalltalk classNamed: 'SmalltalkImage') > >> ifNil: [^ Smalltalk osVersion]) current osVersion > >> > >> -------------------------------------------------------------- > >> by: > >> ------------------------------------------------------------- > >> OSProcess class >> platformName > >> ^ ((Smalltalk classNamed: 'OSPlatform') > >> ifNil: [ > >> (Smalltalk classNamed: 'SmalltalkImage') current > >> ifNil: [^ Smalltalk platformName]]) platformName > >> > >> OSProcess class >> osVersion > >> ^ ((Smalltalk classNamed: 'OSPlatform') > >> ifNil: [ > >> (Smalltalk classNamed: 'SmalltalkImage') current > >> ifNil: [^ Smalltalk osVersion]]) osVersion > >> ------------------------------------------------------------ > >> > >> to avoid deprecation messages when using it in Pharo 1.2. Does it looks > >> good? I'm not able to publish on the squeaksource repository > > > > This failed on the first Pharo image that I tried, which was a > > Pharo-1.1-11400-rc2dev10.06.1 image. I think this is the subject > > of some recent refactoring, so I'm not sure if it's safe to use > > it yet (will somebody try to load OSProcess in one of the images > > that has OSPlatform but that does not yet have the #platformName > > refactoring?). > > > > I expect that there are several versions of Pharo in general > > circulation, so can someone give me some guidance as to whether > > it is safe to code for "OSPlatform current platformName" as the > > expected idiom on Pharo, or should we wait a while and live with > > the deprecation warnings? > > > > Thanks, > > > > Dave > > > > > > _______________________________________________ > > 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

Sept. 3, 2010

[Pharo-project] [ANN] New 1.2 unstable

by StÃ©phane Ducasse

https://gforge.inria.fr/frs/download.php/27445/PharoCore-1.2-12123.zip Stef

Sept. 3, 2010

Re: [Pharo-project] TestSprinter

by Alexandre Bergel

OB and O2 are two distinct efforts for providing code browsers. The only cause I see behind this unfortunate situation is the lake of resources. Cheers, Alexandre On 3 Sep 2010, at 13:07, TimM wrote: > On 02/09/2010 23:54, Alexandre Bergel wrote: >>> A keyboard shortcut to run the tests directly without a mouse (ideally a way to run the single test my cursor is on, its suite of tests, and all tests like you imply above). >> >> Are you aware of Cmd-t in OB(2) ? > > I have to confess that is an area I don't understand in Pharo - which Browser system am I using? OB, OB2, isn't there another one as well? > > I don't understand why there seems to be different types of browsers - and it seems that different versions of pharo have shipped with different ones making it even more confusing? > > So in 1.1 am I just using OB? And should I be using OB2? (Or why wouldn't I use OB2?) > > I'll move this to the user list if thats more appropriate. > > Tim > > > > _______________________________________________ > 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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 3, 2010

[Pharo-project] [update 1.2] #12123

by StÃ©phane Ducasse

12123 ----- - Issue 2890: Some isNil ifTrueifFalse -> ifNil:. Thanks Guillermo Polito. - Issue 2907: undeprecate Smalltalk os so that we can write Smalltalk os versionName and Smalltalk os platformName - Issue 2896: Make sure system notifications for Smalltalk are up-to-date. Thanks Eliot Miranda and Adrian Leinhard. - Issue 2893: Network bugs. Thanks Andreas Raab.

Sept. 3, 2010