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

[Pharo-project] SqNumberParserTests green

by Nicolas Cellier

PharoInbox/KernelTests-nice.217 Ancestors: KernelTests-StephaneDucasse.216 Accepting lower case 16rff broke float reading in base 16. Let NumberParser test auto-detect whether lowercase digit letters are allowed or not, and then disbale non-10-based floating point tests. This makes the tests green again.

March 16, 2010

Re: [Pharo-project] packages :)

by Lukas Renggli

Can you provide a Gofer expression to load it? Lukas On 16 March 2010 17:21, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi > > I started to reimplement the package class is did because the previous one was a bit messy. > I'm currently migrating old the tests to the new implementation and for now I have around 93% coverage. > I started to build a stupid browser to check my api. > Doru started to code a Glamour browser to see if this was ok. > > Now I would really like if > Â Â Â Â - somebody could have a look at the code > Â Â Â Â - develop a simple package browser showing class extensions (it would help me to define > Â Â Â Â a good api to walk though a package). I started to use Momo and this is why I reimplemented the class > Â Â Â Â but so far I get nearly the same interface and I think that I can do better. > > Of course there are comments and tests so if one of you want to join we could do remote pair coding to be able > to release a first version. So far > Â Â Â Â - integration with MC > Â Â Â Â - migrating from packageInfo > Â Â Â Â - event notification > Â Â Â Â are missing. > > Stef > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli http://www.lukas-renggli.ch

March 16, 2010

[Pharo-project] packages :)

by StÃ©phane Ducasse

Hi I started to reimplement the package class is did because the previous one was a bit messy. I'm currently migrating old the tests to the new implementation and for now I have around 93% coverage. I started to build a stupid browser to check my api. Doru started to code a Glamour browser to see if this was ok. Now I would really like if - somebody could have a look at the code - develop a simple package browser showing class extensions (it would help me to define a good api to walk though a package). I started to use Momo and this is why I reimplemented the class but so far I get nearly the same interface and I think that I can do better. Of course there are comments and tests so if one of you want to join we could do remote pair coding to be able to release a first version. So far - integration with MC - migrating from packageInfo - event notification are missing. Stef

March 16, 2010

[Pharo-project] [update 1.1] #11273

by StÃ©phane Ducasse

11273 ----- - Issue 2136: Smalltalk and SmalltalkImage Rewrite Smalltalk to SmalltalkGlobals for some API. Pay attention this may take some times. 103 packages impacted. Stef And yes this was a bad idea to do this integration with the wifi in an hotel... There is no bug in the scriptLoader, just network time out at the wrong moment.

March 16, 2010

Re: [Pharo-project] Code Freeze 1.1?

by StÃ©phane Ducasse

>>>> for code 1.1 I would like to be able to remove Preferences. >>>> >>>> Stef >>> >>> Personally, I think it's rather important to have a stable release where both are in, but where the Preferences adding raises deprecations, and the browser removed. >> >> Sure this is why I did not say removed :) >> But nobody in the image should refer to it. > > Ah, to me it read like you wanted to remove it completely :) No I will as the first action in 1.2 :) > I thought Alain already recreated all uses in the core image as settings? Not all we still have Preferences used in the image and some fixes reintroduced references. Stef

March 16, 2010

Re: [Pharo-project] Code Freeze 1.1?

by Henrik Johansen

On Mar 16, 2010, at 4:59 27PM, StÃ©phane Ducasse wrote: > > On Mar 16, 2010, at 4:52 PM, Henrik Johansen wrote: > >> >> On Mar 16, 2010, at 4:01 51PM, StÃ©phane Ducasse wrote: >> >>> for code 1.1 I would like to be able to remove Preferences. >>> >>> Stef >> >> Personally, I think it's rather important to have a stable release where both are in, but where the Preferences adding raises deprecations, and the browser removed. > > Sure this is why I did not say removed :) > But nobody in the image should refer to it. Ah, to me it read like you wanted to remove it completely :) I thought Alain already recreated all uses in the core image as settings?

March 16, 2010

Re: [Pharo-project] Code Freeze 1.1?

by StÃ©phane Ducasse

On Mar 16, 2010, at 4:52 PM, Henrik Johansen wrote: > > On Mar 16, 2010, at 4:01 51PM, StÃ©phane Ducasse wrote: > >> for code 1.1 I would like to be able to remove Preferences. >> >> Stef > > Personally, I think it's rather important to have a stable release where both are in, but where the Preferences adding raises deprecations, and the browser removed. Sure this is why I did not say removed :) But nobody in the image should refer to it. > Then, in the future, when someone tries to port an old project with Preferences, we can say "Load it into a 1.1 image and fix it there". > Without the availability of such a middle step, it'd be somewhat of a leap getting the code up to date. (unless you do it offline, but that's not really the smalltalk way, is it?) > > Cheers, > Henry > >> On Mar 16, 2010, at 10:19 AM, Marcus Denker wrote: >> >>> Hi, >>> >>> Now with 1.0 done, I think we should think about freezing 1.1. >>> >>> The main reason of course is that 1.1 is *far more pleasent* to use than 1.0. The other >>> thing is that 1.1 did change quite some things that have impact on external code (Preferences, >>> as an example). >>> >>> So I think we should >>> >>> -> start slowing down on 1.1 (Stef suggested that already) >>> -> start polishing (tests...) >>> -> start to look at the Dev image. >>> -> Official code freeze end of March. >>> -> Release if possible end of April (this of course depends on the state of things). >>> >>> >>> Any reasons against? >>> >>> >>> Marcus >>> >>> >>> -- >>> Marcus Denker -- http://www.marcusdenker.de >>> INRIA Lille -- Nord Europe. Team RMoD. >>> >>> >>> _______________________________________________ >>> 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 16, 2010

Re: [Pharo-project] Pharo party near Annecy, France

by Geert Claes

Beautiful area ... and so close to Les Trois VallÃ©es :) -- View this message in context: http://n4.nabble.com/Pharo-party-near-Annecy-France-tp1569407p1595092.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

March 16, 2010

Re: [Pharo-project] Code Freeze 1.1?

by Henrik Johansen

On Mar 16, 2010, at 4:01 51PM, StÃ©phane Ducasse wrote: > for code 1.1 I would like to be able to remove Preferences. > > Stef Personally, I think it's rather important to have a stable release where both are in, but where the Preferences adding raises deprecations, and the browser removed. Then, in the future, when someone tries to port an old project with Preferences, we can say "Load it into a 1.1 image and fix it there". Without the availability of such a middle step, it'd be somewhat of a leap getting the code up to date. (unless you do it offline, but that's not really the smalltalk way, is it?) Cheers, Henry > On Mar 16, 2010, at 10:19 AM, Marcus Denker wrote: > >> Hi, >> >> Now with 1.0 done, I think we should think about freezing 1.1. >> >> The main reason of course is that 1.1 is *far more pleasent* to use than 1.0. The other >> thing is that 1.1 did change quite some things that have impact on external code (Preferences, >> as an example). >> >> So I think we should >> >> -> start slowing down on 1.1 (Stef suggested that already) >> -> start polishing (tests...) >> -> start to look at the Dev image. >> -> Official code freeze end of March. >> -> Release if possible end of April (this of course depends on the state of things). >> >> >> Any reasons against? >> >> >> Marcus >> >> >> -- >> Marcus Denker -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> >> >> _______________________________________________ >> 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 16, 2010

[Pharo-project] [update 1.1] #11272

by StÃ©phane Ducasse

11272 ----- Preparing lukas changes integration - second try

March 16, 2010