Damien, Stef, I _think_ what I would want for a starting point is something like Damien's web image, followed by a script that gets the latest of a few things, specific versions of others, and then loads a bunch of .cs or other files for my code.
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. 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. >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 Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: [EMAIL PROTECTED] Tel: (352) 273-6785 FAX: (352) 392-7029 >>> [EMAIL PROTECTED] 09/26/08 11:03 AM >>> On Fri, Sep 26, 2008 at 8:26 AM, Stéphane Ducasse <[EMAIL PROTECTED]> wrote: > - For example I would like to have a real look at MC1.6 but the > message around it is blurry MC1.6 is not the topic here. > I tried LFP and it broke on me. It worked fine for me. You may want to try again and send bug report to Keith who answered all my emails. > - I like installer but when I look at the code I would like to refactor it. The code may not be perfect but it works fine. I don't think Keith would ignore our enhancements to his code. > - There is no document in a nice format that explain why and how (i'm > fixing that for installer and I was waiting because I will refactor it else I > do not publish the chapter but I did not want to insult keith since this is > not the point since I like installer). This is not fair. There is "no document in a nice format that explains" most of the tools you use everyday. But you still use them. The more people use a tool, the best chance you have to get documentation. Moreover, Keith and Matthew wrote a lot of things in pbwiki, squeak wiki and mailing lists. > - unknown is strange :) Should not be for us Squeakers and Pharoers. > - So if you want to help me I would love to have a > - Installer code refactored > - Installer chapter > - Sake (have a look at the code) > - Sake Chapter for the book I would love that too -- 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 [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
