Properly Implement Generic Names for Default Apps

Registered by Cameron Norman

Some, but not all, elementary app names should be generic in the pantheon environment. They should not be generic in other environments. This is a blueprint for how, specifically, to achieve that.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Medium
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Approved
Series goal:
None
Implementation:
Implemented
Milestone target:
milestone icon loki
Started by
Danielle Foré
Completed by
Danielle Foré

Whiteboard

I propose a simple solution using the following extension to the .desktop file standard: http://standards.freedesktop.org/menu-spec/menu-spec-1.0.html#desktop-entry-extensions. (Specifically, the OnlyShowIn and NotShowIn parts).

All apps using a generic name will ship TWO .desktop files. One will use the generic name and have the line "OnlyShowIn=Pantheon". The other will use the unique name and have the line "NotShowIn=Pantheon". The effect is that the app will be shown with a generic name in Pantheon, but a unique name in all other environments.

In order to make this work, the "Pantheon" environment should be registered with freedesktop (I have no idea how to do this, sorry), two desktop files must be shipped, as described above, and the Pantheon environment label must be used on the Pantheon side of things. I don't know how the last itme would be done, either. Would it be in slingshot and plank (pantheon dock), or in the session?

~CameronNemo

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.