- Pharo-dev - lists.pharo.org

[Pharo-project] About gofer in pier vs seaside?
by stephane ducasse March 19, 2010

March 19, 2010

Lukas I'm confused but it seems that the gofer in pier1.2 does not understand the same protocol than the one in latest seaside. Is there a way to fix that ? Stef

2 1

[Pharo-project] for 1.0 did we put the welcome message
by StÃ©phane Ducasse March 19, 2010

March 19, 2010

with the summary of all the actions? Stef

4 5

[Pharo-project] a summer task....
by John M McIntosh March 19, 2010

March 19, 2010

FileDirectory>>matchingEntries: criteria "Ignore the filter criteria for now" ^self entries Michael R 2001... MMm really want to say matchingEntries: '*.png' Surely someone would like to add a bit more behaviour to the method? -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

2 1

[Pharo-project] RequiresTestCase >> testExlcusionInTraits is failing
by Mariano Martinez Peck March 19, 2010

March 19, 2010

can we (Adrian ?) fix this so that have everything green ? Running all tests together, the first time, it fails. If it run it again, it works :( Cheers Mariano

1 0

[Pharo-project] Deprecation TheWorldMenu in Pharo 1.1
by Lukas Renggli March 19, 2010

March 19, 2010

What is the point of leaving the empty class TheWorldMenu in Pharo 1.1? Obviously it is deprecated, but then all its methods are removed. I run across code like the following one in numerous packages: Smalltalk at: #TheWorldMenu ifPresent: [:theWorldMenu | theWorldMenu registerOpenCommand: { 'RFB/VNC Server' . { RFBServerGUI . #open } . 'Configure access to this desktop from remote VNC viewers.' }] Of course this now fails, because the class is there but none of its code? Would it be possible to either entirely remove the class or add deprecated methods (they don't even need to do anything)? Lukas -- Lukas Renggli http://www.lukas-renggli.ch

3 4

[Pharo-project] String widgets for GUIs built using ToolBuilder
by Ralph Boland March 19, 2010

March 19, 2010

I originally posted this on Squeak-Dev but I didn't get a response so I am hoping someone on this list can help. I will release the code I am working on to SqueakSource. I assume it will work in Pharo as well. If it doesn't let me know and I will clean up the problems. ================================= I am trying to subclass TestBuilder (SUnitGUI) for my own testing facility. TestBuilder builds a GUI using ToolBuilder and I am trying to build my GUI using ToolBuilder as well. I need to use an input field and want to add a StringMorph like widget to label the input field. The only way I can see to do this using ToolBuilder is to use another input field for my input field label string. There has to be a better, standard, way of doing this. Can someone tell me what the standard way, or some reasonable way, of labeling my input field is when using ToolBuilder? Regards, Ralph Boland -- Had a wife and kids in Florida, Jack (Nicklaus) Went out for a "ride" but I couldn't get back As a ten timer being hunted down OR When the wife found out who I was knowing (biblically speaking) I hit a hydrant and I just kept going (till I hit a tree). ...

2 1

[Pharo-project] Sets with nils using SetElement(s)
by Igor Stasenko March 19, 2010

March 19, 2010

i added a changesets into a corresponding tracker issue (#1907) please, be advised, that in Squeak it was adopted after HashedCollection refactoring. And a scope of changes is wider than my own (it includes KeyedSet and KeyedIdentitySet, which i haven't touched before). Still, all tests are green, except there is unimplemented #errorNoFreeSpace , which can be found in trunk's HashedCollection ). -- Best regards, Igor Stasenko AKA sig.

2 1

[Pharo-project] ESUG selected as GSoC 2010 mentoring organization!!!!
by Mariano Martinez Peck March 19, 2010

March 19, 2010

We are incredibly proud to announce that ESUG was selected for the GSoC 2010. We have a long list of wonderful projects, mentors and a cool website. We want to thank you to all the people who help us publishing project ideas, giving feedback on the submit text or the English, etc. For the moment, we don't know the slots (amount of projects) that we will receive. Don't worry. We will contact you again very soon to let you know the following steps. Now, prepare yourself. We have to show the rest of the world why we love Smalltalk so much :) Thank you very much. The very happy GSoC admin team

4 4

March 19, 2010

hi guys I wanted to know if one you try tried to automatically recategorized all the methods of the system. Because I'm tired to get this as yet unclassified in my face. I looks to my like dirt in the street. Wanna get clean... Stef

7 12

[Pharo-project] RefactoringManager and RBNamepsace error?
by Fernando olivero March 19, 2010

March 19, 2010

Lukas, i have the following problem: model := RBNamespace new. Then executing successive RenameRefactoring's using the same model yields an Error. 1. ClassA -> ClassA2 OK 2. ClassA2 -> ClassA3 OK 3. ClassA3 -> ClassA4 ERROR! I've tracked it down to this: 1. RenameRefactoring>>execute self primitiveExecute. RefactoringManager instance addRefactoring: self 2. RefactoringManager>>addRefactoring: aRefactoring RefactoryChangeManager instance performChange: aRefactoring changes. refactorings add: aRefactoring class name 3. Refactoring>>changes ^self model changes which answers all the changes! { ClassA rename: #ClassA2! ClassA2 rename: #ClassA3! ClassA3 rename: #ClassA4! } Why does a particular refactoring answers all the models changes? And not just the ones it introduced? The problem is in #performChange: will apply over and over all the changes, and not just the last one. Lukas, do you think i'm incorrectly using the namespace and refactoring's? Are namespace supposed to be used once and later ditched? My goal is to have a GauchoSystem which nows all the changes (with undos!) that have happened, that's why i'm using always the same namespace. Thanks, Fernando pd: a test that reproduces the problem. >>testSucessiveRefactoringsError | namespace | namespace := RBNamespace new. [ | refactoring| Object subclass: 'ClassA' asSymbol instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'TestingNamespaces1234'. refactoring := RenameClassRefactoring model: namespace rename: (Smalltalk classNamed: 'ClassA' asSymbol ) to: 'ClassA2' asSymbol . refactoring execute. refactoring := RenameClassRefactoring model: namespace rename: (Smalltalk classNamed:'ClassA2' asSymbol ) to: 'ClassA3' asSymbol. refactoring execute. refactoring := RenameClassRefactoring model: namespace rename: (Smalltalk classNamed: 'ClassA3' asSymbol ) to: 'ClassA4' asSymbol. self shouldnt:[refactoring execute] raise: Error description: 'Valid refactoring should not raise error'. ] ensure:[ SystemOrganization removeSystemCategory: 'TestingNamespaces1234' ]

2 3