Damien, Now I'm confused :) If installing Seaside is easy, then the web image is not all that necessary, agreed. With PolyMorph in Pharo, every image gets better. No worries so far. You said "we want one image for Pharo." That is probably a good goal. Will the RB go into Pharo, or will you continue to produce the developer images? Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab@anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029

...

...

damien.cassou@gmail.com 09/28/08 5:38 AM >>> Hi Bill,

I'm not sure I understand your email completly. Please tell me if it is not the case. On Sat, Sep 27, 2008 at 5:44 PM, Bill Schwab <BSchwab@anest.ufl.edu> wrote:

Damien, I suspect you put a lot of work into preparing your images, so please do not view this as anything other than gratitude driving some suggestions. With proper selection of browser and (sorry<g>) deactivating eCompletion, I very much enjoy your web image as a starting point. Whether I continue using it will depend on how hard it is to install Polymorph and the RB vs. Seaside and friends.

Polymorph is going to be included in all Pharo images so you don't have to worry. RB as been in all my images from the beginning and will continue to be. I think I will stop generating web images for Pharo because we want only one image for Pharo. I will try to find a way to make installing Seaside easy.

Call me demanding, I want it all :) Installer can probably (either now or with some refinement) reduce Polymorph (which appears to be on its way into the Pharo base anyway???) and Seaside to one-liners in a script. Ditto cryptography. Add some lines to load .cs or whatever files I create on my own, and I should be able to download an image, and then run one script that builds the new image.

I will stop short of asking you to manually keep up with the small releases, as I probably would end up waiting for the October release before building a new image. It would however be great to either reduce what you do to a simple script, or have it aggressively track updates once Pharo is officially released.

I'm sorry but I do not understand this paragraph.

...

From a gradually decreasing distance at least, Installer looks like it is trying to fill a gap. As always, I would like to see Pharo sprout an ability to apply multiple categories per method; Dolphin has done that from (almost?) the beginning, and it is quite addictive. My point being that however clever, systems that take the one available category to package methods make the restriction all the more obvious.

I hope that makes some sense. Thanks to all for what is shaping up to be a nice system!

Bill