- Pharo-dev - lists.pharo.org

[Pharo-project] recategorizing all the categories...
by StÃ©phane Ducasse March 19, 2010

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

[Pharo-project] unused temporal variables
by Mariano Martinez Peck March 19, 2010

March 19, 2010

Hi. I remember in previous Pharo images when you save a method that has unused temporal variables you have a popup that said "XXX is unused, don't you want to remove it ?" or something similar.... We then removed that. Ok, cool. Now...suppose I want to examine all the system to detect all those unused temporal variables and remove them (yes, recompiling), does someone have an idea how to do that ? Thanks! Mariano

2 1

[Pharo-project] CleanUp unused packages
by Mariano Martinez Peck March 19, 2010

March 19, 2010

http://code.google.com/p/pharo/issues/detail?id=2165 There are some packages that has to be removed. For example: - PinesoftEnhancementsForFreeType: This package is empty - FixUnderscores: This package is old, is not needed any more and has no references The fix is to evaluate: (MCPackage named: 'PinesoftEnhancementsForFreeType') unload. (MCPackage named: 'FixUnderscores') unload. Cheers Mariano

4 6

[Pharo-project] (aDateAndTime offset: '0:12:00:00') = '1901-01-01T00:00:00+12:00'
by stephane ducasse March 19, 2010

March 19, 2010

in Squeak (aDateAndTime offset: '0:12:00:00') = '1901-01-01T00:00:00+12:00' true in pharo (aDateAndTime offset: '0:12:00:00') = '1901-01-01T00:00:00+12:00'. false. Apparently the false in pharo comes from a bug in readFrom: in DateAndTime Now the question is does it make sense to have a DateAndTime = to its string representation. For me I would prefer not (aDateAndTime offset: '0:12:00:00') = '1901-01-01T00:00:00+12:00' -> false (aDateAndTime offset: '0:12:00:00') printString = '1901-01-01T00:00:00+12:00' -> true DateAndTime>>= comparand "comparand conforms to protocol DateAndTime, or can be converted into something that conforms." | comparandAsDateAndTime | self == comparand ifTrue: [^ true]. comparandAsDateAndTime := [comparand asDateAndTime] on: MessageNotUnderstood do: [^ false]. ^ self offset = comparandAsDateAndTime offset ifTrue: [self hasEqualTicks: comparandAsDateAndTime ] ifFalse: [self asUTC ticks = comparandAsDateAndTime asUTC ticks] What do you think Stef

5 5

[Pharo-project] A challenge for us
by StÃ©phane Ducasse March 19, 2010

March 19, 2010

Hi I would like to initiative a task (monthly) for us. I would like to get really good tests coverage for some of the core classes. For example Date, Time, Duration, DateAndTime. This is really important in the long term to get sure that we identify bugs as soon as they appear. It would be really good if we could get team up and fix that together. Does anybody want to help? I started to fix some bugs there and write more tests in the process of fixing tests. Stef

9 13

[Pharo-project] MethodProperties question
by Mariano Martinez Peck March 19, 2010

March 19, 2010

Hi folks (Marcus ?). I saw this class was removed, however: 1) The class MethodPropertiesTest is still alive. Shouldn't we remove it ? 2) After evaluating "ScriptLoader new cleanUpForRelease" if I inspect SystemNavigation default obsoleteClasses I have a "AnObsoleteMethodProperties" Cheers Mariano

2 2

March 18, 2010

What do you think about that? I think that would be good. Issue 2159: We should clean all the platformName = 'Win32' and: [osVersion = 'CE'] This is not good to have all these strings to encode platform support. We should move some code to SmalltalkImage SmalltalkImage>>win32 ^ 'Win 32' SmalltalkImage>>isWin32CE ^ (self platformName = 'Win32' and: [self osVersion = 'CE']) ... Stef

4 8

[Pharo-project] [update 1.1] #11278
by Marcus Denker March 18, 2010

March 18, 2010

11278 ----- Issue 2136: Smalltalk and SmalltalkImage (CleaningSystemDictionary.3.cs) -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

3 7

[Pharo-project] Scratch.app 1.3 hits the App Store, tossing free (USA) trial codes.
by John M McIntosh March 18, 2010

March 18, 2010

In as many weeks I've managed to send 3 releases of Scratch to the App store, so it's becoming more mature. Now a small secret, if you have in the past gotten and ran iSqueak.app from me on your iphone or ipod touch then you can ALSO run a beta version of Scratch.app. You just need to email me (not the list) for a link to the magic provisioning file. Secondly, I've a bunch of 30 day trial codes to hand out, good for the USA store only. If you would like a code, again please email me (not the list). -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

1 0