On 16-Aug-09, at 2:50 PM, Stéphane Ducasse wrote:
The point is that pharoers should implement the vision not pharo. We have enough to do. The fact that pharo will succeed depends also on us as a community nor just 5 guys doing an integration of fixes.
Stef
Ok let's talk about bug http://code.google.com/p/pharo/issues/detail?id=1068&q=quit&colspec=ID%20Typ... Part of this is the *purge* of the string Squeak from the image, so Quit Squeak Vm doesn't fire the quit logic (a) I'd rather not have to build two VMs, one for Squeak and one for Pharo (b) Also I'd rather not have to answer is the Pharo VM different from the Squeak VM? (c) If you take the Squeak.app and rename it all to Pharo then someone has to manage that process and ensure the Pharo clone is cloned properly from the Squeak.app (d) if you have a Pharo.app the question then is where did it come from? (e) I do agree having a Pharo app, then seeing quit Squeak VM is very confusing, therefore people should be able to change that to suit their needs. So how would people like to see how this would work. This of course precludes any discussion of how the linux & windows versions behave and give textual feedback. -- = = = ======================================================================== John M. McIntosh <johnmci@smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================