On Mon, Jan 4, 2010 at 7:14 PM, Dale Henrichs <dale.henrichs@gemstone.com> wrote:

----- "Lukas Renggli" <renggli@gmail.com> wrote:


| > 4) Now I created all the Metacello configurations for the PharoDev
| image and
| > I took me a lot of time. Because I am not the developer of any of
| those
| > projects. So, I need to understand the dependencies, the order, the
| > versions, etc. But why ??? If Seaside people have already done that,
| don't
| > duplicate efforts.
|
| There is a configuration for Seaside 3.0 (and probably also Seaside
| 2.8). This was probably the first configuration every written. Ask
| Dale.

Yes Seaside3.0 was one of the original motivations behind Metacello:)

There are Seaside3.0, Seaside2.8 and Pier (for Seaside2.8) configurations in the Metacello Repository and these were built based on information Lukas, so they should match pretty closely the web image content.

This is really cool. And just because of this I think that we don't need the PharoWeb image, as you have the following options already:

- Use metacello configuration by yourself. It is just one line of code and we can even explain in how to do it in the website. Even more, you can load that conf in a Pharo Dev, at that's all :)
- Use Seaside one click
- Use Lukas script.
�

I agree with the notion of one-click for ease of getting started with a particular framework/project. In the GLASS effort I've often outstripped the one-click images (and appliances) and run into support issues as a consequence.

Once a developer is comfortable with the technology then they are likely to want to build their own image and if the one-click was built with a know configuration, then the developer has a reasonable chance of duplicating the code in his/her custom image.

Dale

_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project