March 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] classNameCache/classNames problem

by StÃ©phane Ducasse

Yes we should remove it :) > > > ^ RealEstateAgent standardWindowExtent > > Better, but still problems. > > SystemWindows >> initialExtent > ^ (self model respondsTo: #initialExtent) > ifTrue: [self model initialExtent] > ifFalse: [RealEstateAgent standardWindowExtent] > > > the thing is that model is nil, and UndefinedObject responds to initialExtent (as it is in Object)..altough it is deprecated. > > Maybe this is a good opportunity to add a respondsAndNotDeprecatedTo: or just change respondsTo: to returns false if it it deprecated. > I am not sure if this is a good idea. > > Another hack may be to implement initialContext in UndefinedObject, but I am not sure if I like it neither. > > Finally, we may implement such method in this way: > > initialExtent > ^ ( self model isNil not and: [ self model respondsTo: #initialExtent ] ) > ifTrue: [self model initialExtent] > ifFalse: [RealEstateAgent standardWindowExtent] > > > What do you think ? > > Cheers > > Mariano > > > > > On Mar 18, 2010, at 4:04 PM, Mariano Martinez Peck wrote: > > > > > > > On Wed, Mar 17, 2010 at 9:31 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > Thanks pavel > > the Smalltalk -> SmalltalkImage current is not finished so any fix is welcomed. > > I have some admin work today and will try to find soem times to fix that. > > > > > I tried to run tests in Pharo 1.1 #11275 and then I got an error when > > > trying to open Message Names. The reason is that if you evaluate > > > > > > Smalltalk classNames includes: #C1 > > > > > > you got true so Smalltalk classNames includes it however it is not > > > present in Smalltalk globals. After Smalltalk flushClassNameCache the > > > problem disapeared. > > > > > > If I tried to create a class named SomeClass, the result was: > > > > > > Smalltalk classNames includes: #SomeClass -> false > > > Smalltalk globals at: #SomeClass -> SomeClass > > > > > > I had to remove Object>>#initialExtent because of neverending > > > deperecation warning (a methods tries respondsTo: #initialExtent on a > > > model. > > > > Oh yesssss. ARGH. My mistake. Indeed some models should not implement intialExtent > > and it falls back on Object.... stupid me. > > but this is strange because I run all the tests and besides > > > > > > Stef: I am trying to run the tests on 11277 and it is impossible because of the amount of warnings about that deprecation in Object >> initialContext. > > > > I would commit a slice but I am not sure what should be done. > > > > Thanks > > > > Mariano > > > > > > > > > > > I don't know which one because Recent Submissions doesn't work > > > because of method reference > > > AutoGeneratedClassForTestingSystemChanges>>#Comment anwered nil on > > > actualClass message) > > > > > > -- Pavel > > > > > > _______________________________________________ > > > 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 > > > _______________________________________________ > 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

March 18, 2010

Re: [Pharo-project] Remove Pen and PenPointRecorder ??

by Mariano Martinez Peck

nuuuuuu hahahahhaha Incredible!!! ok guys...sorry for being the bad guy haha 2010/3/18 Fernando olivero <oliverof(a)lu.unisi.ch> > > On Mar 18, 2010, at 5:53 PM, Mariano Martinez Peck wrote: > > > > On Wed, Mar 17, 2010 at 6:43 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> + 1! >> Even with a bit of nostalgia :) >> > > Nostalgia ??? what's that ? ;) It is not nostalgia as it was the first > time I saw them :) > > In the way to remove them, some friends of Form go away also. > In Inbox: > > Name: SLICE-2163-RemovePenAndPenPointRecorder-MarianoMartinezPeck.2 > Author: MarianoMartinezPeck > Time: 18 March 2010, 5:50:39 pm > UUID: 358400a8-d2c1-4688-8df2-4054d93f5e44 > Ancestors: SLICE-2163-RemovePenAndPenPointRecorder-MarianoMartinezPeck.1 > Dependencies: Graphics-MarianoMartinezPeck.220, > Kernel-MarianoMartinezPeck.622, Morphic-MarianoMartinezPeck.551, > System-MarianoMartinezPeck.16, System-Support-MarianoMartinezPeck.265 > > Fix to issue 2163. Remove Pen and PenPointRecorder. > In the way to remove them, some friends of Form go away also. > > > > > > > >> But this is the way to go. >> Propose a change/slice + a ticket and we get it in. >> >> Stef >> >> On Mar 17, 2010, at 2:33 PM, Mariano Martinez Peck wrote: >> >> > Hi folks, what do you think about removing Pen and PenPointRecorder ? >> > At least, to remove it from the core and let them somewhere in a >> repository. >> > >> > Cheers >> > >> > Mariano >> > _______________________________________________ >> > 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 >> > > <ATT00001..txt> > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 18, 2010

Re: [Pharo-project] Remove Pen and PenPointRecorder ??

by Fernando olivero

On Mar 18, 2010, at 5:53 PM, Mariano Martinez Peck wrote: > > > On Wed, Mar 17, 2010 at 6:43 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > + 1! > Even with a bit of nostalgia :) > > Nostalgia ??? what's that ? ;) It is not nostalgia as it was the first time I saw them :) > > In the way to remove them, some friends of Form go away also. > In Inbox: > > Name: SLICE-2163-RemovePenAndPenPointRecorder-MarianoMartinezPeck.2 > Author: MarianoMartinezPeck > Time: 18 March 2010, 5:50:39 pm > UUID: 358400a8-d2c1-4688-8df2-4054d93f5e44 > Ancestors: SLICE-2163-RemovePenAndPenPointRecorder-MarianoMartinezPeck.1 > Dependencies: Graphics-MarianoMartinezPeck.220, Kernel-MarianoMartinezPeck.622, Morphic-MarianoMartinezPeck.551, System-MarianoMartinezPeck.16, System-Support-MarianoMartinezPeck.265 > > Fix to issue 2163. Remove Pen and PenPointRecorder. > In the way to remove them, some friends of Form go away also. > > > > > > > But this is the way to go. > Propose a change/slice + a ticket and we get it in. > > Stef > > On Mar 17, 2010, at 2:33 PM, Mariano Martinez Peck wrote: > > > Hi folks, what do you think about removing Pen and PenPointRecorder ? > > At least, to remove it from the core and let them somewhere in a repository. > > > > Cheers > > > > Mariano > > _______________________________________________ > > 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 > > <ATT00001..txt>

March 18, 2010

Re: [Pharo-project] [ANN] Gofer Project Loader 1.0 (BETA)

by Dale Henrichs

March 18, 2010

Re: [Pharo-project] classNameCache/classNames problem

by Mariano Martinez Peck

On Thu, Mar 18, 2010 at 4:10 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > yes I know I was waiting that marcus integrates the fix I proposed for > image > Since it contains also some fix for initialExtent. > I will do it. and integrate another fix for initialExtent > > try > > Model>>initialExtent > > ^ RealEstateAgent standardWindowExtent > Better, but still problems. SystemWindows >> initialExtent ^ (self model respondsTo: #initialExtent) ifTrue: [self model initialExtent] ifFalse: [RealEstateAgent standardWindowExtent] the thing is that model is nil, and UndefinedObject responds to initialExtent (as it is in Object)..altough it is deprecated. Maybe this is a good opportunity to add a respondsAndNotDeprecatedTo: or just change respondsTo: to returns false if it it deprecated. I am not sure if this is a good idea. Another hack may be to implement initialContext in UndefinedObject, but I am not sure if I like it neither. Finally, we may implement such method in this way: initialExtent ^ ( self model isNil not and: [ self model respondsTo: #initialExtent ] ) ifTrue: [self model initialExtent] ifFalse: [RealEstateAgent standardWindowExtent] What do you think ? Cheers Mariano > > On Mar 18, 2010, at 4:04 PM, Mariano Martinez Peck wrote: > > > > > > > On Wed, Mar 17, 2010 at 9:31 AM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > > Thanks pavel > > the Smalltalk -> SmalltalkImage current is not finished so any fix is > welcomed. > > I have some admin work today and will try to find soem times to fix that. > > > > > I tried to run tests in Pharo 1.1 #11275 and then I got an error when > > > trying to open Message Names. The reason is that if you evaluate > > > > > > Smalltalk classNames includes: #C1 > > > > > > you got true so Smalltalk classNames includes it however it is not > > > present in Smalltalk globals. After Smalltalk flushClassNameCache the > > > problem disapeared. > > > > > > If I tried to create a class named SomeClass, the result was: > > > > > > Smalltalk classNames includes: #SomeClass -> false > > > Smalltalk globals at: #SomeClass -> SomeClass > > > > > > I had to remove Object>>#initialExtent because of neverending > > > deperecation warning (a methods tries respondsTo: #initialExtent on a > > > model. > > > > Oh yesssss. ARGH. My mistake. Indeed some models should not implement > intialExtent > > and it falls back on Object.... stupid me. > > but this is strange because I run all the tests and besides > > > > > > Stef: I am trying to run the tests on 11277 and it is impossible because > of the amount of warnings about that deprecation in Object >> > initialContext. > > > > I would commit a slice but I am not sure what should be done. > > > > Thanks > > > > Mariano > > > > > > > > > > > I don't know which one because Recent Submissions doesn't work > > > because of method reference > > > AutoGeneratedClassForTestingSystemChanges>>#Comment anwered nil on > > > actualClass message) > > > > > > -- Pavel > > > > > > _______________________________________________ > > > 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 18, 2010

Re: [Pharo-project] Remove Pen and PenPointRecorder ??

by Mariano Martinez Peck

On Wed, Mar 17, 2010 at 6:43 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > + 1! > Even with a bit of nostalgia :) > Nostalgia ??? what's that ? ;) It is not nostalgia as it was the first time I saw them :) In the way to remove them, some friends of Form go away also. In Inbox: Name: SLICE-2163-RemovePenAndPenPointRecorder-MarianoMartinezPeck.2 Author: MarianoMartinezPeck Time: 18 March 2010, 5:50:39 pm UUID: 358400a8-d2c1-4688-8df2-4054d93f5e44 Ancestors: SLICE-2163-RemovePenAndPenPointRecorder-MarianoMartinezPeck.1 Dependencies: Graphics-MarianoMartinezPeck.220, Kernel-MarianoMartinezPeck.622, Morphic-MarianoMartinezPeck.551, System-MarianoMartinezPeck.16, System-Support-MarianoMartinezPeck.265 Fix to issue 2163. Remove Pen and PenPointRecorder. In the way to remove them, some friends of Form go away also. > But this is the way to go. > Propose a change/slice + a ticket and we get it in. > > Stef > > On Mar 17, 2010, at 2:33 PM, Mariano Martinez Peck wrote: > > > Hi folks, what do you think about removing Pen and PenPointRecorder ? > > At least, to remove it from the core and let them somewhere in a > repository. > > > > Cheers > > > > Mariano > > _______________________________________________ > > 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 >

March 18, 2010

Re: [Pharo-project] Smalltalk isMacOS ifTrue: [ Smalltalk osVersion asNumber >= 1000

by John M McIntosh

On 2010-03-18, at 12:35 AM, StÃ©phane Ducasse wrote: > Thanks. > I will publish what I did and we can iterate from here. > > I have > isUnix > isRiscOS > isMacOS > isWin32 > isWin32CE > > And I imagine that I will need > isMacOS9 > isMacOSX isMac isiPhone "Answer true if running on iPhone" ^ (self platformName = 'iPhone') So one of two things can happen here (1) that you retain the isMacOS9 and isMacOSX to retain the existing usage where we have an OS9 codebase and a OS-X subclassed codebase. (2) Or you drop OS9 completely and folded the OSX & OS9 into a single class. Personally I think folding the classes together is a better choice since a closure based image won't run on OS9. >> What is the significance of version 1030? > > Yes this was my question? In that case the behavior of the operating system was different between 10.0 and 10.3 versus 10.3 onwards. So to make the tests past on 10.2 it had to be different from what happens when you run 10.4 -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

March 18, 2010

[Pharo-project] stupid question with "method source with it"

by Mariano Martinez Peck

Hi. I want to search something trough right button -> extended search -> "method source with it" I want to search with case sensitive. The help says "use shift for case-sensitive". However, I don't understand what that means. The shift is the shift key ? in true, in which moment do I have to press the shift key ? Thanks Mariano

March 18, 2010

Re: [Pharo-project] Rename DummySuperclassOfColorPickerMorph

by StÃ©phane Ducasse

We should remove this class. It is plain bad. For that we should replace colorPickerMorph with ColorChooser. Stef On Mar 18, 2010, at 4:11 PM, Mariano Martinez Peck wrote: > But I don't have a better name for that. Any ideas? It has a subclass ColorPickerMorph > > Cheers > > mariano > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 18, 2010

[Pharo-project] Rename DummySuperclassOfColorPickerMorph

by Mariano Martinez Peck

But I don't have a better name for that. Any ideas? It has a subclass ColorPickerMorph Cheers mariano

March 18, 2010