ARMaelalip_appman_ext
Launchpad Entry: foo
Created:
Contributors:
Packages affected:
Summary
Extend an existing graphical application manager to allow users to determine all the dependencies of a particular application, and show the minimum file system size required to support these. Allows device designers to determine the storage requirements for a single use device e.g. Audio player, browser.
Release Note
Speeds up device design.
Rationale
For embedded devices storage can be a limiting factor. Determining the packages required to support a single application, and hence the storage required, can be a time consuming task. A single point & click way of doing this may aid the adoption of Ubuntu ARM as the platform of choice.
User stories
A device manufacturer is designing a browser. He likes the look of arora, but firefox looks good too. Using the appmanext he quickly determines which will take less storage.
Assumptions
- Dependency circularities will not hang the dependency search.
- Support infrastructure in placed e.g. a file system image with the listed packages can be easily constructed.
Design
You can have subsections that better describe specific parts of the issue.
Implementation
Pick a graphical app manager
Available in Lucid
- aptitude
- Better place to fit the option
- synaptic
- Smaller code base
- Nicer GUI
Chose aptitude since I'm more familiar with C++ than XML etc.
UI Changes
Separate dialogue/button on package? Not all packages have any use for the button - so use separate dialogue.
TODO: More detail after app manager chosen
Code Changes
TODO:Identify areas after app manager chosen
Migration
- data migration - NONE
- redirects from old URLs to new ones - NONE
- how users will be pointed to the new way of doing things
- Help entry
- Menu option
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.
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.