GNOME Bugzilla – Bug 590074
use Calculator instead of gcalctool in about dialog
Last modified: 2012-10-16 20:40:50 UTC
Since we call the application "Calculator" in the menu and in the titlebar etc. I think it makes sense to call it Calculator instead of gcalctool in about dialog too.
*** Bug 590075 has been marked as a duplicate of this bug. ***
Created attachment 165489 [details] [review] Replacing gcalctool by Calculator in About dialog
I'm not sure about this one. The .desktop file and window title have 'Calculator' as this is more logical for users to find the application. However the application name is gcalctool (to differentiate it from other calculator applications). I'm not sure exactly what the about dialog should show. I just need a second opinion to convince me...
You don't need to differentiate GNOME core components or utilities. It is the calculator that is part of GNOME. Core utilities should never display the "branded" or "project codename" to the user.
Even the description in the Ubuntu Software Center refers to it as gcalctools
The about dialog is useful to people who use support forums, bug trackers, etc. When I worked tech support in college, we often asked people to read us the about dialog so we knew exactly what version of what program we were talking about. I think we should consider this use case, epecially since I don't know of any other real use for the about dialog, besides vanity.
For 3.8 I plan to rename the project to "gnome-calculator" as this seems to fit in better with the current GNOME application naming conventions. This means we can set the about dialog to "Calculator" and it will be correct. Also the version numbering can now synchronise with GNOME which will be less confusing (what would have been gcalctool 6.8 will now be gnome-calculator 3.8).
Created attachment 226401 [details] [review] Rename to gnome-calculator Need to sort out how to copy the repository correctly. I make http://git.gnome.org/browse/gnome-calculator but I stuffed up the copy and it's missing branches.
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.