GNOME Bugzilla – Bug 642964
libmenu: Add gmenu_tree_entry_get_short_display_name() API
Last modified: 2013-02-02 02:54:50 UTC
See patch. Note that gnome-shell would likely need to call gmenu_tree_set_sort_key (tree, GMENU_TREE_SORT_SHORT_DISPLAY_NAME);
Created attachment 181591 [details] [review] libmenu: Add gmenu_tree_entry_get_short_display_name() API This would be needed by GNOME Shell to display GenericName instead of Name for apps, if an app has the Core category.
Just to make it clear: I need someone to test that it gives good result in gnome-shell before committing that.
This is pure crack in my opinion. An application should have one name, a single identity. It shouldn't be conflicted about what it is called. It may in addition to the name have an internal code name but that isn't for user consumption. The application should be consistent in its use of the name. It is bad enough we currently also have the, so called, full name. Adding another is just not a good idea. This is trying to solve a problem that just doesn't exist. The Name field is not globally unique. That is a role for app-id. We should be using app-ids like org.gnome.Totem anyway. If something is a core GNOME component the name does not have to be globally unique. It merely has to be unique within the scope. Calling Nautilus (internal code-name) Files in the UI and desktop file is fine because it uniquely identifies it within the GNOME core utilities scope. One of the defining characteristics of a GNOME core utility is that it does not have an identity that is distinct from GNOME. We don't expect it to appear in a KDE app store. If a utility is concerned about how it will appear in other OS environments then it is not a core GNOME utility. We have spent almost two years getting the naming consistent within GNOME and have established simple and effective naming guidelines. Upsetting them and adding unnecessary complexity at this late date is not smart. Especially when it is really only for one problematic and conflicted program.
(In reply to comment #3) > Especially when it is really only for one problematic and conflicted program. That's not true. The biggest problem with your approach is that it doesn't respect the desktop desktop file specification: http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s05.html Name Specific name of the application, for example "Mozilla". Having "Files" or "Chat" is NOT a specific name.
The use of the term "specific" there is in order to differentiate it from the other "generic" name when that is provided. Furthermore there is no precise definition of what specific means. According to our usage guidelines generic names should not be provided for core GNOME components. See http://live.gnome.org/GnomeGoals/CorrectDesktopFiles
Jon: we had the exact same discussion on irc already. Do you really want all of us to repeat the same things again?
Yes, and you're still wrong :)
At this point, I don't think that it would be correct to change the name of Empathy to Chat. I withdraw that request.