- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [ANN]

by StÃ©phane Ducasse

Yes but if we want to make sure that we could plug easily a new stream library we should either use virtual classes (quite difficult and major changes at language level) or readStream So readStream gives us a nice solution. Stef > 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 >> > > _______________________________________________ > 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 StÃ©phane Ducasse

ok look at the Regex package. Click browse and you will that regex has class extension in string and character. Stef > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > Hej Stef, > > I was up quite late last night (=this morning) preparing that huge > slice for the WriteStream on: issue, so I overslept this morning, > and I have to be at the train station by 12:00 today, so I think > I'll stay in my hÃ´tel until then. > > But if you can point me to a concrete example, I'm sure I'll > understand it when I see it. > > -- > Cheers, > Peter > _______________________________________________ > 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 StÃ©phane Ducasse

Yes me too but we should avoid hardcoding class references that core everywhere. Stef On Sep 3, 2009, at 11:33 PM, Michael van der Gulik wrote: > > > On Fri, Sep 4, 2009 at 3:21 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > > wrote: > - Issue 1144: Many occurrences of "ReadStream on: aCollection" which > can be replaced with "aCollection readStream" > > > For what it's worth, I prefer the style of "ReadStream on: xxx". I > prefer to choose the stream class rather than let the collection > choose it for me. > > Gulik. > > -- > http://gulik.pbwiki.com/ > _______________________________________________ > 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 Peter Hugosson-Miller

On Fri, Sep 4, 2009 at 9:38 AM, 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 > Hej Stef, I was up quite late last night (=this morning) preparing that huge slice for the WriteStream on: issue, so I overslept this morning, and I have to be at the train station by 12:00 today, so I think I'll stay in my hÃ´tel until then. But if you can point me to a concrete example, I'm sure I'll understand it when I see it. -- Cheers, Peter

Sept. 4, 2009

Re: [Pharo-project] Getting Pharo 1.0 released

by StÃ©phane Ducasse

Did eliot issue them? > on the debugger front , Eliot has some fixes so that should move us > forwards. > Cheers > mike

Sept. 4, 2009

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