2010/1/5 Mariano Martinez Peck <marianopeck@gmail.com>:
3) Don't create PharoWeb images any more but gives the user the possibilities to use Seaside + Pharo. 3) For me it is the best solution. We can do, the following things:
3.a) Put in www.pharo-project.org/download a text among these lines: 3.b)Â Using this way, we encourage people to use the Metacello configuration for Seaside and that's the most important thing because we can give feedback on it, fix issues, etc. And this is also shared for example with Gemstone. They will give feedback on us and us on them. We will probable make even simpler the move for applications from Pharo to Gemstone. 3.c) Those beta testers that said that they would test Web images, can just install Seaside exactly the same way a final user will do (use the metacello configuration). So...we are also testing that.
3.d) Not now, but maybe in a future we can even use the Esteban Lorenzano's Loader for Metacello. That would be even simpler. They will be able to take a PharoDev image and just evaluate:Â Loader load:'Seaside 2.8.4' and wala!
Lukas is right when he said that PharoWeb used to have Aida in. I stopped installing Aida inside PharoWeb images because it was kind of a pain to make Seaside and Aida work happily together. It doesn't take me much time to build PharoWeb images currently because Seaside 2.8 is quite stable. However, you may be right when you say that it is not Pharo's job to build Seaside images. Download counts can be seen on GForge website: https://gforge.inria.fr/frs/?group_id=1299. I also provide some not-up-to-date graphics: http://damiencassou.dabbledb.com/publish/dev-imagesdownloads. These statistics show that web images are downloaded by nearly as much people as the dev images. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry