Mariano Martinez Peck wrote:
Ok....so, after reading all answers and comments I see the following possible actions:
1) Do nothing and keep things as now 2) Like 1) but change PharoWeb name to PharoSeaside. 3) Don't create PharoWeb images any more but gives the user the possibilities to use Seaside + Pharo.
The Pharo-Web image is not just the Pharo Seaside image though! I also remember earlier versions of Pharo-Web to have stuff like AIDAWeb and others, but I recently noticed too that was no longer the case. I would go option 4 :) Until Pharo has a well established user friendly package management system, why not look at the Pharo-Web image as Pharo's showcase web development image? A one-click image people can play around with without having to know too much about how to load stuff into their image. On another note, the Pharo team probalby has enough other stuff on their plate to worry too much about what to do with the Pharo-Web image :) -- View this message in context: http://n2.nabble.com/What-about-killing-PharoWeb-images-tp4249050p4255967.ht... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.