September 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] dnu - isScarySelector not found

by StÃ©phane Ducasse

Apparently some old code in OB is still referencing the code before we clean the isScarySelector with lukas Lukas may be we should have deprecated it. Carlos which image are you using? BTW create a new thread of discussion > Hi, > > On any existing subclass of Object, I add a class method, I add > "testSelector" > > Got MNU Metaclass(class) dnu isScarySelector > OBMethodDefinition>>confirmMethod: > > What is wrong? > > Regards, Carlos > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 4, 2009

Re: [Pharo-project] [ANN]

by Michael Roberts

I also prefer ReadStream on: since it is explicit about the stream you want rather than expecting the collection to know and have the protocol. I don't really see the need to rewrite the whole image. Cheers mike On Friday, September 4, 2009, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Peter you should have a look at Squeak by example and soon pharo by > example > > in short if you had a category with *MyPackage in a class of another > package then > your package MyPackage will contain the extensions. > > You can see the extension by clicking on the Monticello browser and > clicking browse. > > In fact this is a good practice to check the extensions of a package > before publishing it. > > I can show you during the break :) > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 4, 2009

Re: [Pharo-project] Getting Pharo 1.0 released

by StÃ©phane Ducasse

I should also move simpleButton from Sound to Morph - generate new source code. On Sep 4, 2009, at 9:19 AM, Adrian Lienhard wrote: > I went through all 1.0 items and changed those to 1.1 that I think are > not that important. There are 24 issues left that I think need to be > fixed before we can declare 1.0 final. Among them are a lot of > debugger problems likely related to closures that may be hard to fix. > > Peter, one issue is "fix all failing tests". So we really want to "be > green" for the release! > > Two other things we need to prepare is the one-click image (I think > Marcus said he will look into this) and a secondary update stream that > allows us to push maintenance changes to 1.0.x at the same time as we > work on 1.1. > > So, there is still quite some work left... > > Adrian > > On Sep 4, 2009, at 08:52 , StÃ©phane Ducasse wrote: > >> Hi all >> >> I suggest the following: >> we go over the bug tracker and move to 1.1 all the issues that are >> not showstopper >> and we declare pharo 1.0 done >> and we open pharo 1.1 alpha >> >> Does it make sense to you? >> Stef >> >> _______________________________________________ >> 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

Sept. 4, 2009

Re: [Pharo-project] Getting Pharo 1.0 released

by StÃ©phane Ducasse

On Sep 4, 2009, at 9:03 AM, laurent laffont wrote: > > On Fri, Sep 4, 2009 at 8:52 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > > wrote: > Hi all > > I suggest the following: > we go over the bug tracker and move to 1.1 all the issues > that are > not showstopper > and we declare pharo 1.0 done > and we open pharo 1.1 alpha > > Does it make sense to you? > Stef > > Is "Pharo by Example" done ? Yes :) > May be it's a good idea to release both together as a 1.0 version in > the news is a way to attract new developpers and new developpers > need documentation. > > > Laurent Laffont > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 4, 2009

Re: [Pharo-project] Getting Pharo 1.0 released

by Michael Roberts

on the debugger front , Eliot has some fixes so that should move us forwards. Cheers mike On Friday, September 4, 2009, Peter Hugosson-Miller <oldmanlink(a)gmail.com> wrote: > On Fri, Sep 4, 2009 at 9:19 AM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > > > I went through all 1.0 items and changed those to 1.1 that I think are > not that important. There are 24 issues left that I think need to be > fixed before we can declare 1.0 final. Among them are a lot of > debugger problems likely related to closures that may be hard to fix. > > Peter, one issue is "fix all failing tests". So we really want to "be > green" for the release! > > Two other things we need to prepare is the one-click image (I think > Marcus said he will look into this) and a secondary update stream that > allows us to push maintenance changes to 1.0.x at the same time as we > work on 1.1. > > So, there is still quite some work left... > > Adrian > > On Sep 4, 2009, at 08:52 , StÃ©phane Ducasse wrote: > >> Hi all >> >> I suggest the following: >> Â Â Â we go over the bug tracker and move to 1.1 all the issues that are >> not showstopper >> Â Â Â and we declare pharo 1.0 done >> Â Â Â and we open pharo 1.1 alpha >> >> Does it make sense to you? >> Stef >> >> _______________________________________________ >> 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 > > Thanks Adrian, it's very good to know that my feelings are not against the spirit of the project ;-)> > -- > Cheers, > Peter >

Sept. 4, 2009

Re: [Pharo-project] [ANN]

by StÃ©phane Ducasse

Peter you should have a look at Squeak by example and soon pharo by example in short if you had a category with *MyPackage in a class of another package then your package MyPackage will contain the extensions. You can see the extension by clicking on the Monticello browser and clicking browse. In fact this is a good practice to check the extensions of a package before publishing it. I can show you during the break :) Stef

Sept. 4, 2009

Re: [Pharo-project] Getting Pharo 1.0 released

by Peter Hugosson-Miller

On Fri, Sep 4, 2009 at 9:19 AM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > I went through all 1.0 items and changed those to 1.1 that I think are > not that important. There are 24 issues left that I think need to be > fixed before we can declare 1.0 final. Among them are a lot of > debugger problems likely related to closures that may be hard to fix. > > Peter, one issue is "fix all failing tests". So we really want to "be > green" for the release! > > Two other things we need to prepare is the one-click image (I think > Marcus said he will look into this) and a secondary update stream that > allows us to push maintenance changes to 1.0.x at the same time as we > work on 1.1. > > So, there is still quite some work left... > > Adrian > > On Sep 4, 2009, at 08:52 , StÃ©phane Ducasse wrote: > > > Hi all > > > > I suggest the following: > > we go over the bug tracker and move to 1.1 all the issues that are > > not showstopper > > and we declare pharo 1.0 done > > and we open pharo 1.1 alpha > > > > Does it make sense to you? > > Stef > > > > _______________________________________________ > > 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 > Thanks Adrian, it's very good to know that my feelings are not against the spirit of the project ;-)> -- Cheers, Peter

Sept. 4, 2009

Re: [Pharo-project] [ANN] 10430

by StÃ©phane Ducasse

> - Polymorph Widgets > what widgets were added, changed? check the version comments of UIEnhancements. Stef

Sept. 4, 2009

Re: [Pharo-project] Added package SLICE-RemoveReferencesToReadStreamOn-PeterHugossonMiller.3 to PharoInbox

by StÃ©phane Ducasse

This is fun because when I read col readStream it takes me some milliseconds to process more than ReadStream on: col now if the other smalltalk use readStream and writeStream we should keep it like that because it is a minor point. Stef On Sep 4, 2009, at 12:04 AM, Henrik Johansen wrote: > In VW, the methods are called readStream and writeStream. > > Personally, I prefer that, as a method starting with as... to me > indicates having created a new equivalent object, not just a wrapper > which is used to access the original object. > There's a big difference between calling f.ex. _as_Array on an > SequenceableCollection, then messing with the elements of the object > returned, and doing the same with a method called asReadStream. > > Cheers, > Henry > > On Sep 3, 2009, at 4:46 13PM, Peter Hugosson-Miller wrote: > >> I don't know how this is done in VW, but in any case I would also >> prefer the method to be called #asReadStream, since it more clearly >> expresses the fact that there is a conversion happening. >> >> In the same way, I would like to suggest the method >> SequenceableCollection>>#writeStream would be better named >> #asWriteStream, and I also think that the creation of a new method >> SequenceableCollection>>#asReadWriteStream would be a good idea. >> >> -- >> Cheers, >> Peter >> >> On Thu, Sep 3, 2009 at 4:32 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr >> > wrote: >> I'm integrating your changes. >> Now I was wondering if somebody knows if it VW we get readStream too >> because I would prefer to have a better message than readStream >> aCol asReadStream ? >> >> What do you think? >> >> Stef >> >> >> >> On Sep 2, 2009, at 9:59 PM, Peter Hugosson-Miller wrote: >> >> > On Wed, Sep 2, 2009 at 9:30 PM, Adrian Lienhard <adi(a)netstyle.ch> >> > wrote: >> > Welcome, Peter! >> > >> > When you commit a change it would be good to also open an issue >> in the >> > tracker (and tell there which slice this is and in the slice >> comment >> > say which issue number it is). Like this it is easier to keep >> track of >> > changes. >> > >> > Cheers, >> > Adrian >> > >> > Strange, I thought I had done that, but it was probably just the >> > wrong part of the system (I'm just learning). >> > >> > This is the issue I created for the slice: http://code.google.com/p/pharo/issues/detail?id=1144 >> > so could you please tell me what I should have done instead (or as >> > well ;-))? >> > >> > Thanks in advance, >> > Peter >> > _______________________________________________ >> > 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

Sept. 4, 2009

Re: [Pharo-project] Getting Pharo 1.0 released

by Adrian Lienhard

I went through all 1.0 items and changed those to 1.1 that I think are not that important. There are 24 issues left that I think need to be fixed before we can declare 1.0 final. Among them are a lot of debugger problems likely related to closures that may be hard to fix. Peter, one issue is "fix all failing tests". So we really want to "be green" for the release! Two other things we need to prepare is the one-click image (I think Marcus said he will look into this) and a secondary update stream that allows us to push maintenance changes to 1.0.x at the same time as we work on 1.1. So, there is still quite some work left... Adrian On Sep 4, 2009, at 08:52 , StÃ©phane Ducasse wrote: > Hi all > > I suggest the following: > we go over the bug tracker and move to 1.1 all the issues that are > not showstopper > and we declare pharo 1.0 done > and we open pharo 1.1 alpha > > Does it make sense to you? > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 4, 2009