- Pharo-dev - lists.pharo.org

[Pharo-project] Extracting methods to traits
by Alexandre Bergel Jan. 17, 2009

Jan. 17, 2009

Dear List, A method may be moved to a trait by pressing Cmd-e (or selecting the menu entry 'move method into a new trait'). This version contains an improvement of TOBCmdMoveToTrait. Before doing the refactoring, the method is checked first whether some instance variables are accessed. In that case, a popup window offers few options. A list of possible trait names are also offered to select the trait the method should be moved in. I think that if you execute any load*OB method, you will get this. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

3 4

[Pharo-project] {Spam?} Re: AlignementMorphBob1 removed
by Bill Schwab Jan. 17, 2009

Jan. 17, 2009

Stef, There is nothing to stop us and others from having fun on top of a clean system with a user interface that can meet the expectations of users, paying and otherwise. The cleanup is long overdue and very much starting to show. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 >>> stephane.ducasse(a)inria.fr 1/15/2009 3:47:19 PM >>> :) Jannik understood today why we forked :) and why we were really thinking that people are not serious when they want to keep squeak as it was. We cannot attract all the smart guys we want with a system like that. So we are improving :) This is sad because there are so much fun stuff. But fun does not mean shitty. So we will rebuild them. I hope that people will have fun building cool new fun tools and apps in Pharo. The isKindOf: plague is also terrrrrrrible. I learned about the ownerThatIsA: today (arghhhhhhhhhhhhhhhhhhhhhh). Morphic is the proof that graph traversal as programming paradigm is doomed (cf. K. Lieberherr moto - I think all his queries are doomed too -ok you may get something more flexible, dynamic but at which price and for which real use case...) >> remove AlignmentMorphBob1 > > YES, a dream come true ;-) > > michael I'm sad but the next on my pirate boat board "planche" are - BookMorph and friends -- don't we like class depending on their subclasses - yeah. - Project (we will have to pay a bit more attention) Once etoy is finally removed, will restart to work on that and these freaks are out we will really be on a cleaner world. Stef _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

2 1

[Pharo-project] AlignementMorphBob1 removed
by StÃ©phane Ducasse Jan. 17, 2009

Jan. 17, 2009

Hi all with jannik we published two slice in the inbox to clean some dependencies: One remove onwerOfThatClassIs:orA: the other one merge AlignementMorphBob1 into AlignementMorph remove AlignmentMorphBob1 remove ThreadProjectNavigator and damage a bit more Project :) I would appreciate if somebody can have a look and give feedback. This would be good that we got more code review in pharo. Stef

4 4

Re: [Pharo-project] {Spam?} Workspace Enhancement
by Bill Schwab Jan. 17, 2009

Jan. 17, 2009

Alexandre, I think it makes sense for a workspace (the shell/tool type) to warn before going away, but I agree that being prompted for every inspector that I want to close is a pain. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 >>> Alexandre.Bergel(a)inria.fr 1/16/2009 6:12:07 PM >>> Dear List, Added history to Workspace. When you close a workspace now you will not be bothered with a popup window asking you whether you sure you want to close the window. In the workspace you have access to the historic of the last 5 previous contents.. Click on the right top icon of a workspace to get access to the previous contents. Tools-AlexandreBergel.137 in PharoInbox Issue #449 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

2 1

Re: [Pharo-project] {Spam?} about printOnDelimiter vs asStringOn: delimiter:
by Bill Schwab Jan. 16, 2009

Jan. 16, 2009

Stef, In keeping with print==developer, display==user, the idea of the developer representation is to quote the text so that it looks like the literal syntax. At least that is what I have always thought it was about. Does that help? Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 >>> stephane.ducasse(a)inria.fr 1/16/2009 2:57:57 PM >>> vw has also the printOn: versus displayString distinction. But here the point to have ' inside the string (ie the printString of the contained element ) does not make too much sense to me. stef On Jan 16, 2009, at 8:44 PM, Bill Schwab wrote: > Stef, > > I suspect that Object Arts would favor #printOn:delimiter:. They > would > also probably have a #displayOn:delimeter: method. Their approach is > that one 'displays' for users and 'prints' for developers; they > generally don't much like #as* methods, with the exception of true > conversion methods (such as #asOrderedCollection, etc.). > #displayOn: is > used my morphic, which will cause me some hassles some time soon. > > FWIW. > > Bill > > > > > Wilhelm K. Schwab, Ph.D. > University of Florida > Department of Anesthesiology > PO Box 100254 > Gainesville, FL 32610-0254 > > Email: bschwab(a)anest.ufl.edu > Tel: (352) 273-6785 > FAX: (352) 392-7029 > > >>>> stephane.ducasse(a)inria.fr 1/16/2009 12:55:53 PM >>> > Hi all > > I would like to have your point of view on the following: > on the class collection there are two methods > > asStringOn: aStream delimiter: delimString > asStringOn: aStream delimiter: delimString last: lastDelimString > > > printOn: aStream delimiter: delimString > printOn: aStream delimiter: delimString last: lastDelimString > > which are nearly doing the same. > I suggest to remove the printOn: version > > since it prints: > '1'', ''2'' & ''3'. > while asString > '1, 2 & 3' > > I do not see any use of the printOn version and there is no sender > (except tests that I will remove :). > > > Stef > > > _______________________________________________ > 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

1 0

Re: [Pharo-project] {Spam?} about printOnDelimiter vs asStringOn: delimiter:
by Bill Schwab Jan. 16, 2009

Jan. 16, 2009

Stef, I suspect that Object Arts would favor #printOn:delimiter:. They would also probably have a #displayOn:delimeter: method. Their approach is that one 'displays' for users and 'prints' for developers; they generally don't much like #as* methods, with the exception of true conversion methods (such as #asOrderedCollection, etc.). #displayOn: is used my morphic, which will cause me some hassles some time soon. FWIW. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 >>> stephane.ducasse(a)inria.fr 1/16/2009 12:55:53 PM >>> Hi all I would like to have your point of view on the following: on the class collection there are two methods asStringOn: aStream delimiter: delimString asStringOn: aStream delimiter: delimString last: lastDelimString printOn: aStream delimiter: delimString printOn: aStream delimiter: delimString last: lastDelimString which are nearly doing the same. I suggest to remove the printOn: version since it prints: '1'', ''2'' & ''3'. while asString '1, 2 & 3' I do not see any use of the printOn version and there is no sender (except tests that I will remove :). Stef _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

2 1

[Pharo-project] about printOnDelimiter vs asStringOn: delimiter:
by StÃ©phane Ducasse Jan. 16, 2009

Jan. 16, 2009

Hi all I would like to have your point of view on the following: on the class collection there are two methods asStringOn: aStream delimiter: delimString asStringOn: aStream delimiter: delimString last: lastDelimString printOn: aStream delimiter: delimString printOn: aStream delimiter: delimString last: lastDelimString which are nearly doing the same. I suggest to remove the printOn: version since it prints: '1'', ''2'' & ''3'. while asString '1, 2 & 3' I do not see any use of the printOn version and there is no sender (except tests that I will remove :). Stef

1 0

Jan. 16, 2009

testAsCommaString {OrderedCollection new. Set new.} do: [ :coll | self assert: coll asCommaString = ''. coll add: 1. self assert: coll asCommaString = '1'. coll add: 2; add: 3. self assert: coll asCommaString = '1, 2, 3']. I was never said that elements are iterate in a set the same way that they are added. Stef

2 2

Re: [Pharo-project] [squeak-dev] Mac OS X VM (Squeak 3.8.20beta1U) issue
by John M McIntosh Jan. 16, 2009

Jan. 16, 2009

Ok, what I'm going to do here is push out a 3.8.21 later today. I will revert to the old behaviour, however this will have a info.plist flag that allows you choose the new mmap performance since it does gain a few hundred milliseconds of time on a launch. The new behaviour has I believe these two bugs which are show stoppers for general release. (a) Save image when image is on a NFS drive, does not work. VM locks up, image file is truncated. (b) Sporadic reports of image write failing when on local hard drive. I will retain the new behaviour for the iPhone VM since the saving is on the order of seconds. On 14-Jan-09, at 7:53 AM, John M McIntosh wrote: > Ok, well I'll push out a 3.8.21b1 later today. > > On 14-Jan-09, at 7:25 AM, Alain Fischer wrote: > >> The server is Mac OS X 10.5 (Darwin Kernel Version 9.6.0) >> >> On 14 janv. 09, at 16:12, John M McIntosh wrote: >> >>> Ok, well it seems there is a problem with mmap and mapping files >>> on NFS drives under older versions of linux. >>> So is the server involved linux? >>> >>> Obviously I can see a 3.8.21 series VM being generated tomorrow.. -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

1 1

[Pharo-project] Pharo name conflict
by David Hammond Jan. 15, 2009

Jan. 15, 2009

Hi, I don't intend to cause a big fuss, but I have a concern about the name of your project. I first became aware of your project yesterday when I ran a Google search for the word "pharo". This is the name I had chosen for my open source PHP framework project back in January of 2008. At the time, the Smalltalk-related Pharo project did not yet exist, and the Google search results yielded nothing at all similar or relevant to the project I wanted to start. I purchased pharo.org that month (with trac.pharo.org, svn.pharo.org, and apt-trunk.pharo.org currently in active use) and made a teaser post about the project on my blog: http://www.webdevout.net/tidings/2008/01/15/the-pyramids-werent-built-in-a-… My intention is to release the Pharo PHP framework under a BSD license and not profit directly from the project. I have no stakes in preserving the exclusiveness of the "Pharo" name aside from avoiding possible confusion. But I do believe that the name conflict is an issue of concern, since both of our projects are directly related to programming languages.

6 9