On Wed, Jan 27, 2016 at 5:27 AM, Damien Cassou <[email protected]> wrote: > "Sean P. DeNigris" <[email protected]> writes: > >> I now have three Pharo.app files on my Mac - Launcher, Spur, and non-Spur. It >> would be great if we can agree to call one thing Pharo, and add appropriate >> modifiers to the other two names. > > I'm not an OS X user, but I have the impression that .app is reserved > for graphical applications, one you can start with a double click. For > me, no Pharo VM is a graphical application and thus none deserve its > .app file in /Applications. > > On the contrary, what we currently call the Pharo Launcher is a > graphical application so it deserves a .app file. I called it just > Pharo.app because I didn't see any concurrence on the name and some in > the Pharo board would like the launcher to be the default Pharo download > (the one behind the big Download button on the website).
It would be great for Pharo Launcher to be the default download, but why can it not still be called "PharoLauncher.app". It is still just an app on top of *real* Pharo and calling the launcher Pharo.app I believe presents a cognitive dissonance for a newcomer to understand the distinction. The launcher is used to start non-/more-than-Pharo applications like Moose, so to me the launcher application is more generic than just Pharo. Seeing a launcher is generically "a computer program that helps a user to locate and start other computer programs" [1] to me it makes sense to explicitly keep "Launcher" in the app name as the default download. [1] https://en.wikipedia.org/wiki/Comparison_of_desktop_application_launchers cheers -ben > > We could improve the situation by putting all Pharo VMs inside the Pharo > Launcher's .app file. Who volunteers? > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." --Winston Churchill >
