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

Re: [Pharo-project] {Spam?} Re: AlignementMorphBob1 removed

by Michael Roberts

Hi, do you see that your recent mails have spam in the subject?.... Mike

Jan. 17, 2009

Re: [Pharo-project] AlignementMorphBob1 removed

by Michael Roberts

Hi Stef, just curious what you meant that graph traversal as a programming paradigm is doomed? It's quite central to GemStone... good stuff on the continuing cleanup... Mike

Jan. 17, 2009

Re: [Pharo-project] {Spam?} Workspace Enhancement

by Alexandre Bergel

In Visualworks I hate to be prompt for each inspector. Alexandre On 17 Jan 2009, at 01:02, Bill Schwab wrote: > 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 > > _______________________________________________ > 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. 17, 2009

Re: [Pharo-project] {Spam?} Workspace Enhancement

by Bill Schwab

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

Jan. 17, 2009

Re: [Pharo-project] {Spam?} about printOnDelimiter vs asStringOn: delimiter:

by Bill Schwab

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

Jan. 16, 2009

[Pharo-project] Workspace Enhancement

by Alexandre Bergel

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

Jan. 16, 2009

Re: [Pharo-project] {Spam?} about printOnDelimiter vs asStringOn: delimiter:

by StÃ©phane Ducasse

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 >

Jan. 16, 2009

Re: [Pharo-project] {Spam?} about printOnDelimiter vs asStringOn: delimiter:

by Bill Schwab

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

Jan. 16, 2009

[Pharo-project] about printOnDelimiter vs asStringOn: delimiter:

by StÃ©phane Ducasse

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

Jan. 16, 2009

Re: [Pharo-project] how this test can be right

by StÃ©phane Ducasse

Yeap. I will remove it. In the future I plant to certainly integrate the WADictionary with key order... I would like to have a really good collection library. But first the tests :) On Jan 16, 2009, at 9:22 AM, Lukas Renggli wrote: >> I was never said that elements are iterate in a set the same way that >> they are added. > > That's just by chance that it works, because the hash of a > SmallInteger is itself. As soon as the set starts to grow or as soon > as you don't add the numbers in order the result will be different. I > wouldn't write such a test, it depends on the internal implementation > of Set and SmallInteger and is likely to break. > > Cheers, > 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 >

Jan. 16, 2009