I'm not sure having a VM with a different name is so confusing. Cog is a VM for more than one project, it's got its own identity and that is a good thing to me. Very much like V8 is not called javascriptvm or chromevm to the best of my knowledge. I'd say Pharo uses Cog, not that Cog is Pharo, and there's nothing wrong with that. Cheers.
r. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Esteban Lorenzano Sent: 29 November 2011 12:46 To: Pharo Development Subject: [Pharo-project] Pharo VMs should be more Pharo-like Hi, Currently, we are linking official VMs for pharo taking directly from Jenkins a version and packaging for download (or for Pharo One-Click). I think this is a temporal solution, we need something better: 1) Pharo VMs should have Pharo Icons. 2) Pharo VMs should be named "pharo" or "pharovm" (better the fist), not "CogVM", which is an internal name. 3) We should include a PLUGINS.txt file with information about present plugins (internal and external) 4) We should include a LICENCE.txt file with all licence information. ... I think that's all :) I know... this is very dumb and clearly not mandatory, but it says a lot about the maturity of our Pharo :) All agree? Should I create a ticket? Cheers, Esteban pd: I'm the only one who does not likes One-Click versions? I would prefer a different package for each platform (Is ugly to have a directory named Pharo.app in linux or windows. Also, no need to have all those duplicated-but-for-different-platform files) This email is confidential and subject to important disclaimers and conditions including on offers for the purchase or sale of securities, accuracy and completeness of information, viruses, confidentiality, legal privilege, and legal entity disclaimers, available at http://www.jpmorgan.com/pages/disclosures/email.
