Smalltalk › Pharo › Pharo Smalltalk Developers

"Pharo" Name Overload

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

13 messages Options

Sean P. DeNigris

"Pharo" Name Overload

Administrator

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.

Cheers,
Sean

kilon.alios

Re: "Pharo" Name Overload

Why ? We did not have Pharo-stack.app and Pharo-cog.app and none complained before. Spur will become the default soon enough and you will forget about the other as you forgot about stack vm.

On Tue, 26 Jan 2016 at 17:20, Sean P. DeNigris <[hidden email]> wrote:

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.

-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Pharo-Name-Overload-tp4874242.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sean P. DeNigris

Re: "Pharo" Name Overload

Administrator

kilon.alios wrote

none complained before

This has been a consistent complaint about PharoLauncher's branding as just "Pharo", when "Pharo" already means something else. The Cog/Spur just made it a bit worse.

Cheers,
Sean

kilon.alios

Re: "Pharo" Name Overload

To tell you the truth your idea sound unconventional to me as a Macos user. I never seen an app to put in its name nothing more than the name of the app, maybe just maybe the version though even that is rare. App is essentially just a folder you can navigate . I don't see a good reason for the average Pharo user to name Pharo,app anything but that. Since most of us we won't care or at least thats the way I see it.

On Tue, 26 Jan 2016 at 20:32, Sean P. DeNigris <[hidden email]> wrote:

kilon.alios wrote
> none complained before

This has been a consistent complaint about PharoLauncher's branding as just
"Pharo", when "Pharo" already means something else. The Cog/Spur just made
it a bit worse.

-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Pharo-Name-Overload-tp4874242p4874285.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Damien Cassou-2

Re: "Pharo" Name Overload

In reply to this post by Sean P. DeNigris

"Sean P. DeNigris" <[hidden email]> 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).

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

Damien Cassou-2

Re: "Pharo" Name Overload

In reply to this post by kilon.alios

Dimitris Chloupis <[hidden email]> writes:

> Spur will become the default soon enough and you will forget about the
> other as you forgot about stack vm.

I'm not sure this is what will happen. I have the impression that we
will have one VM for Pharo 4, one VM for Pharo 5, one VM for Pharo 6...

--
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill

Pierce Ng-3

Re: "Pharo" Name Overload

In reply to this post by Sean P. DeNigris

On Tue, Jan 26, 2016 at 06:56:00AM -0800, Sean P. DeNigris wrote:
> 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.

Using more Linux than OSX these days coz my MB battery is crapping out but I
recall in the days of compiling source from squeakvm.org and early Cog versions
that the OSX app icon has a different colour depending on version - pastel pink
and light blue for squeakvm versions and gold for Cog.

Perhaps the same can be done now, or make the words like Launcher, Spur etc
part of the icon.

Pierce

Pierce Ng-3

Re: "Pharo" Name Overload

In reply to this post by kilon.alios

On Tue, Jan 26, 2016 at 06:24:48PM +0000, Dimitris Chloupis wrote:
> Why ? We did not have Pharo-stack.app and Pharo-cog.app and none complained

I've also renamed Pharo to "Pharo Cog" or whatever as the case may be using
Finder. Using Terminal rename Pharo.app to "Pharo Cog.app".

Pierce

Ben Coman

Re: "Pharo" Name Overload

In reply to this post by Damien Cassou-2

On Wed, Jan 27, 2016 at 5:27 AM, Damien Cassou <[hidden email]> wrote:

> "Sean P. DeNigris" <[hidden email]> 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
>

Denis Kudriashov

Re: "Pharo" Name Overload

2016-01-27 3:06 GMT+01:00 Ben Coman <[hidden email]>:

It would be great for Pharo Launcher to be the default download, but
why can it not still be called "PharoLauncher.app".

Damien Cassou-2

Re: "Pharo" Name Overload

In reply to this post by Ben Coman

Ben Coman <[hidden email]> writes:

> On Wed, Jan 27, 2016 at 5:27 AM, Damien Cassou <[hidden email]> wrote:
>> "Sean P. DeNigris" <[hidden email]> 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.

I disagree but I don't care enough to argue. If OS X users agree (and
maybe the board as well), someone should make the change (that won't be
me :-)).

--
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill

stepharo

Re: "Pharo" Name Overload

In reply to this post by Denis Kudriashov

+ 1

Le 27/1/16 09:48, Denis Kudriashov a écrit :

2016-01-27 3:06 GMT+01:00 Ben Coman <[hidden email]>:

It would be great for Pharo Launcher to be the default download, but
why can it not still be called "PharoLauncher.app".

+1

kilon.alios

Re: "Pharo" Name Overload

In reply to this post by Damien Cassou-2

I still wonder why Pharolauncher is not Pharo.app yet. And I could not agree more with your post about apps. But I think I have upset enough people this week :D

On Wed, 27 Jan 2016 at 14:04, Damien Cassou <[hidden email]> wrote:

Ben Coman <[hidden email]> writes:

> On Wed, Jan 27, 2016 at 5:27 AM, Damien Cassou <[hidden email]> wrote:
>> "Sean P. DeNigris" <[hidden email]> 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.

I disagree but I don't care enough to argue. If OS X users agree (and
maybe the board as well), someone should make the change (that won't be
me :-)).

--
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill