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

Re: [Pharo-project] Who is working on which tests? Why are there new, broken tests?

by StÃ©phane Ducasse

aha. may be squeakdev is based on another image or there is package that when loading remove hex. Stef On Jun 10, 2008, at 9:35 PM, Oscar Nierstrasz wrote: > > Wow. > > I took pharo0.1-10032-7075dev08.06.1 and updated it. There is no > Integer>>hex there. > > Damien, can you help? It looks like the pharo-dev image is somehow > out of sync. > > I will try both again now. > > - on > > On Jun 10, 2008, at 9:21 PM, StÃ©phane Ducasse wrote: > >> Hi oscar >> >> I took the pharo image Pharo0.1-10028-2008-05-24 available on the >> pharo web site >> and did an update. >> >> and there is >> Integer>>hex >> ^ self printStringBase: 16 >> >> I checked the version and it is from 25 of may >> >> Stef >> >>> >>> Hi Stef, >>> >>> I loaded a fresh pharo-dev image and updated everything. Then the >>> testHex tests failed, so I fixed them. >>> >>> Can you please tell me which implementors of hex you find in your >>> image? >>> >>> I only find Character>>hex and Float>>hex. I had to implement >>> Integer>>hex myself. >>> >>> - on >>> >>> On Jun 10, 2008, at 6:38 PM, StÃ©phane Ducasse wrote: >>> >>>> testHex >>>> self assert: $a hex '61' = '61'. >>>> self assert: Character space hex = '20' >>>> >>>> is green on my image >>>> >>>> as well as this one >>>> >>>> testHex >>>> self assert: 0 hex = '0'. >>>> self assert: 12 hex = 'C'. >>>> self assert: 1234 hex = '4D2'. >>>> >>>> They are red in yours? >>>> >>>> Stef >>>> >>>> >>>> On Jun 10, 2008, at 4:00 PM, Oscar Nierstrasz wrote: >>>> >>>>> >>>>> Well, I thought we would start to fix the existing broken tests >>>>> before adding new broken tests. >>>>> >>>>> I would also be very happy to see some comments when someone >>>>> adds a new broken test, so I know what the plan is. >>>>> >>>>> Now I added an implementation of Integer>>hex, for example, but >>>>> I am not so sure why we need this. >>>>> Ain't too many senders. An easier fix would have been to remove >>>>> the broken test. >>>>> >>>>> Cheers, >>>>> - on >>>>> >>>>> On Jun 10, 2008, at 15:53, Bill Schwab wrote: >>>>> >>>>>> Is your concern that the new tests are broken (which seems >>>>>> normal to me >>>>>> that they would start out that way), or are you objecting to >>>>>> their being >>>>>> included in the image? >>>>>> >>>>>> I can see arguments either way on the latter. If code in the >>>>>> image is >>>>>> wrong and a clearly correct but currently failing test >>>>>> highlights it, >>>>>> I'd rather be alerted to it. You are also correct that having >>>>>> them >>>>>> included draws attention that could easily encourage >>>>>> duplication of >>>>>> effort. >>>>>> >>>>>> Comments? >>>>>> >>>>>> 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) 846-1285 >>>>>> FAX: (352) 392-7029 >>>>>> >>>>>>>>> oscar(a)iam.unibe.ch 06/10/08 8:31 AM >>> >>>>>> >>>>>> I looked at the wiki page >>>>>> http://code.google.com/p/pharo/wiki/CurrentlyWorkingOn >>>>>> but it does not say much. >>>>>> >>>>>> I would like to work through some tests, but I cannot find an >>>>>> overview. >>>>>> >>>>>> The tests CharacterTest>>testHex and IntegerTest>>testHex are >>>>>> broken >>>>>> but seem to be very new. Stef, are you working on these? You >>>>>> seem to >>>>>> have written the tests ... >>>>>> >>>>>> - on >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>> >> >> >> _______________________________________________ >> 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 >

June 10, 2008

Re: [Pharo-project] self halt in RxParserTest>>testMatchesInwW

by StÃ©phane Ducasse

Ok I will publish a new version of the package on squeaksource stef On Jun 10, 2008, at 9:04 PM, Oscar Nierstrasz wrote: > > You har the image-meister, so you should patch it, I think. I can > only add a patch into the PharoInbox, but this is so trivial it is > easier if you just update your master image. > > - on > > On Jun 10, 2008, at 6:33 PM, StÃ©phane Ducasse wrote: > >> Yes go ahead. >> >> Stef >> >> On Jun 10, 2008, at 2:06 PM, Oscar Nierstrasz wrote: >> >>> >>> Stef, >>> >>> RxParserTest>>testMatchesInwW >>> >>> has a self halt in it dating from 2006, apparently added by you. >>> >>> I guess you should remove it ... The test runs fine otherwise. >>> >>> - on >>> >>> >>> _______________________________________________ >>> 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 >

June 10, 2008

Re: [Pharo-project] KernelTests green

by StÃ©phane Ducasse

Excellent! may be this is the hash of class that changed. Marcus retrochanged the hash behavior that we harvested in 3.9. And may be in 3.10 they changed class hash too. Now I do not know if in 3.9 these tests were broken. Stef On Jun 10, 2008, at 9:32 PM, Oscar Nierstrasz wrote: > > OK, I investigated more deeply. > > It appears that SequenceableCollection>>hash behaves differently in > Pharo and Squeak 3.10. > > Squeak: > > #(1) hash --> 22516953 > > Pharo: > > #(1) hash --> 61541560 > > Since DateAndTime>>hash is ultimately implemented in terms of > Array>>hash (inherited from SequenceableCollection), this test fails. > > Not yet sure why these two behave differently ... > > Already the first line (self species hash) is different: > > Squeak: > > Array hash --> 259007228 > > Pharo: > > Array hash --> 2455 > > - on > > On Jun 10, 2008, at 6:34 PM, StÃ©phane Ducasse wrote: > >> We checked with lukas what is strange is that the same tests are >> green in 3.10. >> >> Stef >> >> On Jun 10, 2008, at 3:48 PM, Oscar Nierstrasz wrote: >> >>> >>> I have posted some patches to the inbox to make the Kernel Number >>> tests run, and in the Issues page I propose to delete a bunch of >>> nonsensical testHash tests. With these changes the Kernel tests >>> should all be green. >>> >>> - on >>> >>> _______________________________________________ >>> 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 >

June 10, 2008

Re: [Pharo-project] Who is working on which tests? Why are there new, broken tests?

by Oscar Nierstrasz

Wow. I took pharo0.1-10032-7075dev08.06.1 and updated it. There is no Integer>>hex there. Damien, can you help? It looks like the pharo-dev image is somehow out of sync. I will try both again now. - on On Jun 10, 2008, at 9:21 PM, StÃ©phane Ducasse wrote: > Hi oscar > > I took the pharo image Pharo0.1-10028-2008-05-24 available on the > pharo web site > and did an update. > > and there is > Integer>>hex > ^ self printStringBase: 16 > > I checked the version and it is from 25 of may > > Stef > >> >> Hi Stef, >> >> I loaded a fresh pharo-dev image and updated everything. Then the >> testHex tests failed, so I fixed them. >> >> Can you please tell me which implementors of hex you find in your >> image? >> >> I only find Character>>hex and Float>>hex. I had to implement >> Integer>>hex myself. >> >> - on >> >> On Jun 10, 2008, at 6:38 PM, StÃ©phane Ducasse wrote: >> >>> testHex >>> self assert: $a hex '61' = '61'. >>> self assert: Character space hex = '20' >>> >>> is green on my image >>> >>> as well as this one >>> >>> testHex >>> self assert: 0 hex = '0'. >>> self assert: 12 hex = 'C'. >>> self assert: 1234 hex = '4D2'. >>> >>> They are red in yours? >>> >>> Stef >>> >>> >>> On Jun 10, 2008, at 4:00 PM, Oscar Nierstrasz wrote: >>> >>>> >>>> Well, I thought we would start to fix the existing broken tests >>>> before adding new broken tests. >>>> >>>> I would also be very happy to see some comments when someone adds >>>> a new broken test, so I know what the plan is. >>>> >>>> Now I added an implementation of Integer>>hex, for example, but I >>>> am not so sure why we need this. >>>> Ain't too many senders. An easier fix would have been to remove >>>> the broken test. >>>> >>>> Cheers, >>>> - on >>>> >>>> On Jun 10, 2008, at 15:53, Bill Schwab wrote: >>>> >>>>> Is your concern that the new tests are broken (which seems >>>>> normal to me >>>>> that they would start out that way), or are you objecting to >>>>> their being >>>>> included in the image? >>>>> >>>>> I can see arguments either way on the latter. If code in the >>>>> image is >>>>> wrong and a clearly correct but currently failing test >>>>> highlights it, >>>>> I'd rather be alerted to it. You are also correct that having >>>>> them >>>>> included draws attention that could easily encourage duplication >>>>> of >>>>> effort. >>>>> >>>>> Comments? >>>>> >>>>> 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) 846-1285 >>>>> FAX: (352) 392-7029 >>>>> >>>>>>>> oscar(a)iam.unibe.ch 06/10/08 8:31 AM >>> >>>>> >>>>> I looked at the wiki page >>>>> http://code.google.com/p/pharo/wiki/CurrentlyWorkingOn >>>>> but it does not say much. >>>>> >>>>> I would like to work through some tests, but I cannot find an >>>>> overview. >>>>> >>>>> The tests CharacterTest>>testHex and IntegerTest>>testHex are >>>>> broken >>>>> but seem to be very new. Stef, are you working on these? You >>>>> seem to >>>>> have written the tests ... >>>>> >>>>> - on >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 10, 2008

Re: [Pharo-project] KernelTests green

by Oscar Nierstrasz

OK, I investigated more deeply. It appears that SequenceableCollection>>hash behaves differently in Pharo and Squeak 3.10. Squeak: #(1) hash --> 22516953 Pharo: #(1) hash --> 61541560 Since DateAndTime>>hash is ultimately implemented in terms of Array>>hash (inherited from SequenceableCollection), this test fails. Not yet sure why these two behave differently ... Already the first line (self species hash) is different: Squeak: Array hash --> 259007228 Pharo: Array hash --> 2455 - on On Jun 10, 2008, at 6:34 PM, StÃ©phane Ducasse wrote: > We checked with lukas what is strange is that the same tests are > green in 3.10. > > Stef > > On Jun 10, 2008, at 3:48 PM, Oscar Nierstrasz wrote: > >> >> I have posted some patches to the inbox to make the Kernel Number >> tests run, and in the Issues page I propose to delete a bunch of >> nonsensical testHash tests. With these changes the Kernel tests >> should all be green. >> >> - on >> >> _______________________________________________ >> 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

June 10, 2008

Re: [Pharo-project] [ANN] test fixes + MVC cleaning step one

by StÃ©phane Ducasse

I missed some packages since my script only dealt with dirty packages. So I will continue to harvest the rest of the changes. Stef On Jun 10, 2008, at 9:13 PM, StÃ©phane Ducasse wrote: > Hi guys > > I harvested the MVC step one changes of Alain Plantec > Next the on: of damien. > > PS: I'm checking the hex problem by rebuilding my image from the > latest image available. > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 10, 2008

Re: [Pharo-project] Who is working on which tests? Why are there new, broken tests?

by StÃ©phane Ducasse

Hi oscar I took the pharo image Pharo0.1-10028-2008-05-24 available on the pharo web site and did an update. and there is Integer>>hex ^ self printStringBase: 16 I checked the version and it is from 25 of may Stef > > Hi Stef, > > I loaded a fresh pharo-dev image and updated everything. Then the > testHex tests failed, so I fixed them. > > Can you please tell me which implementors of hex you find in your > image? > > I only find Character>>hex and Float>>hex. I had to implement > Integer>>hex myself. > > - on > > On Jun 10, 2008, at 6:38 PM, StÃ©phane Ducasse wrote: > >> testHex >> self assert: $a hex '61' = '61'. >> self assert: Character space hex = '20' >> >> is green on my image >> >> as well as this one >> >> testHex >> self assert: 0 hex = '0'. >> self assert: 12 hex = 'C'. >> self assert: 1234 hex = '4D2'. >> >> They are red in yours? >> >> Stef >> >> >> On Jun 10, 2008, at 4:00 PM, Oscar Nierstrasz wrote: >> >>> >>> Well, I thought we would start to fix the existing broken tests >>> before adding new broken tests. >>> >>> I would also be very happy to see some comments when someone adds >>> a new broken test, so I know what the plan is. >>> >>> Now I added an implementation of Integer>>hex, for example, but I >>> am not so sure why we need this. >>> Ain't too many senders. An easier fix would have been to remove >>> the broken test. >>> >>> Cheers, >>> - on >>> >>> On Jun 10, 2008, at 15:53, Bill Schwab wrote: >>> >>>> Is your concern that the new tests are broken (which seems normal >>>> to me >>>> that they would start out that way), or are you objecting to >>>> their being >>>> included in the image? >>>> >>>> I can see arguments either way on the latter. If code in the >>>> image is >>>> wrong and a clearly correct but currently failing test highlights >>>> it, >>>> I'd rather be alerted to it. You are also correct that having them >>>> included draws attention that could easily encourage duplication of >>>> effort. >>>> >>>> Comments? >>>> >>>> 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) 846-1285 >>>> FAX: (352) 392-7029 >>>> >>>>>>> oscar(a)iam.unibe.ch 06/10/08 8:31 AM >>> >>>> >>>> I looked at the wiki page >>>> http://code.google.com/p/pharo/wiki/CurrentlyWorkingOn >>>> but it does not say much. >>>> >>>> I would like to work through some tests, but I cannot find an >>>> overview. >>>> >>>> The tests CharacterTest>>testHex and IntegerTest>>testHex are >>>> broken >>>> but seem to be very new. Stef, are you working on these? You >>>> seem to >>>> have written the tests ... >>>> >>>> - on >>>> >>>> >>>> _______________________________________________ >>>> 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 >

June 10, 2008

[Pharo-project] [ANN] test fixes + MVC cleaning step one

by StÃ©phane Ducasse

Hi guys I harvested the MVC step one changes of Alain Plantec Next the on: of damien. PS: I'm checking the hex problem by rebuilding my image from the latest image available. Stef

June 10, 2008

[Pharo-project] Integer>>hex

by Oscar Nierstrasz

I just checked the 3.10 image. There is no IntegerTest>>testHex, but there is an Integer>>hex which behaves differently from what you specified. I really don't understand what this is all about. I suggest to drop IntegerTest>>testHex for now. - on On Jun 10, 2008, at 9:03 PM, Oscar Nierstrasz wrote: > > Hi Stef, > > I loaded a fresh pharo-dev image and updated everything. Then the > testHex tests failed, so I fixed them. > > Can you please tell me which implementors of hex you find in your > image? > > I only find Character>>hex and Float>>hex. I had to implement > Integer>>hex myself. > > - on > > On Jun 10, 2008, at 6:38 PM, StÃ©phane Ducasse wrote: > >> testHex >> self assert: $a hex '61' = '61'. >> self assert: Character space hex = '20' >> >> is green on my image >> >> as well as this one >> >> testHex >> self assert: 0 hex = '0'. >> self assert: 12 hex = 'C'. >> self assert: 1234 hex = '4D2'. >> >> They are red in yours? >> >> Stef >> >> >> On Jun 10, 2008, at 4:00 PM, Oscar Nierstrasz wrote: >> >>> >>> Well, I thought we would start to fix the existing broken tests >>> before adding new broken tests. >>> >>> I would also be very happy to see some comments when someone adds >>> a new broken test, so I know what the plan is. >>> >>> Now I added an implementation of Integer>>hex, for example, but I >>> am not so sure why we need this. >>> Ain't too many senders. An easier fix would have been to remove >>> the broken test. >>> >>> Cheers, >>> - on >>> >>> On Jun 10, 2008, at 15:53, Bill Schwab wrote: >>> >>>> Is your concern that the new tests are broken (which seems normal >>>> to me >>>> that they would start out that way), or are you objecting to >>>> their being >>>> included in the image? >>>> >>>> I can see arguments either way on the latter. If code in the >>>> image is >>>> wrong and a clearly correct but currently failing test highlights >>>> it, >>>> I'd rather be alerted to it. You are also correct that having them >>>> included draws attention that could easily encourage duplication of >>>> effort. >>>> >>>> Comments? >>>> >>>> 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) 846-1285 >>>> FAX: (352) 392-7029 >>>> >>>>>>> oscar(a)iam.unibe.ch 06/10/08 8:31 AM >>> >>>> >>>> I looked at the wiki page >>>> http://code.google.com/p/pharo/wiki/CurrentlyWorkingOn >>>> but it does not say much. >>>> >>>> I would like to work through some tests, but I cannot find an >>>> overview. >>>> >>>> The tests CharacterTest>>testHex and IntegerTest>>testHex are >>>> broken >>>> but seem to be very new. Stef, are you working on these? You >>>> seem to >>>> have written the tests ... >>>> >>>> - on >>>> >>>> >>>> _______________________________________________ >>>> 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 >

June 10, 2008

Re: [Pharo-project] self halt in RxParserTest>>testMatchesInwW

by Oscar Nierstrasz

You har the image-meister, so you should patch it, I think. I can only add a patch into the PharoInbox, but this is so trivial it is easier if you just update your master image. - on On Jun 10, 2008, at 6:33 PM, StÃ©phane Ducasse wrote: > Yes go ahead. > > Stef > > On Jun 10, 2008, at 2:06 PM, Oscar Nierstrasz wrote: > >> >> Stef, >> >> RxParserTest>>testMatchesInwW >> >> has a self halt in it dating from 2006, apparently added by you. >> >> I guess you should remove it ... The test runs fine otherwise. >> >> - on >> >> >> _______________________________________________ >> 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

June 10, 2008

Re: [Pharo-project] Who is working on which tests? Why are there new, broken tests?

by Oscar Nierstrasz

Hi Stef, I loaded a fresh pharo-dev image and updated everything. Then the testHex tests failed, so I fixed them. Can you please tell me which implementors of hex you find in your image? I only find Character>>hex and Float>>hex. I had to implement Integer>>hex myself. - on On Jun 10, 2008, at 6:38 PM, StÃ©phane Ducasse wrote: > testHex > self assert: $a hex '61' = '61'. > self assert: Character space hex = '20' > > is green on my image > > as well as this one > > testHex > self assert: 0 hex = '0'. > self assert: 12 hex = 'C'. > self assert: 1234 hex = '4D2'. > > They are red in yours? > > Stef > > > On Jun 10, 2008, at 4:00 PM, Oscar Nierstrasz wrote: > >> >> Well, I thought we would start to fix the existing broken tests >> before adding new broken tests. >> >> I would also be very happy to see some comments when someone adds a >> new broken test, so I know what the plan is. >> >> Now I added an implementation of Integer>>hex, for example, but I >> am not so sure why we need this. >> Ain't too many senders. An easier fix would have been to remove the >> broken test. >> >> Cheers, >> - on >> >> On Jun 10, 2008, at 15:53, Bill Schwab wrote: >> >>> Is your concern that the new tests are broken (which seems normal >>> to me >>> that they would start out that way), or are you objecting to their >>> being >>> included in the image? >>> >>> I can see arguments either way on the latter. If code in the >>> image is >>> wrong and a clearly correct but currently failing test highlights >>> it, >>> I'd rather be alerted to it. You are also correct that having them >>> included draws attention that could easily encourage duplication of >>> effort. >>> >>> Comments? >>> >>> 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) 846-1285 >>> FAX: (352) 392-7029 >>> >>>>>> oscar(a)iam.unibe.ch 06/10/08 8:31 AM >>> >>> >>> I looked at the wiki page >>> http://code.google.com/p/pharo/wiki/CurrentlyWorkingOn >>> but it does not say much. >>> >>> I would like to work through some tests, but I cannot find an >>> overview. >>> >>> The tests CharacterTest>>testHex and IntegerTest>>testHex are broken >>> but seem to be very new. Stef, are you working on these? You >>> seem to >>> have written the tests ... >>> >>> - on >>> >>> >>> _______________________________________________ >>> 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

June 10, 2008

Re: [Pharo-project] Who is working on which tests? Why are there new, broken tests?

by Oscar Nierstrasz

Hi Bill, That's not what I mean. I agree fully with you that it is good to add tests that show in which way the system is broken. Adding tests for methods that don't even exist doesn't make much sense to me right now. testHex is (was) testing something that doesn't exist. OK if you are doing test-driven development. Not good if you want a system to be coherent and understandable. At the very least such tests need comments to explain why they have been added. Tests that are fragile and meaningless is also bad. The testHash tests that test that a hash returns a specific value are not good. I prefer to get rid of them. On Jun 10, 2008, at 5:34 PM, Bill Schwab wrote: > But if the test is revealing a true flaw in the system, better to keep > it than to remove it and pat ourselves on the back about "all tests > passing." > > 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) 846-1285 > FAX: (352) 392-7029 > >>>> oscar(a)iam.unibe.ch 06/10/08 10:00 AM >>> > > Well, I thought we would start to fix the existing broken tests before > adding new broken tests. > > I would also be very happy to see some comments when someone adds a > new broken test, so I know what the plan is. > > Now I added an implementation of Integer>>hex, for example, but I am > not so sure why we need this. > Ain't too many senders. An easier fix would have been to remove the > broken test. > > Cheers, > - on > > On Jun 10, 2008, at 15:53, Bill Schwab wrote: > >> Is your concern that the new tests are broken (which seems normal to >> me >> that they would start out that way), or are you objecting to their >> being >> included in the image? >> >> I can see arguments either way on the latter. If code in the image >> is >> wrong and a clearly correct but currently failing test highlights it, >> I'd rather be alerted to it. You are also correct that having them >> included draws attention that could easily encourage duplication of >> effort. >> >> Comments? >> >> 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) 846-1285 >> FAX: (352) 392-7029 >> >>>>> oscar(a)iam.unibe.ch 06/10/08 8:31 AM >>> >> >> I looked at the wiki page >> http://code.google.com/p/pharo/wiki/CurrentlyWorkingOn >> but it does not say much. >> >> I would like to work through some tests, but I cannot find an >> overview. >> >> The tests CharacterTest>>testHex and IntegerTest>>testHex are broken >> but seem to be very new. Stef, are you working on these? You seem >> to >> have written the tests ... >> >> - on >> >> >> _______________________________________________ >> 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

June 10, 2008

Re: [Pharo-project] Who is working on which tests? Why are there new, broken tests?

by StÃ©phane Ducasse

testHex self assert: $a hex '61' = '61'. self assert: Character space hex = '20' is green on my image as well as this one testHex self assert: 0 hex = '0'. self assert: 12 hex = 'C'. self assert: 1234 hex = '4D2'. They are red in yours? Stef On Jun 10, 2008, at 4:00 PM, Oscar Nierstrasz wrote: > > Well, I thought we would start to fix the existing broken tests > before adding new broken tests. > > I would also be very happy to see some comments when someone adds a > new broken test, so I know what the plan is. > > Now I added an implementation of Integer>>hex, for example, but I am > not so sure why we need this. > Ain't too many senders. An easier fix would have been to remove the > broken test. > > Cheers, > - on > > On Jun 10, 2008, at 15:53, Bill Schwab wrote: > >> Is your concern that the new tests are broken (which seems normal >> to me >> that they would start out that way), or are you objecting to their >> being >> included in the image? >> >> I can see arguments either way on the latter. If code in the image >> is >> wrong and a clearly correct but currently failing test highlights it, >> I'd rather be alerted to it. You are also correct that having them >> included draws attention that could easily encourage duplication of >> effort. >> >> Comments? >> >> 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) 846-1285 >> FAX: (352) 392-7029 >> >>>>> oscar(a)iam.unibe.ch 06/10/08 8:31 AM >>> >> >> I looked at the wiki page >> http://code.google.com/p/pharo/wiki/CurrentlyWorkingOn >> but it does not say much. >> >> I would like to work through some tests, but I cannot find an >> overview. >> >> The tests CharacterTest>>testHex and IntegerTest>>testHex are broken >> but seem to be very new. Stef, are you working on these? You seem >> to >> have written the tests ... >> >> - on >> >> >> _______________________________________________ >> 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 >

June 10, 2008

Re: [Pharo-project] Why does Installer package stay dirty?

by StÃ©phane Ducasse

for the installer I had some problem at one point so damien hardcoded the version we load. Stef On Jun 10, 2008, at 4:20 PM, Oscar Nierstrasz wrote: > > When I update a pharo-dev image, I see that Installer still has > updates. > > However I cannot update this consistently. > > If I load Installer-sd.4.mcz then Installer-dc.4.mcz is > highlighted. One of these two should be deleted, I think. > Which one? > > - on > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 10, 2008

Re: [Pharo-project] Who is working on which tests? Why are there new, broken tests?

by StÃ©phane Ducasse

I do not remember what we did with lukas about hex I know that we want hex but I forgot. :( Stef On Jun 10, 2008, at 2:31 PM, Oscar Nierstrasz wrote: > > I looked at the wiki page http://code.google.com/p/pharo/wiki/CurrentlyWorkingOn > but it does not say much. > > I would like to work through some tests, but I cannot find an > overview. > > The tests CharacterTest>>testHex and IntegerTest>>testHex are broken > but seem to be very new. Stef, are you working on these? You seem > to have written the tests ... I think that these tests are from serge or harvested from a mantis entry. > > > - on > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 10, 2008

Re: [Pharo-project] KernelTests green

by StÃ©phane Ducasse

We checked with lukas what is strange is that the same tests are green in 3.10. Stef On Jun 10, 2008, at 3:48 PM, Oscar Nierstrasz wrote: > > I have posted some patches to the inbox to make the Kernel Number > tests run, and in the Issues page I propose to delete a bunch of > nonsensical testHash tests. With these changes the Kernel tests > should all be green. > > - on > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 10, 2008

Re: [Pharo-project] self halt in RxParserTest>>testMatchesInwW

by StÃ©phane Ducasse

Yes go ahead. Stef On Jun 10, 2008, at 2:06 PM, Oscar Nierstrasz wrote: > > Stef, > > RxParserTest>>testMatchesInwW > > has a self halt in it dating from 2006, apparently added by you. > > I guess you should remove it ... The test runs fine otherwise. > > - on > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 10, 2008

Re: [Pharo-project] Who is working on which tests? Why are there new, broken tests?

by Bill Schwab

But if the test is revealing a true flaw in the system, better to keep it than to remove it and pat ourselves on the back about "all tests passing." 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) 846-1285 FAX: (352) 392-7029 >>> oscar(a)iam.unibe.ch 06/10/08 10:00 AM >>> Well, I thought we would start to fix the existing broken tests before adding new broken tests. I would also be very happy to see some comments when someone adds a new broken test, so I know what the plan is. Now I added an implementation of Integer>>hex, for example, but I am not so sure why we need this. Ain't too many senders. An easier fix would have been to remove the broken test. Cheers, - on On Jun 10, 2008, at 15:53, Bill Schwab wrote: > Is your concern that the new tests are broken (which seems normal to > me > that they would start out that way), or are you objecting to their > being > included in the image? > > I can see arguments either way on the latter. If code in the image is > wrong and a clearly correct but currently failing test highlights it, > I'd rather be alerted to it. You are also correct that having them > included draws attention that could easily encourage duplication of > effort. > > Comments? > > 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) 846-1285 > FAX: (352) 392-7029 > >>>> oscar(a)iam.unibe.ch 06/10/08 8:31 AM >>> > > I looked at the wiki page > http://code.google.com/p/pharo/wiki/CurrentlyWorkingOn > but it does not say much. > > I would like to work through some tests, but I cannot find an > overview. > > The tests CharacterTest>>testHex and IntegerTest>>testHex are broken > but seem to be very new. Stef, are you working on these? You seem to > have written the tests ... > > - on > > > _______________________________________________ > 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

June 10, 2008

[Pharo-project] Why does Installer package stay dirty?

by Oscar Nierstrasz

When I update a pharo-dev image, I see that Installer still has updates. However I cannot update this consistently. If I load Installer-sd.4.mcz then Installer-dc.4.mcz is highlighted. One of these two should be deleted, I think. Which one? - on

June 10, 2008

Re: [Pharo-project] Who is working on which tests? Why are there new, broken tests?

by Oscar Nierstrasz

Well, I thought we would start to fix the existing broken tests before adding new broken tests. I would also be very happy to see some comments when someone adds a new broken test, so I know what the plan is. Now I added an implementation of Integer>>hex, for example, but I am not so sure why we need this. Ain't too many senders. An easier fix would have been to remove the broken test. Cheers, - on On Jun 10, 2008, at 15:53, Bill Schwab wrote: > Is your concern that the new tests are broken (which seems normal to > me > that they would start out that way), or are you objecting to their > being > included in the image? > > I can see arguments either way on the latter. If code in the image is > wrong and a clearly correct but currently failing test highlights it, > I'd rather be alerted to it. You are also correct that having them > included draws attention that could easily encourage duplication of > effort. > > Comments? > > 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) 846-1285 > FAX: (352) 392-7029 > >>>> oscar(a)iam.unibe.ch 06/10/08 8:31 AM >>> > > I looked at the wiki page > http://code.google.com/p/pharo/wiki/CurrentlyWorkingOn > but it does not say much. > > I would like to work through some tests, but I cannot find an > overview. > > The tests CharacterTest>>testHex and IntegerTest>>testHex are broken > but seem to be very new. Stef, are you working on these? You seem to > have written the tests ... > > - on > > > _______________________________________________ > 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

June 10, 2008

Re: [Pharo-project] Who is working on which tests? Why are there new, broken tests?

by Bill Schwab

Is your concern that the new tests are broken (which seems normal to me that they would start out that way), or are you objecting to their being included in the image? I can see arguments either way on the latter. If code in the image is wrong and a clearly correct but currently failing test highlights it, I'd rather be alerted to it. You are also correct that having them included draws attention that could easily encourage duplication of effort. Comments? 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) 846-1285 FAX: (352) 392-7029 >>> oscar(a)iam.unibe.ch 06/10/08 8:31 AM >>> I looked at the wiki page http://code.google.com/p/pharo/wiki/CurrentlyWorkingOn but it does not say much. I would like to work through some tests, but I cannot find an overview. The tests CharacterTest>>testHex and IntegerTest>>testHex are broken but seem to be very new. Stef, are you working on these? You seem to have written the tests ... - on _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 10, 2008

[Pharo-project] KernelTests green

by Oscar Nierstrasz

I have posted some patches to the inbox to make the Kernel Number tests run, and in the Issues page I propose to delete a bunch of nonsensical testHash tests. With these changes the Kernel tests should all be green. - on

June 10, 2008

Re: [Pharo-project] Who is working on which tests? Why are there new, broken tests?

by Oscar Nierstrasz

Right, ok. I have started to do use it to log my changes. - on On Jun 10, 2008, at 14:56, Serge Stinckwich wrote: > Maybe we could use the issues system to know who is working on what ?

June 10, 2008

Re: [Pharo-project] Who is working on which tests? Why are there new, broken tests?

by Serge Stinckwich

Maybe we could use the issues system to know who is working on what ? 2008/6/10 Oscar Nierstrasz <oscar(a)iam.unibe.ch>: > > I looked at the wiki page > http://code.google.com/p/pharo/wiki/CurrentlyWorkingOn but it does not say > much. > > I would like to work through some tests, but I cannot find an overview. > > The tests CharacterTest>>testHex and IntegerTest>>testHex are broken but > seem to be very new. Stef, are you working on these? You seem to have > written the tests ... > > - on > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Serge Stinckwich Smalltalkers do: [:it | All with: Class, (And love: it)] http://blog.doesnotunderstand.org/

June 10, 2008

[Pharo-project] Who is working on which tests? Why are there new, broken tests?

by Oscar Nierstrasz

I looked at the wiki page http://code.google.com/p/pharo/wiki/CurrentlyWorkingOn but it does not say much. I would like to work through some tests, but I cannot find an overview. The tests CharacterTest>>testHex and IntegerTest>>testHex are broken but seem to be very new. Stef, are you working on these? You seem to have written the tests ... - on

June 10, 2008

[Pharo-project] self halt in RxParserTest>>testMatchesInwW

by Oscar Nierstrasz

Stef, RxParserTest>>testMatchesInwW has a self halt in it dating from 2006, apparently added by you. I guess you should remove it ... The test runs fine otherwise. - on

June 10, 2008

Re: [Pharo-project] What is ScheduledControllers?

by Oscar Nierstrasz

Right. As far as I can tell this is all MVC stuff that can be removed. I have added a comment. - on On Jun 10, 2008, at 13:14, StÃ©phane Ducasse wrote: > Yes > > On Jun 10, 2008, at 12:47 PM, Alain Plantec wrote: > >> On Tuesday 10 June 2008 12:20:30 Oscar Nierstrasz wrote: >>> >>> I was looking at http://code.google.com/p/pharo/issues/detail?id=6 >>> and >>> discovered this is broken because StandardSystemView sends to >>> ScheduledControllers which does not exist. >>> >>> I googled for it and found it seems sometimes to be a class and >>> sometimes a global. Anyway it does not exist. Anyone know where it >>> came from? >> >> ControlManager>>Comment >> I represent the top level control over scheduling which controller >> of a view >> on the screen the user is actively using. ScheduledControllers is >> the global reference to an >> instance of me, the one attached to the Project currently being used. >> >> I think it's linked to MVC. ScheduledControllers is referenced from >> a lot of places >> (SystemNavigation default browseMethodsWithSourceString: >> 'ScheduledControllers'). >> I guess it remains to be cleaned by next steps of MVC removing. >> >> alain >> >> >>> >>> - on >>> >>> >>> _______________________________________________ >>> 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

June 10, 2008

Re: [Pharo-project] What is ScheduledControllers?

by StÃ©phane Ducasse

Yes On Jun 10, 2008, at 12:47 PM, Alain Plantec wrote: > On Tuesday 10 June 2008 12:20:30 Oscar Nierstrasz wrote: >> >> I was looking at http://code.google.com/p/pharo/issues/detail?id=6 >> and >> discovered this is broken because StandardSystemView sends to >> ScheduledControllers which does not exist. >> >> I googled for it and found it seems sometimes to be a class and >> sometimes a global. Anyway it does not exist. Anyone know where it >> came from? > > ControlManager>>Comment > I represent the top level control over scheduling which controller > of a view > on the screen the user is actively using. ScheduledControllers is > the global reference to an > instance of me, the one attached to the Project currently being used. > > I think it's linked to MVC. ScheduledControllers is referenced from > a lot of places > (SystemNavigation default browseMethodsWithSourceString: > 'ScheduledControllers'). > I guess it remains to be cleaned by next steps of MVC removing. > > alain > > >> >> - on >> >> >> _______________________________________________ >> 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 >

June 10, 2008

Re: [Pharo-project] fix Utilities offerCommonRequests -> UIEnvironment class

by StÃ©phane Ducasse

I have the impression that we could move that in SystemNavigation. Now it depends how we want to structure the UI implication. For now I would move the navigation methods from Utilities to SystemNavigation. UIEnvironment is certainly redondant On Jun 10, 2008, at 12:09 PM, Oscar Nierstrasz wrote: > > Stef, > > This is one of yours. UIEnvironment does not exist. > > Are you proposing to split up Utilities and move a lot of these > utility-like this to a new utility class called UIEnvironment? > > What is the motivation/rationale? I do not see what problem is > solved by introducing another utility class. > > Should the new class also stay in the System-Support category? > > - on > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 10, 2008

Re: [Pharo-project] Re: fix Utilities classFromPattern:withCaption: -> Browser

by StÃ©phane Ducasse

It should not be in utilities but I imagine in System Navigation On Jun 10, 2008, at 12:04 PM, Oscar Nierstrasz wrote: > > > Oops. I meant Stef. The original request was submitted by Stef, > not Damien. > > - on > > On Jun 10, 2008, at 12:02, Oscar Nierstrasz wrote: > >> >> Damien, >> >> I do not understand this issue. >> >> http://code.google.com/p/pharo/issues/detail?id=2 >> >> Example doit: >> Utilities classFromPattern: 'orph' withCaption: 'Morphs' >> This generates a menu with the caption as heading. The name of the >> selected class is returned. >> I do not understand the issue here. The following code will fire up >> a browser. >> (Utilities classFromPattern: 'orph' withCaption: 'Morphs') browse >> WHat needs to be fixed? >> - on > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 10, 2008

Re: [Pharo-project] What is ScheduledControllers?

by Alain Plantec

On Tuesday 10 June 2008 12:20:30 Oscar Nierstrasz wrote: > > I was looking at http://code.google.com/p/pharo/issues/detail?id=6 and > discovered this is broken because StandardSystemView sends to > ScheduledControllers which does not exist. > > I googled for it and found it seems sometimes to be a class and > sometimes a global. Anyway it does not exist. Anyone know where it > came from? ControlManager>>Comment I represent the top level control over scheduling which controller of a view on the screen the user is actively using. ScheduledControllers is the global reference to an instance of me, the one attached to the Project currently being used. I think it's linked to MVC. ScheduledControllers is referenced from a lot of places (SystemNavigation default browseMethodsWithSourceString: 'ScheduledControllers'). I guess it remains to be cleaned by next steps of MVC removing. alain > > - on > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >

June 10, 2008

[Pharo-project] What is ScheduledControllers?

by Oscar Nierstrasz

I was looking at http://code.google.com/p/pharo/issues/detail?id=6 and discovered this is broken because StandardSystemView sends to ScheduledControllers which does not exist. I googled for it and found it seems sometimes to be a class and sometimes a global. Anyway it does not exist. Anyone know where it came from? - on

June 10, 2008

[Pharo-project] fix Utilities offerCommonRequests -> UIEnvironment class

by Oscar Nierstrasz

Stef, This is one of yours. UIEnvironment does not exist. Are you proposing to split up Utilities and move a lot of these utility-like this to a new utility class called UIEnvironment? What is the motivation/rationale? I do not see what problem is solved by introducing another utility class. Should the new class also stay in the System-Support category? - on

June 10, 2008

[Pharo-project] Re: fix Utilities classFromPattern:withCaption: -> Browser

by Oscar Nierstrasz

Oops. I meant Stef. The original request was submitted by Stef, not Damien. - on On Jun 10, 2008, at 12:02, Oscar Nierstrasz wrote: > > Damien, > > I do not understand this issue. > > http://code.google.com/p/pharo/issues/detail?id=2 > > Example doit: > Utilities classFromPattern: 'orph' withCaption: 'Morphs' > This generates a menu with the caption as heading. The name of the > selected class is returned. > I do not understand the issue here. The following code will fire up > a browser. > (Utilities classFromPattern: 'orph' withCaption: 'Morphs') browse > WHat needs to be fixed? > - on

June 10, 2008

[Pharo-project] fix Utilities classFromPattern:withCaption: -> Browser

by Oscar Nierstrasz

Damien, I do not understand this issue. http://code.google.com/p/pharo/issues/detail?id=2 Example doit: Utilities classFromPattern: 'orph' withCaption: 'Morphs' This generates a menu with the caption as heading. The name of the selected class is returned. I do not understand the issue here. The following code will fire up a browser. (Utilities classFromPattern: 'orph' withCaption: 'Morphs') browse WHat needs to be fixed? - on

June 10, 2008

Re: [Pharo-project] HaveALookAt

by Oscar Nierstrasz

Thanks. Fixed. - on On Jun 10, 2008, at 9:58, Norbert Hartl wrote: > I think the link to the packages issue should point to > > http://www.squeaksource.com/PackagesForSqueak/ > > Norbert > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 10, 2008

[Pharo-project] HaveALookAt

by Norbert Hartl

I think the link to the packages issue should point to http://www.squeaksource.com/PackagesForSqueak/ Norbert

June 10, 2008

[Pharo-project] Are wiki comments making it to the list?

by Victor Rodriguez

Hello, I'm not sure comments added to wiki pages are making it to the site. Could it be that the list does not accept email from non-subscribers? If so, could someone please "subscribe" or otherwise "whitelist" codesite-noreply(a)google.com? Thanks, VÃctor RodrÃguez.

June 10, 2008

Re: [Pharo-project] HaveALootAt -> HaveALookAt -- where are the open tasks?

by StÃ©phane Ducasse

The milestone list gives a good impression of large todo items. The old task list lists simpler todo items. Stef On Jun 9, 2008, at 1:47 PM, Oscar Nierstrasz wrote: > > I guess this page should be called "HaveALookAt" but I do not see > how to rename a wiki page. > > Anybody know how to do this? > > http://code.google.com/p/pharo/wiki/HaveALootAt > > Where is the list of open tasks? I thought it might be here. > > - on > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 9, 2008

Re: [Pharo-project] Issues (was: HaveALootAt ...)

by Damien Cassou

On Mon, Jun 9, 2008 at 5:22 PM, Oscar Nierstrasz <oscar(a)iam.unibe.ch> wrote: > I do not see any tags. Wiki pages have labels, but Issues don't have tags, > but they do have comments. > Do you simply mean the Comment text should include the text "COMMENT"? Issues have labels (at the very bottom). We can add new kinds of labels in the Administration pane. However, in this particular case, I meant: "Change the status of the issue from ACCEPTED to COMMENT". > PS: Your emails are starting to get as cryptic as Stef's -- you must be > hanging around with him too much ;-) Oooops, I will try to avoid writing like him :-). Thanks for the warning. -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

June 9, 2008

Re: [Pharo-project] Issues (was: HaveALootAt ...)

by Oscar Nierstrasz

I do not see any tags. Wiki pages have labels, but Issues don't have tags, but they do have comments. Do you simply mean the Comment text should include the text "COMMENT"? - on PS: Your emails are starting to get as cryptic as Stef's -- you must be hanging around with him too much ;-) On Jun 9, 2008, at 16:06, Damien Cassou wrote: > On Mon, Jun 9, 2008 at 4:02 PM, Oscar Nierstrasz > <oscar(a)iam.unibe.ch> wrote: >> >> OK, I will try to help migrate the issues. >> >> But the old issues were not very clear. It would be good to add a >> bit more >> explanation. >> >> I will add comments if I do not understand the issues. > > You should also add the tag COMMENT. > > > -- > Damien Cassou > Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good > luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 9, 2008

Re: [Pharo-project] Issues (was: HaveALootAt ...)

by Damien Cassou

On Mon, Jun 9, 2008 at 4:02 PM, Oscar Nierstrasz <oscar(a)iam.unibe.ch> wrote: > > OK, I will try to help migrate the issues. > > But the old issues were not very clear. It would be good to add a bit more > explanation. > > I will add comments if I do not understand the issues. You should also add the tag COMMENT. -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

June 9, 2008

Re: [Pharo-project] Issues (was: HaveALootAt ...)

by Oscar Nierstrasz

OK, I will try to help migrate the issues. But the old issues were not very clear. It would be good to add a bit more explanation. I will add comments if I do not understand the issues. - on On Jun 9, 2008, at 14:58, Damien Cassou wrote: > > Look at "issues". I have already migrated 4 issues (1 is closed and is > hidden by default). We will have to manually migrate the rest. > > --

June 9, 2008

Re: [Pharo-project] HaveALootAt -> HaveALookAt -- where are the open tasks?

by Damien Cassou

On Mon, Jun 9, 2008 at 2:44 PM, Oscar Nierstrasz <oscar(a)iam.unibe.ch> wrote: > > OK, got it. (Create new page and delete the old one -- duh.) > > But where are the open tasks? > > - on > > On Jun 9, 2008, at 13:47, Oscar Nierstrasz wrote: > >> >> I guess this page should be called "HaveALookAt" but I do not see how to >> rename a wiki page. >> >> Anybody know how to do this? >> >> http://code.google.com/p/pharo/wiki/HaveALootAt >> >> Where is the list of open tasks? I thought it might be here. Look at "issues". I have already migrated 4 issues (1 is closed and is hidden by default). We will have to manually migrate the rest. -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

June 9, 2008

Re: [Pharo-project] HaveALootAt -> HaveALookAt -- where are the open tasks?

by Oscar Nierstrasz

OK, got it. (Create new page and delete the old one -- duh.) But where are the open tasks? - on On Jun 9, 2008, at 13:47, Oscar Nierstrasz wrote: > > I guess this page should be called "HaveALookAt" but I do not see > how to rename a wiki page. > > Anybody know how to do this? > > http://code.google.com/p/pharo/wiki/HaveALootAt > > Where is the list of open tasks? I thought it might be here. > > - on > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 9, 2008

[Pharo-project] HaveALootAt -> HaveALookAt -- where are the open tasks?

by Oscar Nierstrasz

I guess this page should be called "HaveALookAt" but I do not see how to rename a wiki page. Anybody know how to do this? http://code.google.com/p/pharo/wiki/HaveALootAt Where is the list of open tasks? I thought it might be here. - on

June 9, 2008

[Pharo-project] Harvesting some fixes

by StÃ©phane Ducasse

Hi all I will harvest the MVC cleaning step one. I harvested some changes. I suggest you to reload 10034. because of some manipulations I did with the scriptloader

June 9, 2008

Re: [Pharo-project] editing pharo home page?

by Damien Cassou

On Mon, Jun 9, 2008 at 1:00 PM, Oscar Nierstrasz <oscar(a)iam.unibe.ch> wrote: > > How do I edit the Pharo home page? > > http://code.google.com/p/pharo/ > > I see no edit button. > Go to the administration part. -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

June 9, 2008

[Pharo-project] editing pharo home page?

by Oscar Nierstrasz

How do I edit the Pharo home page? http://code.google.com/p/pharo/ I see no edit button. - on

June 9, 2008

Re: [Pharo-project] I harvest ...

by StÃ©phane Ducasse

Not yet too dead yesterday. And indeed I see some problems with MC to remove empty categories. May be I will try with a script and hope that I will not end up with dirty packages. So far for MVC step one I got only one conflict that I will resolve. Stef On Jun 9, 2008, at 10:45 AM, Norbert Hartl wrote: > On Sun, 2008-06-08 at 10:42 +0200, StÃ©phane Ducasse wrote: >> - Adrian trait core cleaning. >> - Serge fixing tests >> >> I plan to harvest on: and MVC clean up. >> and some graphics test cleaning. >> > Did you have look at my changeset for removing the > mathod categories for nebraska? > > Norbert > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 9, 2008