Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Equinox p2 UM workflows"
(New page: This page captures user scenarios in the Eclipse Update Manager and discusses issues or problems that were to be solved by the next provisioning UI (Equinox p2 User Interface). == Sce...) |
|||
Line 12: | Line 12: | ||
== Problems == | == Problems == | ||
* Artificial separation of searching ("what can I get") vs. managing ("what do I have") due to performance characteristics of update sites (long download times). | * Artificial separation of searching ("what can I get") vs. managing ("what do I have") due to performance characteristics of update sites (long download times). | ||
− | * High click count to find new content | + | * High click count to find new content or add new content found on web |
* Repo management part of basic workflows | * Repo management part of basic workflows | ||
* No way to find something by name | * No way to find something by name |
Revision as of 13:16, 19 June 2008
This page captures user scenarios in the Eclipse Update Manager and discusses issues or problems that were to be solved by the next provisioning UI (Equinox p2 User Interface).
Contents
Scenarios
Check for updates
What can I get?
Here's something cool on the web
What do I have?
Automatic Updating
What's wrong?
Repo management
Problems
- Artificial separation of searching ("what can I get") vs. managing ("what do I have") due to performance characteristics of update sites (long download times).
- High click count to find new content or add new content found on web
- Repo management part of basic workflows
- No way to find something by name
- Presentation of detail that user didn't understand (error messages referencing software user didn't know about)
- No ability to retarget UI (dialog vs. preference page) - "All or Nothing" implementation