October 2008 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] MethodFinder

by StÃ©phane Ducasse

I created a new package MethodFinder and published it to Pharo. I really like this tool. So I will give a try to clean it. On Oct 7, 2008, at 8:21 PM, StÃ©phane Ducasse wrote: > Hi > > marcus removed methodFinder and I understand the reasons (lot of > list of old method selectors hardcoded and not maintained). > Still I think that MethodFinder was a really cool tool. > So is there somebody that would like to have a look and take an old > pharo version, package MethodFinder > and clean it. This would be great. > > Stef and Marcus > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 8, 2008

Re: [Pharo-project] [updates] 10088

by StÃ©phane Ducasse

I put them back apparently I may have removed them during my journey to etoy hell. Please check if this is ok. Stef On Oct 8, 2008, at 3:28 PM, Gary Chambers wrote: > Seems ok when applied to a 3.9 image. > Note that these are modified method, not removals: > > BookMorph>>goToPageMorph: transitionSpec: runTransitionScripts: > BookMorph>>goToPageMorph: transitionSpec: > > Gary. > > ----- Original Message ----- From: "Marcus Denker" <denker(a)iam.unibe.ch > > > To: "Pharo Development" <pharo-project(a)lists.gforge.inria.fr> > Sent: Wednesday, October 08, 2008 12:59 PM > Subject: Re: [Pharo-project] [updates] 10088 > > > > On 08.10.2008, at 13:43, StÃ©phane Ducasse wrote: > >> >> On Oct 8, 2008, at 11:35 AM, Adrian Lienhard wrote: >> >>> @Marcus: thanks! >>> >>> @all: >>> I've run the tests and currently we have 3 tests that are not >>> green. I've filed issues for two. The third one is due to a DNU >>> in BookMorph (actually "BookMorph new" does not work anymore). >>> What is the status of BookMorph? Is this a candidate to be >>> removed or should we fix it? >> >> on one hand I like it but on the other hand it is introducing a >> lot of cruft in the system. >> I imagine that this is the gotoPage: withTransitionSpec: that >> (marcus not sure) removed. > > > Seems it was this change: > > Name: MorphicExtras-stephane.ducasse.53 > Author: stephane.ducasse > Time: 28 September 2008, 5:01:33 pm > UUID: b95626df-9568-49ef-8568-5b689a0bc8be > Ancestors: MorphicExtras-stephane.ducasse.52 > > Etoy cleaning from gary (continued) > Removed UndefinedObjectTest>>testNewTileMorphRepresentative > Removed BooleanTest>>testNewTileMorphRepresentative > Removed BookMorph>>chooseAndRevertToVersion > Removed BookMorph>>revertToCheckpoint: secsSince1901 > BookMorph>>installRollBackButtons > BookMorph>>methodHolderVersions > BookMorph>>methodHolders > BookMoprh>>goToPageMorph: transitionSpec: runTransitionScripts: > BookMorph>>goToPageMorph: transitionSpec: > TabbedPalette>>selectTab: cleaned > Removed TabbedPalette>>becomeStandPalette > Removed>>currentPlayerDo: and fixed sender > EncodedCharSet fixed initialize > > > > -- > Marcus Denker -- denker(a)iam.unibe.ch > http://www.iam.unibe.ch/~denker > > > _______________________________________________ > 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 >

Oct. 8, 2008

Re: [Pharo-project] [updates] 10088

by StÃ©phane Ducasse

Yeap 10089 should recover that. When I was curving etoy. Stef >>> >>> @all: >>> I've run the tests and currently we have 3 tests that are not >>> green. I've filed issues for two. The third one is due to a DNU in >>> BookMorph (actually "BookMorph new" does not work anymore). What >>> is the status of BookMorph? Is this a candidate to be removed or >>> should we fix it? >> >> on one hand I like it but on the other hand it is introducing a lot >> of cruft in the system. >> I imagine that this is the gotoPage: withTransitionSpec: that >> (marcus not sure) removed. > > > Seems it was this change: > > Name: MorphicExtras-stephane.ducasse.53 > Author: stephane.ducasse > Time: 28 September 2008, 5:01:33 pm > UUID: b95626df-9568-49ef-8568-5b689a0bc8be > Ancestors: MorphicExtras-stephane.ducasse.52 > > Etoy cleaning from gary (continued) > Removed UndefinedObjectTest>>testNewTileMorphRepresentative > Removed BooleanTest>>testNewTileMorphRepresentative > Removed BookMorph>>chooseAndRevertToVersion > Removed BookMorph>>revertToCheckpoint: secsSince1901 > BookMorph>>installRollBackButtons > BookMorph>>methodHolderVersions > BookMorph>>methodHolders > BookMoprh>>goToPageMorph: transitionSpec: runTransitionScripts: > BookMorph>>goToPageMorph: transitionSpec: > TabbedPalette>>selectTab: cleaned > Removed TabbedPalette>>becomeStandPalette > Removed>>currentPlayerDo: and fixed sender > EncodedCharSet fixed initialize > > > > -- > Marcus Denker -- denker(a)iam.unibe.ch > http://www.iam.unibe.ch/~denker > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 8, 2008

Re: [Pharo-project] [updates] 10088

by Gary Chambers

Seems ok when applied to a 3.9 image. Note that these are modified method, not removals: BookMorph>>goToPageMorph: transitionSpec: runTransitionScripts: BookMorph>>goToPageMorph: transitionSpec: Gary. ----- Original Message ----- From: "Marcus Denker" <denker(a)iam.unibe.ch> To: "Pharo Development" <pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, October 08, 2008 12:59 PM Subject: Re: [Pharo-project] [updates] 10088 On 08.10.2008, at 13:43, StÃ©phane Ducasse wrote: > > On Oct 8, 2008, at 11:35 AM, Adrian Lienhard wrote: > >> @Marcus: thanks! >> >> @all: >> I've run the tests and currently we have 3 tests that are not green. >> I've filed issues for two. The third one is due to a DNU in BookMorph >> (actually "BookMorph new" does not work anymore). What is the status of >> BookMorph? Is this a candidate to be removed or should we fix it? > > on one hand I like it but on the other hand it is introducing a lot of > cruft in the system. > I imagine that this is the gotoPage: withTransitionSpec: that (marcus not > sure) removed. Seems it was this change: Name: MorphicExtras-stephane.ducasse.53 Author: stephane.ducasse Time: 28 September 2008, 5:01:33 pm UUID: b95626df-9568-49ef-8568-5b689a0bc8be Ancestors: MorphicExtras-stephane.ducasse.52 Etoy cleaning from gary (continued) Removed UndefinedObjectTest>>testNewTileMorphRepresentative Removed BooleanTest>>testNewTileMorphRepresentative Removed BookMorph>>chooseAndRevertToVersion Removed BookMorph>>revertToCheckpoint: secsSince1901 BookMorph>>installRollBackButtons BookMorph>>methodHolderVersions BookMorph>>methodHolders BookMoprh>>goToPageMorph: transitionSpec: runTransitionScripts: BookMorph>>goToPageMorph: transitionSpec: TabbedPalette>>selectTab: cleaned Removed TabbedPalette>>becomeStandPalette Removed>>currentPlayerDo: and fixed sender EncodedCharSet fixed initialize -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 8, 2008

Re: [Pharo-project] [OT] Rewrite in C++

by Bill Schwab

Torsten, Pharo will be different from Squeak, but it should be a Smalltalk, not what we think a C* (C/C++/Java/Python/C#/etc.) programmer would to to Smalltalk to "fix" it. Without specific complaints, it is hard to know whether there is an unfortunate synergy among some of Squeak's quirks, or whether the developer never quite mastered Smalltalk. On the former, the number crunching side of the project is probably something that I would dump into a C-callable C++ dll/so. Plugins, if used, would be a real pain in the neck, at least from my perspective. That would be the case both because of the the development cycle, and because C++ operators and precedence will have advantages over Slang for translating equations into code. Plugins would add mixed-language hassles without much benefit beyond speed. IMHO, the Squeak community has a bias against FFI. What I do not know is whether that is justified on technical grounds. Dolphin's FFI works very well, so if there is a problem, we should fix it, not discourage the concept. Another consideration is the devices in question. I have tried to avoid palm-top devices on the grounds that tablets are "real computers" with much longer product life cycles, more computing power and far fewer gimmicks than their smaller cousins. My fear is that by the time I figure out the oddities of one system, it will be replaced by another, and I would have been better off prototyping on something more stable and powerful. That said, I'm glad to people tackling small machines, because I might really need them some day :) 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 >>> astares(a)gmx.de 10/08/08 4:13 AM >>> Found a program currently written in Squeak called TaalPulse (see http://taalpulse.net) >From the news page: "For the technically inclined, the new version of TaalPulse is being written in C++ using the Qt 4.4 user-interface toolkit. " In the forum the developer Guillaume Pothier explains his decision: http://sourceforge.net/mailarchive/forum.php?thread_name=8caa8ded0804172152… "Squeak was the only truly portable solution, and it still is to this day" "Although I haven't programmed in C++ for years I am confident it will be easier than Smalltalk" Could not really understand the move to C++, it's sad and at least this rings some bells that Pharo has to be different than Squeak ... Bye Torsten -- Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten Browser-Versionen downloaden: http://www.gmx.net/de/go/browser _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 8, 2008

Re: [Pharo-project] [updates] 10088

by Adrian Lienhard

On Oct 8, 2008, at 13:43 , StÃ©phane Ducasse wrote: > > On Oct 8, 2008, at 11:35 AM, Adrian Lienhard wrote: > >> @Marcus: thanks! >> >> @all: >> I've run the tests and currently we have 3 tests that are not >> green. I've filed issues for two. The third one is due to a DNU in >> BookMorph (actually "BookMorph new" does not work anymore). What is >> the status of BookMorph? Is this a candidate to be removed or >> should we fix it? > > on one hand I like it but on the other hand it is introducing a lot > of cruft in the system. then maybe somebody interested could extract the parts of Morphic that are valuable and put them in a project on SqueakSource? Adrian

Oct. 8, 2008

Re: [Pharo-project] [updates] 10088

by Marcus Denker

On 08.10.2008, at 13:43, StÃ©phane Ducasse wrote: > > On Oct 8, 2008, at 11:35 AM, Adrian Lienhard wrote: > >> @Marcus: thanks! >> >> @all: >> I've run the tests and currently we have 3 tests that are not >> green. I've filed issues for two. The third one is due to a DNU in >> BookMorph (actually "BookMorph new" does not work anymore). What is >> the status of BookMorph? Is this a candidate to be removed or >> should we fix it? > > on one hand I like it but on the other hand it is introducing a lot > of cruft in the system. > I imagine that this is the gotoPage: withTransitionSpec: that > (marcus not sure) removed. Seems it was this change: Name: MorphicExtras-stephane.ducasse.53 Author: stephane.ducasse Time: 28 September 2008, 5:01:33 pm UUID: b95626df-9568-49ef-8568-5b689a0bc8be Ancestors: MorphicExtras-stephane.ducasse.52 Etoy cleaning from gary (continued) Removed UndefinedObjectTest>>testNewTileMorphRepresentative Removed BooleanTest>>testNewTileMorphRepresentative Removed BookMorph>>chooseAndRevertToVersion Removed BookMorph>>revertToCheckpoint: secsSince1901 BookMorph>>installRollBackButtons BookMorph>>methodHolderVersions BookMorph>>methodHolders BookMoprh>>goToPageMorph: transitionSpec: runTransitionScripts: BookMorph>>goToPageMorph: transitionSpec: TabbedPalette>>selectTab: cleaned Removed TabbedPalette>>becomeStandPalette Removed>>currentPlayerDo: and fixed sender EncodedCharSet fixed initialize -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Oct. 8, 2008

Re: [Pharo-project] [updates] 10088

by StÃ©phane Ducasse

On Oct 8, 2008, at 11:35 AM, Adrian Lienhard wrote: > @Marcus: thanks! > > @all: > I've run the tests and currently we have 3 tests that are not green. > I've filed issues for two. The third one is due to a DNU in > BookMorph (actually "BookMorph new" does not work anymore). What is > the status of BookMorph? Is this a candidate to be removed or should > we fix it? on one hand I like it but on the other hand it is introducing a lot of cruft in the system. I imagine that this is the gotoPage: withTransitionSpec: that (marcus not sure) removed. Stef > > > Adrian > > > On Oct 8, 2008, at 10:15 , Marcus Denker wrote: > >> Issue 218: Enhancements collected by gary and simon >> 1. Fixed flaky borwser comment text area sometime not showing. >> 2. Added getArgumentPermutation to support RefactoringEngine. >> 3. Fixes to CanvasCharacterScanner and MultiCanvasCharacterScanner >> to correctly align the first line of text >> when centered/justifed etc. >> 4. Added more constant names to Character class. >> 5. Modified ConnectionQueue to not accept connections when queue >> is full. >> 6. Changed GrafPort to answer a MultiDisplayScanner when >> appropriate (allows subclasses of >> MultiNewParagraph). >> 7. NaturalLanguageTranslator startup postion move to after >> PasteUpMorph since it will show a progress bar. >> 8. Fix to Random>>nextInt: to allow large numbers which would be >> out of range if using Floats (as mentioned >> recently on dev, use of Floats is dodgy anyway...) >> 9. Changed TranscriptStream>>clear to use a new buffer (was just >> reset which could leave a massive >> collection). >> 10. Changed RemoteString to handle concurrent processes safely. >> This ones particularly interesting: we were >> load-testing our Seaside app here and getting lots of syntax >> errors when hitting the image with around the 20 >> concurrent processes due to source file access. After this change >> we were hitting it with approximately 500 >> concurrent processes, and the failure was in the Java load tester >> (it timed out). >> Issue 224: random cleans >> - removeColorSwatch.1.cs: remove class ColorSwatch >> Issue 221: cleanup: remove methods calling isThisEverCalled >> - remove some methods that where deprecated in 3.9 >> - remove all methods with calls to #isThisEverCalled >> Issue 222: methods from NewCompiler >> - some method from newcompiler/Reflectivity that are better >> directly in the base (accessors, mostly) >> Issue 199: remove MethodFinder >> - finding methods by name is done by "Method Names", too >> - it s >1000 lines of Code. >> - it has a list of all selectors of a very old Squeak version. >> Many methods are only referenced here, thus >> they can not be found using the tools to find unsent mesages. >> >> postscript: >> >> Smalltalk removeClassNamed: #CardPlayer59. >> Smalltalk removeClassNamed: #Player58. >> SystemOrganization removeEmptyCategories. >> -- >> Marcus Denker -- denker(a)iam.unibe.ch >> http://www.iam.unibe.ch/~denker >> >> >> _______________________________________________ >> 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 >

Oct. 8, 2008

Re: [Pharo-project] [updates] 10088

by Adrian Lienhard

@Marcus: thanks! @all: I've run the tests and currently we have 3 tests that are not green. I've filed issues for two. The third one is due to a DNU in BookMorph (actually "BookMorph new" does not work anymore). What is the status of BookMorph? Is this a candidate to be removed or should we fix it? Adrian On Oct 8, 2008, at 10:15 , Marcus Denker wrote: > Issue 218: Enhancements collected by gary and simon > 1. Fixed flaky borwser comment text area sometime not showing. > 2. Added getArgumentPermutation to support RefactoringEngine. > 3. Fixes to CanvasCharacterScanner and MultiCanvasCharacterScanner > to correctly align the first line of text > when centered/justifed etc. > 4. Added more constant names to Character class. > 5. Modified ConnectionQueue to not accept connections when queue is > full. > 6. Changed GrafPort to answer a MultiDisplayScanner when > appropriate (allows subclasses of > MultiNewParagraph). > 7. NaturalLanguageTranslator startup postion move to after > PasteUpMorph since it will show a progress bar. > 8. Fix to Random>>nextInt: to allow large numbers which would be > out of range if using Floats (as mentioned > recently on dev, use of Floats is dodgy anyway...) > 9. Changed TranscriptStream>>clear to use a new buffer (was just > reset which could leave a massive > collection). > 10. Changed RemoteString to handle concurrent processes safely. > This ones particularly interesting: we were > load-testing our Seaside app here and getting lots of syntax errors > when hitting the image with around the 20 > concurrent processes due to source file access. After this change > we were hitting it with approximately 500 > concurrent processes, and the failure was in the Java load tester > (it timed out). > Issue 224: random cleans > - removeColorSwatch.1.cs: remove class ColorSwatch > Issue 221: cleanup: remove methods calling isThisEverCalled > - remove some methods that where deprecated in 3.9 > - remove all methods with calls to #isThisEverCalled > Issue 222: methods from NewCompiler > - some method from newcompiler/Reflectivity that are better > directly in the base (accessors, mostly) > Issue 199: remove MethodFinder > - finding methods by name is done by "Method Names", too > - it s >1000 lines of Code. > - it has a list of all selectors of a very old Squeak version. Many > methods are only referenced here, thus > they can not be found using the tools to find unsent mesages. > > postscript: > > Smalltalk removeClassNamed: #CardPlayer59. > Smalltalk removeClassNamed: #Player58. > SystemOrganization removeEmptyCategories. > -- > Marcus Denker -- denker(a)iam.unibe.ch > http://www.iam.unibe.ch/~denker > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 8, 2008

[Pharo-project] [updates] 10088

by Marcus Denker

Issue 218: Enhancements collected by gary and simon 1. Fixed flaky borwser comment text area sometime not showing. 2. Added getArgumentPermutation to support RefactoringEngine. 3. Fixes to CanvasCharacterScanner and MultiCanvasCharacterScanner to correctly align the first line of text when centered/justifed etc. 4. Added more constant names to Character class. 5. Modified ConnectionQueue to not accept connections when queue is full. 6. Changed GrafPort to answer a MultiDisplayScanner when appropriate (allows subclasses of MultiNewParagraph). 7. NaturalLanguageTranslator startup postion move to after PasteUpMorph since it will show a progress bar. 8. Fix to Random>>nextInt: to allow large numbers which would be out of range if using Floats (as mentioned recently on dev, use of Floats is dodgy anyway...) 9. Changed TranscriptStream>>clear to use a new buffer (was just reset which could leave a massive collection). 10. Changed RemoteString to handle concurrent processes safely. This ones particularly interesting: we were load-testing our Seaside app here and getting lots of syntax errors when hitting the image with around the 20 concurrent processes due to source file access. After this change we were hitting it with approximately 500 concurrent processes, and the failure was in the Java load tester (it timed out). Issue 224: random cleans - removeColorSwatch.1.cs: remove class ColorSwatch Issue 221: cleanup: remove methods calling isThisEverCalled - remove some methods that where deprecated in 3.9 - remove all methods with calls to #isThisEverCalled Issue 222: methods from NewCompiler - some method from newcompiler/Reflectivity that are better directly in the base (accessors, mostly) Issue 199: remove MethodFinder - finding methods by name is done by "Method Names", too - it s >1000 lines of Code. - it has a list of all selectors of a very old Squeak version. Many methods are only referenced here, thus they can not be found using the tools to find unsent mesages. postscript: Smalltalk removeClassNamed: #CardPlayer59. Smalltalk removeClassNamed: #Player58. SystemOrganization removeEmptyCategories. -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Oct. 8, 2008