- Pharo-dev - lists.pharo.org

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