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

Re: [Pharo-project] HowToContribute wiki page rewrite

by Damien Cassou

On Thu, Jun 5, 2008 at 11:31 AM, Serge Stinckwich <serge.stinckwich(a)doesnotunderstand.org> wrote: > I guess i'm not an administrator ;-) Fixed. -- 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 5, 2008

Re: [Pharo-project] About on:

by Damien Cassou

On Thu, Jun 5, 2008 at 8:52 AM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > > On Jun 5, 2008, at 00:27 , Bill Schwab wrote: > >> Stef, Damien, >> >> No surprise, I would argue that we proceed, and would also include a >> rename of #next to #nextOrNil and #next: to #nextAvailable:. All code in >> the image at the time should work as before. > > What would be the impact on code that is not in the image? Would all > external packages need to be adapted as well or would the current semantics > be preserved? In the case of changing 'ReadStream on: smth' to 'smth readStream' there is really nothing to change in external libraries. This change only enhance the code without changing anything. The refactoring can also be applied in some parts of the image without changing others. The change Bill proposes is completely different and I would propose to postpone it until we have more discussions and everybody agrees. There is no point in doing both at the same time. The changes are completely independent. -- 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 5, 2008

Re: [Pharo-project] About readStream on: vs readStream

by Damien Cassou

On Wed, Jun 4, 2008 at 8:36 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > I was wondering why you think that ReadStream on: anObject is worse than > anObject readStream? > Because you do not hardcode ReadStream? I already gave my opinion that at least 3 times :-). Here is it again: - no more direct reference on ReadStream where it is not necessary - allows different implementation of #readStream depending on the receiver class (different collection classes can use specific streams as it is the case in Nile. In GnuSmalltalk, WriteStream>>readStream answers a ReadStream without needing copy the collection) - clarify the code: I noticed the code becomes much more readable - use a method that has been there for ages -- 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 5, 2008

Re: [Pharo-project] HowToContribute wiki page rewrite

by Serge Stinckwich

I guess i'm not an administrator ;-) 2008/6/5 Damien Cassou <damien.cassou(a)gmail.com>: > On Wed, Jun 4, 2008 at 8:07 PM, Serge Stinckwich > <serge.stinckwich(a)doesnotunderstand.org> wrote: >> How could i edit the main page ? > > Administer -> Project Summary > > -- > 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 > -- Serge Stinckwich Smalltalkers do: [:it | All with: Class, (And love: it)] http://blog.doesnotunderstand.org/

June 5, 2008

Re: [Pharo-project] HowToContribute wiki page rewrite

by Damien Cassou

On Wed, Jun 4, 2008 at 8:07 PM, Serge Stinckwich <serge.stinckwich(a)doesnotunderstand.org> wrote: > How could i edit the main page ? Administer -> Project Summary -- 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 5, 2008

Re: [Pharo-project] HowToContribute wiki page rewrite

by Damien Cassou

On Thu, Jun 5, 2008 at 5:10 AM, Victor Rodriguez <victorr(a)gmail.com> wrote: > On Wed, Jun 4, 2008 at 3:20 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Hi victor >> If you can, do it but >> pay attention that we will certainly use pier or cmsbox at the end. (I know >> that the current wiki is slow). > > I think it is worth to do it, since there doesn't appear to be a firm > idea on when a Pier or Cmsbox site will be ready. > > Project owners, *please* add me to the project! > >> If you do it can you mark each page of the old one with a link to the new >> one. > > Not a problem. > > Su servidor, > > VÃctor RodrÃguez. > >> Stef >> On Jun 4, 2008, at 7:58 PM, Victor Rodriguez wrote: >> >>> On Wed, Jun 4, 2008 at 1:39 PM, StÃ©phane Ducasse >>> <stephane.ducasse(a)inria.fr> wrote: >>>> >>>> Thanks so may be we should move the wiki contents to this one >>>> but more importantly the tasks. >>> >>> I'll volunteer to move the wiki pages, as long as people don't mind if >>> it takes the rest of the week to do it (I can only manage a few hours >>> per week of "free time" :-P ). >>> >>> Victor. >>> >>> ps. Please add me to the project as victorr(a)gmail.com. Done. I've added everyone for which I had a gmail email address on my address book. -- 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 5, 2008

Re: [Pharo-project] About on:

by Adrian Lienhard

On Jun 5, 2008, at 00:27 , Bill Schwab wrote: > Stef, Damien, > > No surprise, I would argue that we proceed, and would also include a > rename of #next to #nextOrNil and #next: to #nextAvailable:. All > code in the image at the time should work as before. What would be the impact on code that is not in the image? Would all external packages need to be adapted as well or would the current semantics be preserved? Adrian > The next step (part B) would be to add exception-aware #next and > #next:. > > Damien and I could cook it up, try it, and then return with an "all > clear." > > 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 > > >>>> stephane.ducasse(a)inria.fr 6/4/2008 10:36 AM >>> > > On Jun 4, 2008, at 5:20 PM, Damien Cassou wrote: > >> On Wed, Jun 4, 2008 at 1:45 PM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >>> here is what I propose for on: >>> I will move your package out of the inbox so that the discussion >>> can go on >>> and >>> I try to integrate all the other changes. >>> Then with bill and others you propose how to proceed. >>> Is it ok ? >> >> What do you mean by 'I will move your package out of the inbox'? Do >> you mean you simply delete the packages or you moved them to Pharo? > > I mean move them to the treatedBox without putting in the image > >> Replacing 'ReadStream on: smth' by 'smth readStream' is not >> mandatory. >> However, it makes the code simpler to read, avoids a direct class >> reference and allows different implementation of #readStream >> depending >> on the kind of collection it is sent to. I do not think anyone is >> against that as soon as I apply the automatic refactoring >> carefully. I >> did that and didn't see any place where the RB did a bad job. It even >> detected that SequenceableCollection>>readStream should not be >> changed >> to avoid infinite recursion. >> >> Do you think there is a problem that I might take care of? > > Now as a group how do we want to handle this case? > We give a try and trust damien? > > Stef > > >> >> >> >> -- >> 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 >> > > > _______________________________________________ > 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 5, 2008

Re: [Pharo-project] HowToContribute wiki page rewrite

by Victor Rodriguez

On Wed, Jun 4, 2008 at 3:20 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi victor > If you can, do it but > pay attention that we will certainly use pier or cmsbox at the end. (I know > that the current wiki is slow). I think it is worth to do it, since there doesn't appear to be a firm idea on when a Pier or Cmsbox site will be ready. Project owners, *please* add me to the project! > If you do it can you mark each page of the old one with a link to the new > one. Not a problem. Su servidor, VÃctor RodrÃguez. > Stef > On Jun 4, 2008, at 7:58 PM, Victor Rodriguez wrote: > >> On Wed, Jun 4, 2008 at 1:39 PM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >>> >>> Thanks so may be we should move the wiki contents to this one >>> but more importantly the tasks. >> >> I'll volunteer to move the wiki pages, as long as people don't mind if >> it takes the rest of the week to do it (I can only manage a few hours >> per week of "free time" :-P ). >> >> Victor. >> >> ps. Please add me to the project as victorr(a)gmail.com. >> >>> stef >>> >>> On Jun 4, 2008, at 7:36 PM, Damien Cassou wrote: >>> >>>> On Wed, Jun 4, 2008 at 7:08 PM, Damien Cassou <damien.cassou(a)gmail.com> >>>> wrote: >>>>> >>>>> On Wed, Jun 4, 2008 at 7:01 PM, StÃ©phane Ducasse >>>>> <stephane.ducasse(a)inria.fr> wrote: >>>>>>> >>>>>>> I think Lukas mention sometimes ago to use Google code, much cleaner >>>>>>> interface than this one, the wiki seems also much simpler >>>>>>> and there is a simple bug tracker integrated. >>>>>> >>>>>> Yes may be we should use the Googlecode tracker. >>>>>> Cna someone give a try. >>>>> >>>> >>>> http://code.google.com/p/pharo/. It seems very cool and simple. >>>> >>>> >>>> >>>> >>>> -- >>>> 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 >>>> >>> >>> >>> _______________________________________________ >>> 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 5, 2008

Re: [Pharo-project] About readStream on: vs readStream

by Bill Schwab

Stef, FWIW, I consider it to be negotiable, provided we can use ReadStream as a factory/facade for Nile classes. With some double-dispatch, I think we could end up with something similar to directories: code references the generic class and the system instantiates platform-specific subclasses. In Nile, ReadStream on:aStream would answer a Nile read stream for the relevant collection species. That said, #readStream is a preferable idiom to #on:. My leaning would be to keep the latter and strongly encourage use of the former. 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 >>> stephane.ducasse(a)inria.fr 6/4/2008 1:36 PM >>> Hi damien I was wondering why you think that ReadStream on: anObject is worse than anObject readStream? Because you do not hardcode ReadStream? Stef _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 4, 2008

Re: [Pharo-project] About on:

by Bill Schwab

Stef, Damien, No surprise, I would argue that we proceed, and would also include a rename of #next to #nextOrNil and #next: to #nextAvailable:. All code in the image at the time should work as before. The next step (part B) would be to add exception-aware #next and #next:. Damien and I could cook it up, try it, and then return with an "all clear." 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 >>> stephane.ducasse(a)inria.fr 6/4/2008 10:36 AM >>> On Jun 4, 2008, at 5:20 PM, Damien Cassou wrote: > On Wed, Jun 4, 2008 at 1:45 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> here is what I propose for on: >> I will move your package out of the inbox so that the discussion >> can go on >> and >> I try to integrate all the other changes. >> Then with bill and others you propose how to proceed. >> Is it ok ? > > What do you mean by 'I will move your package out of the inbox'? Do > you mean you simply delete the packages or you moved them to Pharo? I mean move them to the treatedBox without putting in the image > Replacing 'ReadStream on: smth' by 'smth readStream' is not mandatory. > However, it makes the code simpler to read, avoids a direct class > reference and allows different implementation of #readStream depending > on the kind of collection it is sent to. I do not think anyone is > against that as soon as I apply the automatic refactoring carefully. I > did that and didn't see any place where the RB did a bad job. It even > detected that SequenceableCollection>>readStream should not be changed > to avoid infinite recursion. > > Do you think there is a problem that I might take care of? Now as a group how do we want to handle this case? We give a try and trust damien? Stef > > > > -- > 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 > _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 4, 2008

[Pharo-project] 2 new updates

by StÃ©phane Ducasse

Hi guys I harvested some fixes proposed: - file test cleaning - number parsing tests - nebraska cleaning I cleaned up the inbox. Tomorrow I will try to take a look at MVC step 1 :) Stef

June 4, 2008

Re: [Pharo-project] HowToContribute wiki page rewrite

by StÃ©phane Ducasse

Hi victor If you can, do it but pay attention that we will certainly use pier or cmsbox at the end. (I know that the current wiki is slow). If you do it can you mark each page of the old one with a link to the new one. Stef On Jun 4, 2008, at 7:58 PM, Victor Rodriguez wrote: > On Wed, Jun 4, 2008 at 1:39 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Thanks so may be we should move the wiki contents to this one >> but more importantly the tasks. > > I'll volunteer to move the wiki pages, as long as people don't mind if > it takes the rest of the week to do it (I can only manage a few hours > per week of "free time" :-P ). > > Victor. > > ps. Please add me to the project as victorr(a)gmail.com. > >> stef >> >> On Jun 4, 2008, at 7:36 PM, Damien Cassou wrote: >> >>> On Wed, Jun 4, 2008 at 7:08 PM, Damien Cassou <damien.cassou(a)gmail.com >>> > >>> wrote: >>>> >>>> On Wed, Jun 4, 2008 at 7:01 PM, StÃ©phane Ducasse >>>> <stephane.ducasse(a)inria.fr> wrote: >>>>>> >>>>>> I think Lukas mention sometimes ago to use Google code, much >>>>>> cleaner >>>>>> interface than this one, the wiki seems also much simpler >>>>>> and there is a simple bug tracker integrated. >>>>> >>>>> Yes may be we should use the Googlecode tracker. >>>>> Cna someone give a try. >>>> >>> >>> http://code.google.com/p/pharo/. It seems very cool and simple. >>> >>> >>> >>> >>> -- >>> 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 >>> >> >> >> _______________________________________________ >> 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 4, 2008

[Pharo-project] About readStream on: vs readStream

by StÃ©phane Ducasse

Hi damien I was wondering why you think that ReadStream on: anObject is worse than anObject readStream? Because you do not hardcode ReadStream? Stef

June 4, 2008

Re: [Pharo-project] HowToContribute wiki page rewrite

by Serge Stinckwich

How could i edit the main page ? 2008/6/4 Damien Cassou <damien.cassou(a)gmail.com>: > On Wed, Jun 4, 2008 at 7:08 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: >> On Wed, Jun 4, 2008 at 7:01 PM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >>>> I think Lukas mention sometimes ago to use Google code, much cleaner >>>> interface than this one, the wiki seems also much simpler >>>> and there is a simple bug tracker integrated. >>> >>> Yes may be we should use the Googlecode tracker. >>> Cna someone give a try. >> > > http://code.google.com/p/pharo/. It seems very cool and simple. > > > > > -- > 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 > -- Serge Stinckwich http://blog.doesnotunderstand.org/

June 4, 2008

Re: [Pharo-project] HowToContribute wiki page rewrite

by Victor Rodriguez

On Wed, Jun 4, 2008 at 1:39 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Thanks so may be we should move the wiki contents to this one > but more importantly the tasks. I'll volunteer to move the wiki pages, as long as people don't mind if it takes the rest of the week to do it (I can only manage a few hours per week of "free time" :-P ). Victor. ps. Please add me to the project as victorr(a)gmail.com. > stef > > On Jun 4, 2008, at 7:36 PM, Damien Cassou wrote: > >> On Wed, Jun 4, 2008 at 7:08 PM, Damien Cassou <damien.cassou(a)gmail.com> >> wrote: >>> >>> On Wed, Jun 4, 2008 at 7:01 PM, StÃ©phane Ducasse >>> <stephane.ducasse(a)inria.fr> wrote: >>>>> >>>>> I think Lukas mention sometimes ago to use Google code, much cleaner >>>>> interface than this one, the wiki seems also much simpler >>>>> and there is a simple bug tracker integrated. >>>> >>>> Yes may be we should use the Googlecode tracker. >>>> Cna someone give a try. >>> >> >> http://code.google.com/p/pharo/. It seems very cool and simple. >> >> >> >> >> -- >> 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 >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 4, 2008

Re: [Pharo-project] HowToContribute wiki page rewrite

by StÃ©phane Ducasse

Thanks so may be we should move the wiki contents to this one but more importantly the tasks. stef On Jun 4, 2008, at 7:36 PM, Damien Cassou wrote: > On Wed, Jun 4, 2008 at 7:08 PM, Damien Cassou > <damien.cassou(a)gmail.com> wrote: >> On Wed, Jun 4, 2008 at 7:01 PM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >>>> I think Lukas mention sometimes ago to use Google code, much >>>> cleaner >>>> interface than this one, the wiki seems also much simpler >>>> and there is a simple bug tracker integrated. >>> >>> Yes may be we should use the Googlecode tracker. >>> Cna someone give a try. >> > > http://code.google.com/p/pharo/. It seems very cool and simple. > > > > > -- > 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 4, 2008

Re: [Pharo-project] HowToContribute wiki page rewrite

by Damien Cassou

On Wed, Jun 4, 2008 at 7:08 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > On Wed, Jun 4, 2008 at 7:01 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >>> I think Lukas mention sometimes ago to use Google code, much cleaner >>> interface than this one, the wiki seems also much simpler >>> and there is a simple bug tracker integrated. >> >> Yes may be we should use the Googlecode tracker. >> Cna someone give a try. > http://code.google.com/p/pharo/. It seems very cool and simple. -- 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 4, 2008

Re: [Pharo-project] HowToContribute wiki page rewrite

by Damien Cassou

On Wed, Jun 4, 2008 at 7:01 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> I think Lukas mention sometimes ago to use Google code, much cleaner >> interface than this one, the wiki seems also much simpler >> and there is a simple bug tracker integrated. > > Yes may be we should use the Googlecode tracker. > Cna someone give a try. I'm having a look. -- 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 4, 2008

Re: [Pharo-project] HowToContribute wiki page rewrite

by StÃ©phane Ducasse

> I think Lukas mention sometimes ago to use Google code, much cleaner > interface than this one, the wiki seems also much simpler > and there is a simple bug tracker integrated. Yes may be we should use the Googlecode tracker. Cna someone give a try. Stef > > Look for example the SyX project : > http://code.google.com/p/syx/ > and his wiki : http://code.google.com/p/syx/w/list > > -- > Serge Stinckwich > http://blog.doesnotunderstand.org/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 4, 2008

Re: [Pharo-project] About on:

by StÃ©phane Ducasse

On Jun 4, 2008, at 5:20 PM, Damien Cassou wrote: > On Wed, Jun 4, 2008 at 1:45 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> here is what I propose for on: >> I will move your package out of the inbox so that the discussion >> can go on >> and >> I try to integrate all the other changes. >> Then with bill and others you propose how to proceed. >> Is it ok ? > > What do you mean by 'I will move your package out of the inbox'? Do > you mean you simply delete the packages or you moved them to Pharo? I mean move them to the treatedBox without putting in the image > Replacing 'ReadStream on: smth' by 'smth readStream' is not mandatory. > However, it makes the code simpler to read, avoids a direct class > reference and allows different implementation of #readStream depending > on the kind of collection it is sent to. I do not think anyone is > against that as soon as I apply the automatic refactoring carefully. I > did that and didn't see any place where the RB did a bad job. It even > detected that SequenceableCollection>>readStream should not be changed > to avoid infinite recursion. > > Do you think there is a problem that I might take care of? Now as a group how do we want to handle this case? We give a try and trust damien? Stef > > > > -- > 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 4, 2008

Re: [Pharo-project] About on:

by Damien Cassou

On Wed, Jun 4, 2008 at 1:45 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > here is what I propose for on: > I will move your package out of the inbox so that the discussion can go on > and > I try to integrate all the other changes. > Then with bill and others you propose how to proceed. > Is it ok ? What do you mean by 'I will move your package out of the inbox'? Do you mean you simply delete the packages or you moved them to Pharo? Replacing 'ReadStream on: smth' by 'smth readStream' is not mandatory. However, it makes the code simpler to read, avoids a direct class reference and allows different implementation of #readStream depending on the kind of collection it is sent to. I do not think anyone is against that as soon as I apply the automatic refactoring carefully. I did that and didn't see any place where the RB did a bad job. It even detected that SequenceableCollection>>readStream should not be changed to avoid infinite recursion. Do you think there is a problem that I might take care of? -- 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 4, 2008

Re: [Pharo-project] why removing testhex?

by StÃ©phane Ducasse

I will have to check. I'm in a meeting right now. ;) Stef On Jun 4, 2008, at 3:06 PM, Serge Stinckwich wrote: > Hum be explicit, when you are talking a package version. > This one : GraphicsTests-SergeStinckwich.11.mcz ? > > I didn't found a removal ... but if there is one, i guest it's a > mistake. > I never remove a test ;-) > > 2008/6/4 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> in the package you publish about html color >> >> >> >>> Hi serge >>> >>> why did you remove testHex? >>> >>> BTW I did not receive your nice license agreement >>> _______________________________________________ >>> 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 >> > > > > -- > Serge Stinckwich > http://blog.doesnotunderstand.org/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 4, 2008

Re: [Pharo-project] why removing testhex?

by Serge Stinckwich

Hum be explicit, when you are talking a package version. This one : GraphicsTests-SergeStinckwich.11.mcz ? I didn't found a removal ... but if there is one, i guest it's a mistake. I never remove a test ;-) 2008/6/4 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > in the package you publish about html color > > > >> Hi serge >> >> why did you remove testHex? >> >> BTW I did not receive your nice license agreement >> _______________________________________________ >> 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 > -- Serge Stinckwich http://blog.doesnotunderstand.org/

June 4, 2008

Re: [Pharo-project] HowToContribute wiki page rewrite

by Serge Stinckwich

2008/6/4 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > > On Jun 4, 2008, at 5:51 AM, Victor Rodriguez wrote: > >> Hello, >> >> I took the liberty of rewriting the HowToContribute wiki page [1] with >> some of the information from the recent discussion in the mailing >> list. > > Excellent! > > >> Please take a look at the wiki page (I have also reproduced the text >> below) and feel free to make corrections yourself (or post a reply to >> this message and I'll take care of it). >> >> Please take special care reviewing the "publish to PharoInbox" step, >> since I have yet to publish anything myself so I might have gotten it >> wrong. >> >> Best regards, >> >> VÃctor RodrÃguez. >> >> p.s. I got to watch two "Smalltalk daily" [2] screencasts while >> waiting for the edited page to save.. any timetable on the nifty Pier >> or Cmsbox Pharo project site? :-) > > Yes terrible and ugly wiki. We are waiting for a nice logo and graphical > chart > and after that we will mirgate to a much better wiki. I think Lukas mention sometimes ago to use Google code, much cleaner interface than this one, the wiki seems also much simpler and there is a simple bug tracker integrated. Look for example the SyX project : http://code.google.com/p/syx/ and his wiki : http://code.google.com/p/syx/w/list -- Serge Stinckwich http://blog.doesnotunderstand.org/

June 4, 2008

Re: [Pharo-project] why removing testhex?

by StÃ©phane Ducasse

in the package you publish about html color > Hi serge > > why did you remove testHex? > > BTW I did not receive your nice license agreement > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 4, 2008

Re: [Pharo-project] HowToContribute wiki page rewrite

by StÃ©phane Ducasse

On Jun 4, 2008, at 5:51 AM, Victor Rodriguez wrote: > Hello, > > I took the liberty of rewriting the HowToContribute wiki page [1] with > some of the information from the recent discussion in the mailing > list. Excellent! > Please take a look at the wiki page (I have also reproduced the text > below) and feel free to make corrections yourself (or post a reply to > this message and I'll take care of it). > > Please take special care reviewing the "publish to PharoInbox" step, > since I have yet to publish anything myself so I might have gotten it > wrong. > > Best regards, > > VÃctor RodrÃguez. > > p.s. I got to watch two "Smalltalk daily" [2] screencasts while > waiting for the edited page to save.. any timetable on the nifty Pier > or Cmsbox Pharo project site? :-) Yes terrible and ugly wiki. We are waiting for a nice logo and graphical chart and after that we will mirgate to a much better wiki. > > [1] http://gforge.inria.fr/plugins/wiki/index.php?id=1299&type=g > [2] http://www.cincomsmalltalk.com/blog/blogView?searchCategory=screencast > > First and foremost, you must be aware that '''the Pharo project only > accepts code published under the MIT license'''. By publishing your > code in the !SqueakSource Pharo or !PharoInbox repositories, you are > agreeing to this condition. > > With that out of the way, here are the steps to submit your > contributions: > > * Prepare a changeset with your changes. File it out. > '''Important''': Put your Full name instead of your initials, it will > help up to contact you as it is often necessary. > > * Load your changes into a fresh image: > > ** Download the latest Pharo image from [Files | > http://gforge.inria.fr/frs/?group_id=1299] > > ** Launch the fresh image and load the latest updates by clicking on > the ''load code updates'' button on the left flap. > > ** Importat: Save the image at this point, so that you don't need to > reload the updates when you test your changes. > > ** File in your changeset. > > * Create a SLICE package in your package cache: > > ** Open the Monticello browser. You should see one or more packages > marked as modified (they have an asterisk before their name). > > ** Select your package-cache repository on the right hand pane. > > ** Create the new package (click on the ''+Package'' button). Name it > SLICE-nameofchange, (e.g. SLICE-remove-isMorphic). > > ** Make all the modified packages (the ones with asterisks before > their names) required by your SLICE package. To do this, right click > on the SLICE package in the left pane and select ''add required > package'', then select the package from the next menu. Repeat for all > modified packages. > > ** Save the SLICE package (click on the ''Save'' button). An mcz > package will be saved in your cache for the SLICE package and all the > modified packages. You will be prompted for a log message for each > one of them, type a useful comment for the first package, copy it and > paste it on the others. > > ** To prepare for the next step, quit the image without saving. > > * Test your packages in the clean image. > > ** Relaunch the clean Pharo image. If you didn't save the image after > loading the updates, load the updates (I told you it was important!). > > ** Open the Monticello browser. > > ** Open your package-cache repository (select the package-cache in the > right pane, click on the ''Open'' button). > > ** Load your SLICE package. If it loads without errors, you are ready > for the next step. If there are errors, try again, or ask for help in > the mailing list. > > * Publish the SLICE package to !PharoInbox !SqueakSource repository. > > ** In the Monticello browser add the !PharoInbox repository. Make > sure the SLICE package is selected in the left pane, then click on the > ''+Repository''. Select ''HTTP'' from the menu, then make sure that > the location reads ''http://www.squeaksource.com/PharoInbox''. > > ** Finally, click on ''Save''. > > * Announce your contribution. > > ** You might need to add an entry to the [tracker | > http://gforge.inria.fr/tracker/?group_id=1299] to MantisBugsHarvested > in the wiki, etc. > > ** Send a email to the mailing list. > > Congratulations, the world is one step closer to being a better place! > > We greately appreciate your effort. > > In case of problems, you can send a changeset to the mailing list, but > please only do this as a last resort. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 4, 2008

Re: [Pharo-project] EToys

by StÃ©phane Ducasse

Sorry :) We should not even try to reload etoy. Stef On Jun 3, 2008, at 6:06 PM, Gary Chambers wrote: > :-) > > I think he meant #2. > > I hope so... but then, not quite a reload, but a patch package could > be done > for the stuff not included in the EToys package. At least then, > technically, > EToys would be modular. Though it would be likely to hamper further > streamlining. > > Regards, Gary. > >> -----Original Message----- >> From: pharo-project-bounces(a)lists.gforge.inria.fr >> [mailto:pharo-project-bounces@lists.gforge.inria.fr]On Behalf Of >> Damien >> Cassou >> Sent: 03 June 2008 4:51 PM >> To: An open mailing list to discuss any topics related to an >> open-sourceSmalltalk >> Subject: Re: [Pharo-project] EToys >> >> >> On Tue, Jun 3, 2008 at 5:47 PM, Damien Cassou >> <damien.cassou(a)gmail.com> wrote: >>> On Tue, Jun 3, 2008 at 5:39 PM, Gary Chambers >> <gazzaguru2(a)btinternet.com> wrote: >>>> Damien, >>>> >>>> I don't, particularly! Just wondering what the approach is >> here... quite >>>> happy to rip it out altogether (might get a bit zealous with >> it!). Early >>>> indications are that around 200 methods can be dropped from >> Morph alone! >>>> >>>> Will wait for the inbox to settle first before applying my >> investigations to >>>> Pahro though. >>> >>> I was asking the question to StÃ©phane who said: >>> >>> "No reload of Etoy (as its current state) is important else it will >>> reintroduce cruft" >> >> Now that I read again the sentence, I think it can have 2 >> different meanings: >> >> "No ! reload of etoy is important !" >> >> or >> >> "reload of etoy is not important" >> >> Which one is correct? Knowing Stef, I would vote for 2 but I >> thought he meant 1. >> >> >> >> -- >> 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 4, 2008

Re: [Pharo-project] EToys

by StÃ©phane Ducasse

I went over some changes and I plan to move in treated - the dockproject clean of alex because this is not that clean - on: fix of damien On Jun 3, 2008, at 5:39 PM, Gary Chambers wrote: > Damien, > > I don't, particularly! Just wondering what the approach is here... > quite > happy to rip it out altogether (might get a bit zealous with it!). > Early > indications are that around 200 methods can be dropped from Morph > alone! > > Will wait for the inbox to settle first before applying my > investigations to > Pahro though. > > Regards, Gary. > >> -----Original Message----- >> From: pharo-project-bounces(a)lists.gforge.inria.fr >> [mailto:pharo-project-bounces@lists.gforge.inria.fr]On Behalf Of >> Damien >> Cassou >> Sent: 03 June 2008 4:29 PM >> To: An open mailing list to discuss any topics related to an >> open-sourceSmalltalk >> Subject: Re: [Pharo-project] EToys >> >> >> On Mon, Jun 2, 2008 at 4:24 PM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >>> No reload of Etoy (as its current state) is important else it will >>> reintroduce >>> cruft. >> >> Why do you want to be able to reload Etoys? >> >> -- >> 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 4, 2008

[Pharo-project] About on:

by StÃ©phane Ducasse

> From: pharo-project-owner(a)lists.gforge.inria.fr > Date: June 3, 2008 6:43:05 AM CEDT > To: ducasse(a)iam.unibe.ch > Subject: About on: > > You are not allowed to post to this mailing list, and your message has > been automatically rejected. If you think that your messages are > being rejected in error, contact the mailing list owner at > pharo-project-owner(a)lists.gforge.inria.fr. > > > From: stÃ©phane ducasse <ducasse(a)iam.unibe.ch> > Date: June 3, 2008 6:42:33 AM CEDT > To: An open mailing list to discuss any topics related to an open- > source Smalltalk <Pharo-project(a)lists.gforge.inria.fr> > Subject: About on: > > > Hi damien > > here is what I propose for on: > I will move your package out of the inbox so that the discussion can > go on and > I try to integrate all the other changes. > Then with bill and others you propose how to proceed. > Is it ok ? > > Stef > > >

June 4, 2008

Re: [Pharo-project] why removing testhex?

by Serge Stinckwich

2008/6/3 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > Hi serge > > why did you remove testHex? I don't remember removing this one ... In which package ? There is no testHex in the last Pharo release. > BTW I did not receive your nice license agreement Maybe i could sign something at RMLL'08 ? Cheers, -- Serge Stinckwich http://blog.doesnotunderstand.org/

June 4, 2008

Re: [Pharo-project] HowToContribute wiki page rewrite

by Serge Stinckwich

Thank you Victor for your contributions. I think you have to create a SLICE package only if your modifications impact severals packages. 2008/6/4 Victor Rodriguez <victorr(a)gmail.com>: > Hello, > > I took the liberty of rewriting the HowToContribute wiki page [1] with > some of the information from the recent discussion in the mailing > list. > > Please take a look at the wiki page (I have also reproduced the text > below) and feel free to make corrections yourself (or post a reply to > this message and I'll take care of it). > > Please take special care reviewing the "publish to PharoInbox" step, > since I have yet to publish anything myself so I might have gotten it > wrong. > > Best regards, > > VÃctor RodrÃguez. > > p.s. I got to watch two "Smalltalk daily" [2] screencasts while > waiting for the edited page to save.. any timetable on the nifty Pier > or Cmsbox Pharo project site? :-) > > [1] http://gforge.inria.fr/plugins/wiki/index.php?id=1299&type=g > [2] http://www.cincomsmalltalk.com/blog/blogView?searchCategory=screencast > > First and foremost, you must be aware that '''the Pharo project only > accepts code published under the MIT license'''. By publishing your > code in the !SqueakSource Pharo or !PharoInbox repositories, you are > agreeing to this condition. > > With that out of the way, here are the steps to submit your contributions: > > * Prepare a changeset with your changes. File it out. > '''Important''': Put your Full name instead of your initials, it will > help up to contact you as it is often necessary. > > * Load your changes into a fresh image: > > ** Download the latest Pharo image from [Files | > http://gforge.inria.fr/frs/?group_id=1299] > > ** Launch the fresh image and load the latest updates by clicking on > the ''load code updates'' button on the left flap. > > ** Importat: Save the image at this point, so that you don't need to > reload the updates when you test your changes. > > ** File in your changeset. > > * Create a SLICE package in your package cache: > > ** Open the Monticello browser. You should see one or more packages > marked as modified (they have an asterisk before their name). > > ** Select your package-cache repository on the right hand pane. > > ** Create the new package (click on the ''+Package'' button). Name it > SLICE-nameofchange, (e.g. SLICE-remove-isMorphic). > > ** Make all the modified packages (the ones with asterisks before > their names) required by your SLICE package. To do this, right click > on the SLICE package in the left pane and select ''add required > package'', then select the package from the next menu. Repeat for all > modified packages. > > ** Save the SLICE package (click on the ''Save'' button). An mcz > package will be saved in your cache for the SLICE package and all the > modified packages. You will be prompted for a log message for each > one of them, type a useful comment for the first package, copy it and > paste it on the others. > > ** To prepare for the next step, quit the image without saving. > > * Test your packages in the clean image. > > ** Relaunch the clean Pharo image. If you didn't save the image after > loading the updates, load the updates (I told you it was important!). > > ** Open the Monticello browser. > > ** Open your package-cache repository (select the package-cache in the > right pane, click on the ''Open'' button). > > ** Load your SLICE package. If it loads without errors, you are ready > for the next step. If there are errors, try again, or ask for help in > the mailing list. > > * Publish the SLICE package to !PharoInbox !SqueakSource repository. > > ** In the Monticello browser add the !PharoInbox repository. Make > sure the SLICE package is selected in the left pane, then click on the > ''+Repository''. Select ''HTTP'' from the menu, then make sure that > the location reads ''http://www.squeaksource.com/PharoInbox''. > > ** Finally, click on ''Save''. > > * Announce your contribution. > > ** You might need to add an entry to the [tracker | > http://gforge.inria.fr/tracker/?group_id=1299] to MantisBugsHarvested > in the wiki, etc. > > ** Send a email to the mailing list. > > Congratulations, the world is one step closer to being a better place! > > We greately appreciate your effort. > > In case of problems, you can send a changeset to the mailing list, but > please only do this as a last resort. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Serge Stinckwich http://blog.doesnotunderstand.org/

June 4, 2008

Re: [Pharo-project] EToys

by Serge Stinckwich

2008/6/3 Bill Schwab <BSchwab(a)anest.ufl.edu>: > My hunch is that Stef is against loading it in its current state. Any well-factored and optional package should be welcome. I am thrilled to see Gary on board! No, this is not a problem of someone who don't like EToys. EToys add an enormous layer of complexity in Morphic and Squeak everywhere. No one here got the energy and competences do remove safely EToys. If we want to refactor massively Squeak, we have to cut the EToys crud. After that, the EToys guys could propose a Pharo package in order to reintroduce EToys. -- Serge Stinckwich http://blog.doesnotunderstand.org/

June 4, 2008

Re: [Pharo-project] HowToContribute wiki page rewrite

by Alexandre Bergel

I like it. Someone put your version online already. thanks for this, Alexandre On 4 Jun 2008, at 05:51, Victor Rodriguez wrote: > Hello, > > I took the liberty of rewriting the HowToContribute wiki page [1] with > some of the information from the recent discussion in the mailing > list. > > Please take a look at the wiki page (I have also reproduced the text > below) and feel free to make corrections yourself (or post a reply to > this message and I'll take care of it). > > Please take special care reviewing the "publish to PharoInbox" step, > since I have yet to publish anything myself so I might have gotten it > wrong. > > Best regards, > > VÃctor RodrÃguez. > > p.s. I got to watch two "Smalltalk daily" [2] screencasts while > waiting for the edited page to save.. any timetable on the nifty Pier > or Cmsbox Pharo project site? :-) > > [1] http://gforge.inria.fr/plugins/wiki/index.php?id=1299&type=g > [2] http://www.cincomsmalltalk.com/blog/blogView?searchCategory=screencast > > First and foremost, you must be aware that '''the Pharo project only > accepts code published under the MIT license'''. By publishing your > code in the !SqueakSource Pharo or !PharoInbox repositories, you are > agreeing to this condition. > > With that out of the way, here are the steps to submit your > contributions: > > * Prepare a changeset with your changes. File it out. > '''Important''': Put your Full name instead of your initials, it will > help up to contact you as it is often necessary. > > * Load your changes into a fresh image: > > ** Download the latest Pharo image from [Files | > http://gforge.inria.fr/frs/?group_id=1299] > > ** Launch the fresh image and load the latest updates by clicking on > the ''load code updates'' button on the left flap. > > ** Importat: Save the image at this point, so that you don't need to > reload the updates when you test your changes. > > ** File in your changeset. > > * Create a SLICE package in your package cache: > > ** Open the Monticello browser. You should see one or more packages > marked as modified (they have an asterisk before their name). > > ** Select your package-cache repository on the right hand pane. > > ** Create the new package (click on the ''+Package'' button). Name it > SLICE-nameofchange, (e.g. SLICE-remove-isMorphic). > > ** Make all the modified packages (the ones with asterisks before > their names) required by your SLICE package. To do this, right click > on the SLICE package in the left pane and select ''add required > package'', then select the package from the next menu. Repeat for all > modified packages. > > ** Save the SLICE package (click on the ''Save'' button). An mcz > package will be saved in your cache for the SLICE package and all the > modified packages. You will be prompted for a log message for each > one of them, type a useful comment for the first package, copy it and > paste it on the others. > > ** To prepare for the next step, quit the image without saving. > > * Test your packages in the clean image. > > ** Relaunch the clean Pharo image. If you didn't save the image after > loading the updates, load the updates (I told you it was important!). > > ** Open the Monticello browser. > > ** Open your package-cache repository (select the package-cache in the > right pane, click on the ''Open'' button). > > ** Load your SLICE package. If it loads without errors, you are ready > for the next step. If there are errors, try again, or ask for help in > the mailing list. > > * Publish the SLICE package to !PharoInbox !SqueakSource repository. > > ** In the Monticello browser add the !PharoInbox repository. Make > sure the SLICE package is selected in the left pane, then click on the > ''+Repository''. Select ''HTTP'' from the menu, then make sure that > the location reads ''http://www.squeaksource.com/PharoInbox''. > > ** Finally, click on ''Save''. > > * Announce your contribution. > > ** You might need to add an entry to the [tracker | > http://gforge.inria.fr/tracker/?group_id=1299] to MantisBugsHarvested > in the wiki, etc. > > ** Send a email to the mailing list. > > Congratulations, the world is one step closer to being a better place! > > We greately appreciate your effort. > > In case of problems, you can send a changeset to the mailing list, but > please only do this as a last resort. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

June 4, 2008

[Pharo-project] HowToContribute wiki page rewrite

by Victor Rodriguez

Hello, I took the liberty of rewriting the HowToContribute wiki page [1] with some of the information from the recent discussion in the mailing list. Please take a look at the wiki page (I have also reproduced the text below) and feel free to make corrections yourself (or post a reply to this message and I'll take care of it). Please take special care reviewing the "publish to PharoInbox" step, since I have yet to publish anything myself so I might have gotten it wrong. Best regards, VÃctor RodrÃguez. p.s. I got to watch two "Smalltalk daily" [2] screencasts while waiting for the edited page to save.. any timetable on the nifty Pier or Cmsbox Pharo project site? :-) [1] http://gforge.inria.fr/plugins/wiki/index.php?id=1299&type=g [2] http://www.cincomsmalltalk.com/blog/blogView?searchCategory=screencast First and foremost, you must be aware that '''the Pharo project only accepts code published under the MIT license'''. By publishing your code in the !SqueakSource Pharo or !PharoInbox repositories, you are agreeing to this condition. With that out of the way, here are the steps to submit your contributions: * Prepare a changeset with your changes. File it out. '''Important''': Put your Full name instead of your initials, it will help up to contact you as it is often necessary. * Load your changes into a fresh image: ** Download the latest Pharo image from [Files | http://gforge.inria.fr/frs/?group_id=1299] ** Launch the fresh image and load the latest updates by clicking on the ''load code updates'' button on the left flap. ** Importat: Save the image at this point, so that you don't need to reload the updates when you test your changes. ** File in your changeset. * Create a SLICE package in your package cache: ** Open the Monticello browser. You should see one or more packages marked as modified (they have an asterisk before their name). ** Select your package-cache repository on the right hand pane. ** Create the new package (click on the ''+Package'' button). Name it SLICE-nameofchange, (e.g. SLICE-remove-isMorphic). ** Make all the modified packages (the ones with asterisks before their names) required by your SLICE package. To do this, right click on the SLICE package in the left pane and select ''add required package'', then select the package from the next menu. Repeat for all modified packages. ** Save the SLICE package (click on the ''Save'' button). An mcz package will be saved in your cache for the SLICE package and all the modified packages. You will be prompted for a log message for each one of them, type a useful comment for the first package, copy it and paste it on the others. ** To prepare for the next step, quit the image without saving. * Test your packages in the clean image. ** Relaunch the clean Pharo image. If you didn't save the image after loading the updates, load the updates (I told you it was important!). ** Open the Monticello browser. ** Open your package-cache repository (select the package-cache in the right pane, click on the ''Open'' button). ** Load your SLICE package. If it loads without errors, you are ready for the next step. If there are errors, try again, or ask for help in the mailing list. * Publish the SLICE package to !PharoInbox !SqueakSource repository. ** In the Monticello browser add the !PharoInbox repository. Make sure the SLICE package is selected in the left pane, then click on the ''+Repository''. Select ''HTTP'' from the menu, then make sure that the location reads ''http://www.squeaksource.com/PharoInbox''. ** Finally, click on ''Save''. * Announce your contribution. ** You might need to add an entry to the [tracker | http://gforge.inria.fr/tracker/?group_id=1299] to MantisBugsHarvested in the wiki, etc. ** Send a email to the mailing list. Congratulations, the world is one step closer to being a better place! We greately appreciate your effort. In case of problems, you can send a changeset to the mailing list, but please only do this as a last resort.

June 4, 2008

Re: [Pharo-project] EToys

by Bill Schwab

My hunch is that Stef is against loading it in its current state. Any well-factored and optional package should be welcome. I am thrilled to see Gary on board! 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 >>> damien.cassou(a)gmail.com 6/3/2008 10:50 AM >>> On Tue, Jun 3, 2008 at 5:47 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > On Tue, Jun 3, 2008 at 5:39 PM, Gary Chambers <gazzaguru2(a)btinternet.com> wrote: >> Damien, >> >> I don't, particularly! Just wondering what the approach is here... quite >> happy to rip it out altogether (might get a bit zealous with it!). Early >> indications are that around 200 methods can be dropped from Morph alone! >> >> Will wait for the inbox to settle first before applying my investigations to >> Pahro though. > > I was asking the question to StÃ©phane who said: > > "No reload of Etoy (as its current state) is important else it will > reintroduce cruft" Now that I read again the sentence, I think it can have 2 different meanings: "No ! reload of etoy is important !" or "reload of etoy is not important" Which one is correct? Knowing Stef, I would vote for 2 but I thought he meant 1. -- 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 3, 2008

Re: [Pharo-project] Tools-AlexandreBergel.83 adds a dependency to OmniBrowser

by Alexandre Bergel

You're right Damien. Maybe the test should be an override of OB. But the test breaks if OB is loaded, and is green without OB. The class may be moved to the OB package... Alexandre On 3 Jun 2008, at 12:37, Damien Cassou wrote: > There is a reference to OB specific classes in > Tools-AlexandreBergel.83. OB must not be part of pharo in my opinion. > > -- > 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 > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

June 3, 2008

Re: [Pharo-project] EToys

by Michael Rueger

Gary Chambers wrote: > :-) > > I think he meant #2. > > I hope so... but then, not quite a reload, but a patch package could be done > for the stuff not included in the EToys package. At least then, technically, > EToys would be modular. Though it would be likely to hamper further > streamlining. as most surely know I'm a big supporter of etoys. But, etoys has forked based on the 3.8 image a long time ago and it would be non-trivial to merge the current state back into a 3.9 or 3.10 image anyways. Michael

June 3, 2008

RE: [Pharo-project] EToys

by Gary Chambers

:-) I think he meant #2. I hope so... but then, not quite a reload, but a patch package could be done for the stuff not included in the EToys package. At least then, technically, EToys would be modular. Though it would be likely to hamper further streamlining. Regards, Gary. > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr > [mailto:pharo-project-bounces@lists.gforge.inria.fr]On Behalf Of Damien > Cassou > Sent: 03 June 2008 4:51 PM > To: An open mailing list to discuss any topics related to an > open-sourceSmalltalk > Subject: Re: [Pharo-project] EToys > > > On Tue, Jun 3, 2008 at 5:47 PM, Damien Cassou > <damien.cassou(a)gmail.com> wrote: > > On Tue, Jun 3, 2008 at 5:39 PM, Gary Chambers > <gazzaguru2(a)btinternet.com> wrote: > >> Damien, > >> > >> I don't, particularly! Just wondering what the approach is > here... quite > >> happy to rip it out altogether (might get a bit zealous with > it!). Early > >> indications are that around 200 methods can be dropped from > Morph alone! > >> > >> Will wait for the inbox to settle first before applying my > investigations to > >> Pahro though. > > > > I was asking the question to StÃ©phane who said: > > > > "No reload of Etoy (as its current state) is important else it will > > reintroduce cruft" > > Now that I read again the sentence, I think it can have 2 > different meanings: > > "No ! reload of etoy is important !" > > or > > "reload of etoy is not important" > > Which one is correct? Knowing Stef, I would vote for 2 but I > thought he meant 1. > > > > -- > 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 3, 2008

Re: [Pharo-project] EToys

by Damien Cassou

On Tue, Jun 3, 2008 at 5:47 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > On Tue, Jun 3, 2008 at 5:39 PM, Gary Chambers <gazzaguru2(a)btinternet.com> wrote: >> Damien, >> >> I don't, particularly! Just wondering what the approach is here... quite >> happy to rip it out altogether (might get a bit zealous with it!). Early >> indications are that around 200 methods can be dropped from Morph alone! >> >> Will wait for the inbox to settle first before applying my investigations to >> Pahro though. > > I was asking the question to StÃ©phane who said: > > "No reload of Etoy (as its current state) is important else it will > reintroduce cruft" Now that I read again the sentence, I think it can have 2 different meanings: "No ! reload of etoy is important !" or "reload of etoy is not important" Which one is correct? Knowing Stef, I would vote for 2 but I thought he meant 1. -- 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 3, 2008

Re: [Pharo-project] EToys

by Damien Cassou

On Tue, Jun 3, 2008 at 5:39 PM, Gary Chambers <gazzaguru2(a)btinternet.com> wrote: > Damien, > > I don't, particularly! Just wondering what the approach is here... quite > happy to rip it out altogether (might get a bit zealous with it!). Early > indications are that around 200 methods can be dropped from Morph alone! > > Will wait for the inbox to settle first before applying my investigations to > Pahro though. I was asking the question to StÃ©phane who said: "No reload of Etoy (as its current state) is important else it will reintroduce cruft" -- 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 3, 2008

RE: [Pharo-project] EToys

by Gary Chambers

Damien, I don't, particularly! Just wondering what the approach is here... quite happy to rip it out altogether (might get a bit zealous with it!). Early indications are that around 200 methods can be dropped from Morph alone! Will wait for the inbox to settle first before applying my investigations to Pahro though. Regards, Gary. > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr > [mailto:pharo-project-bounces@lists.gforge.inria.fr]On Behalf Of Damien > Cassou > Sent: 03 June 2008 4:29 PM > To: An open mailing list to discuss any topics related to an > open-sourceSmalltalk > Subject: Re: [Pharo-project] EToys > > > On Mon, Jun 2, 2008 at 4:24 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: > > No reload of Etoy (as its current state) is important else it will > > reintroduce > > cruft. > > Why do you want to be able to reload Etoys? > > -- > 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 3, 2008

Re: [Pharo-project] EToys

by Damien Cassou

On Mon, Jun 2, 2008 at 4:24 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > No reload of Etoy (as its current state) is important else it will > reintroduce > cruft. Why do you want to be able to reload Etoys? -- 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 3, 2008

Re: [Pharo-project] Missing development tools in Pharo

by Oscar Nierstrasz

My bad! I missed it on this page with a million links -- though I shouldn't since it is right under the pharo releases! Thanks. - on On Jun 3, 2008, at 14:53, Serge Stinckwich wrote: > Hi Oscar, > you can use the Pharo-dev image built by Damien to do that. > > 2008/6/3 Oscar Nierstrasz <oscar(a)iam.unibe.ch>: >> >> I am missing some things in Pharo, starting with the Refactoring >> Browser and >> the VB-regex package. >> >> I sympathize with the principle of keeping Pharo small, but it >> would be >> really nice if we had in the Squeak flap some buttons to load in >> much of >> this standard stuff. How hard would it be to do this? It will >> surely be >> needed for Pharo development itself, no? >> >> - 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 > http://blog.doesnotunderstand.org/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 3, 2008

Re: [Pharo-project] Missing development tools in Pharo

by Serge Stinckwich

Hi Oscar, you can use the Pharo-dev image built by Damien to do that. 2008/6/3 Oscar Nierstrasz <oscar(a)iam.unibe.ch>: > > I am missing some things in Pharo, starting with the Refactoring Browser and > the VB-regex package. > > I sympathize with the principle of keeping Pharo small, but it would be > really nice if we had in the Squeak flap some buttons to load in much of > this standard stuff. How hard would it be to do this? It will surely be > needed for Pharo development itself, no? > > - 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 http://blog.doesnotunderstand.org/

June 3, 2008

[Pharo-project] Missing development tools in Pharo

by Oscar Nierstrasz

I am missing some things in Pharo, starting with the Refactoring Browser and the VB-regex package. I sympathize with the principle of keeping Pharo small, but it would be really nice if we had in the Squeak flap some buttons to load in much of this standard stuff. How hard would it be to do this? It will surely be needed for Pharo development itself, no? - on

June 3, 2008

[Pharo-project] Tools-AlexandreBergel.83 adds a dependency to OmniBrowser

by Damien Cassou

There is a reference to OB specific classes in Tools-AlexandreBergel.83. OB must not be part of pharo in my opinion. -- 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 3, 2008

RE: [Pharo-project] EToys

by Gary Chambers

Looking at the repository the "base" packages are being saved (forked from mainstream Squeak). Which is what I expected. Given the amount of stuff in the inbox I'll have to wait till things have settled down before applying the EToys removal. Bound to be some overlap with other's stuff (MVC removal, for instance). In the meantime I'll continue investigating (as part of work for producing normal Squeak "deployment" images). Regards, Gary. > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr > [mailto:pharo-project-bounces@lists.gforge.inria.fr]On Behalf Of > Stephane Ducasse > Sent: 02 June 2008 5:10 PM > To: An open mailing list to discuss any topics related to an > open-sourceSmalltalk > Subject: Re: [Pharo-project] EToys > > > > I assume for the SLICES thing to work we are essentially forking base > > packages like Morphic? > > No this is just that when people publish a fix that touches several > packages > it was a hell to identify them. Now with a slice we can get the slice > and all the packages that > are reltaed > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 3, 2008

[Pharo-project] why removing testhex?

by StÃ©phane Ducasse

Hi serge why did you remove testHex? BTW I did not receive your nice license agreement

June 3, 2008

Re: {Spam?} [Pharo-project] Some questions on how to help

by StÃ©phane Ducasse

On Jun 2, 2008, at 11:06 PM, Bill Schwab wrote: > Norbert, > > I have also noted the "return nil on error" in parsers, and (my > current > mission) streams. IMHO, these decisions were questionable before > structured exception handling, and are all the more unfortunate > now. My > preference would be to create something like #readFrom:onError: and > then > re-write #readFrom: in terms of it, raising an error inside the block. > Failing to do that risks intermittent downstream failures due to > "unexpected" garbage values. I like my bad news early, and in > context. Yes this is true that we should get rid of code that predate exception such as default block returning values > Skipping to the end of your message, I am hopeful that Pharo will not > suffer from Squeak's barriers to adoption of good code, but I cannot > promise same. It is probably best to start small and ask up-front > whether people want what you propose. I suspect you will find that > good > work will be included in Pharo. Yes and again writing tests and running them.... :) > > > 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 > > >>>> norbert(a)hartl.name 6/2/2008 2:28:15 PM >>> > Hi, > > I really appreciate the existence of the pharo project. For > me I declared it as a good starting point for me to dive > into the deeper waters of squeak/pharo. My biggest problem > is that I do not know how exactly things have to be done. > I don't want to just submit changes without to know if the > worth it. > > A little story. I started last week to toy around with the > newest pharo release. On the web site I read that all tests > green is a primary goal. So I started to let the test runner > run all tests. After having some trouble I found a failing > test in NumberParsingTest. The test is failing because the > test case expects Number>>readFrom: to throw an error if a > number couldn't be parsed. Searchig the ST80 book I found > nothing about Number>>readFrom:. Searching the web I found > a thread on squeak-dev from january where the outcome was: > > - readFrom: returns 0 on unsuccesful read attempt to satisfy > the parser (sounds like some history thing) > - readExactlyFrom: does throw an error an unsuccesful read > attempt. And it utilizes sqNumberParser > > So what to do? I tried to be least aggressive and fixed the > test case to use readExactlyFrom: (and then splitting the > test case into two because the test does different things). > Not thinking first I would have asked a lot of questions on > this list: > > - Do we want to preserve the current readFrom: ? > - Should we integrate sqNumberParser completely avoiding > mulitple implementations? > - Is it only me having slightly problems having a class > Number which uses a class SqNumberParser instead of > integrating the code into the Number hierarchy? > > Is there a way to get this questions answered without generating > a lot of noise on the list? > > Other questions: > > - I scanned the image for obsolete references and found some. I > don't know how to deal with it in an update. Using > > ServerDirectory resetServers. > FileServices removeObsolete. > PackageOrganizer default unregisterPackageNamed: > 'FlexibleVocabularies' > > I have removed all obsolete references but one. How is this > integrated into the upstream? > > - Trying to solve the last obsolete references I found an obsolete > class referenced in PasteUpMorph. The method which referenced it > is PasteUpMorph>>isSafeToServe. The method is in category > Nebraska. I thought Nebraska has been removed from the system. > Thinking that I would have removed all methods of this category > but one because they have no senders. > One method transferRemoteServerFrom: is referenced from > Project>>enter: returningFlag revert: revertFlag saveForRevert: > saveForRevert > Is it ok to rip this call out (by trying to understand what it > does in class Project ;) ) > > > Some words of advice would be helpful to get a feeling about those > things. I don't have a problem preparing some stuff and put it into > the Inbox. A problem would be to have a patch rejected without > explanation :) > > Norbert > > > > > > _______________________________________________ > 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 2, 2008

Re: [Pharo-project] Lots of modifications waiting in PharoInbox

by StÃ©phane Ducasse

lukas helped but indeed may be when marcus is back from PhD last effort. I will try to take some times with alex to show him before the end of the week. Now what would help is that some people have a look at the changes proposed. Stef On Jun 2, 2008, at 11:01 PM, Serge Stinckwich wrote: > There is now a lots of package modifications waiting in the inbox. > Is Stef the only one to integrate the changes inside Pharo ? > > -- > Serge Stinckwich > http://blog.doesnotunderstand.org/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 2, 2008