DefaultApplicationPriorities

Differences between revisions 6 and 7
Revision 6 as of 2009-06-02 13:17:38
Size: 3048
Editor: ANancy-258-1-2-114
Comment:
Revision 7 as of 2009-06-02 13:23:24
Size: 2709
Editor: ANancy-258-1-2-114
Comment:
Deletions are marked like this. Additions are marked like this.
Line 27: Line 27:
== Assumptions ==
Line 31: Line 29:
You can have subsections that better describe specific parts of the issue.

== Implementation ==

This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

=== UI Changes ===

Should cover changes required to the UI, or specific UI that is required to implement this

=== Code Changes ===

Code changes should include an overview of what needs to change, and in some cases even the specific details.
 * The .desktop files will have an optional InitialPreference=<Priority> (similar key to what KDE is using), a default priority will be used if there is no such key
 * The priorities to use will be described in a policy document
 * /usr/share/applications/defaults.list will not be shipped with new version but still read for compatibility reason
 * The cache format will be changed to list priorities, the cache filename need to be changed to reflect the compatibility breakage
 * The shared-mime-info update-desktop-database tool will be updated to write the new cache
 * glib needs to be update to understand the new format
Line 47: Line 38:
Include:
 * data migration, if any
 * redirects from old URLs to new ones, if any
 * how users will be pointed to the new way of doing things, if necessary.
There is no migration required, a new cache will be used and the previous defaults.list still used for compatibility
Line 58: Line 46:
== Unresolved issues ==

This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.

== BoF agenda and discussion ==

Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.

Summary

The specification describes how the static list shipped with the distribution and describing the application to use for a mimetype will be changed to a dynamic one

Release Note

This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)

It is mandatory.

Rationale

The static list used currently doesn't allow distributors to change a default application easily (vendors installing a commercial DVD players probably want this one to be used by default)

User stories

  • Daniel decides to buy a better DVD player than the one coming with Ubuntu, it goes on the Canonical store and buy a commercial player there, this one should be used once installed
  • Vincent has some w32 exe installers on its disk, those are associated with file-roller by default, he installs wine to be able to install those applications, once installed wine should be the default choice

Design

  • The .desktop files will have an optional InitialPreference=<Priority> (similar key to what KDE is using), a default priority will be used if there is no such key

  • The priorities to use will be described in a policy document
  • /usr/share/applications/defaults.list will not be shipped with new version but still read for compatibility reason
  • The cache format will be changed to list priorities, the cache filename need to be changed to reflect the compatibility breakage
  • The shared-mime-info update-desktop-database tool will be updated to write the new cache
  • glib needs to be update to understand the new format

Migration

There is no migration required, a new cache will be used and the previous defaults.list still used for compatibility

Test/Demo Plan

It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.

This need not be added or completed until the specification is nearing beta.


CategorySpec

DesktopTeam/Specs/Karmic/DefaultApplicationPriorities (last edited 2009-08-04 07:17:14 by 91)