csrabak wrote: > > ... >> 3) Tomorrow we can have AidaWeb images based in pharo (please Janko!!) >> so we can just do the >> same and put the link to those images. > > While I'm fond of the idea on having AidaWeb very soon as possible, I also > think we should put ourselves in Janko's shoes and understand that he'll > need to master Metacelllo to arrive at the packaging. . . > +1
csrabak wrote: > > ... > I would postpone the publishing of these kind of scripts for a much more > stable Pharo and Metacello (or packaging solution ensuing), otherwise > you'll have the same work as testing the scripts means creating and > testing the packages!! > Once Pharo has arrived at a stage where it is extremely easy to manage components/project packages - both from the project and user's point of view - there will still a place to provide a stable environment for those interrested in a dev/web/seaside/aidaweb/glass etc type of image. >From a testing and support point of view, this discussion actually makes me think in a way about the "Pharo-beginner mailing list" suggestion. Pharo's main focuss is on Pharo-Core. On top of Pharo core there may be a number of projects e.g : Pharo-Seaside, Pharo-AIDAWeb, Pharo-Moose, Pharo-GLASS, which all can be loaded into (or un-loaded from) the image (I guess the ConfigurationOfNnnn type scripts). There should be no loss in testers because issues can still be logged, discussed and escallated to the issue culprit, whether it was a configuration script issue or a Pharo-Core issue, no? -- View this message in context: http://n2.nabble.com/What-about-killing-PharoWeb-images-tp4249050p4255309.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
