- Pharo-dev - lists.pharo.org

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