Jump to: navigation, search

Difference between revisions of "Equinox/p2/User Interface"

< Equinox‎ | p2
(Scenario 6: What's wrong with my configuration?)
 
(24 intermediate revisions by one other user not shown)
Line 1: Line 1:
__TOC__
+
This page provides links to the various design and discussion documents surrounding the p2 User Interface.
This page captures user scenarios in the p2 User Interface and discusses problems and issues in the workflow.
+
  
== Original Goals ==
+
== Workflows ==
Most of the goals were derived from problems observed/reported in the previous UI (Update Manager).  See  [[Equinox p2 UM workflows]] for the equivalent scenarios.
+
* [[Equinox p2 UM workflows]] summarizes the Eclipse 3.3 Update Manager scenarios
* Reduce click/decision counts
+
* [[Equinox p2 UI 3.4 workflows]] summarizes the goals for the Eclipse 3.4 (p2) Update UI. It includes scenarios and compares click counts to the 3.3 UI.
* Move advanced concepts out of main workflows
+
* [[Equinox p2 UI 3.5 workflows]] provides mockups for proposed changes in 3.5
** required software details (automatic resolution)
+
** repo management (alternate views of content)
+
** mirror selection (automatic)
+
** install locations (not supported)
+
* Automatic updating should not interrupt workflow
+
* Make it easier for users to get content they find on the web
+
* Integrate "what do I have" with "what can I get"
+
* Integrate "what do I have" with "what updates are available"
+
* User-oriented error messages, higher level explanations
+
* Code structured for multiple levels of integration (pluggable policies, different host dialogs, building blocks)
+
  
== Scenarios ==
+
== Design discussions ==
=== Scenario 1: Check for updates ===
+
* [[Equinox p2 UIWG Walkthrough|p2 UIWG First Walkthrough]] includes the both the prep info and the minutes from the 6/25/2008 walkthrough of the p2 UI at the UIWG.
*Help >
+
* [[Equinox p2 UI Use Cases]] includes discussion of user personas, important user scenarios, and discussion of changes that may be necessary in the 3.5 p2 UI
*Software Updates...
+
*[[Equinox/p2/UIWG Walkthrough 2|p2 UIWG Second Walkthrough]] includes the prep info for the 10/1/2008 walkthrough of the p2 UI at the UIWG
  
[[Image:P2InstalledList.jpg]]
+
== Development Plans ==
 +
* [[Equinox p2 UI Plan]] contains the working plan for the UI current release
 +
* [[Equinox p2 UI Eclipse 3.4 Plan]] contains milestone plans from the 3.4 release
  
*select Installed Software page
+
== Testing ==
*Update...
+
* [[Equinox/p2/UI Manual Tests]] contains the UI manual tests
  
[[Image:P2UpdateDialog.jpg]]
+
== How-to's ==
 
+
* [[Equinox/p2/Adding Self-Update to an RCP Application]]
*Next
+
 
+
[[Image:P2LicenseDialog.jpg]]
+
 
+
*I accept...
+
*Finish
+
 
+
==== Click/decision count ====
+
* 7 clicks/decisions (vs. 14 for UM)
+
* Can reduce to 5 once a license has been accepted/remembered (vs. 12 with UM automatic mirror selection)
+
 
+
=== Scenario 2: What add-ons can I get? ===
+
 
+
*Help >
+
*Software Updates...
+
 
+
[[Image:P2AvailableList.jpg]]
+
 
+
*select Available Software page
+
* expand each site, then categories, and checkmark desired items
+
 
+
**[[Image:P2BySite.jpg]]
+
 
+
* OR view by categories, expand categories, and checkmark desired items
+
 
+
**[[Image:P2ByCategory.jpg]]
+
 
+
* OR view by name, checkmark desired items
+
 
+
**[[Image:P2ByName.jpg]]
+
 
+
* OR filter by name from any view
+
 
+
**[[Image:P2Filtered.jpg]]
+
 
+
* Install...
+
* Progress dialog followed by Install dialog
+
* Scenario continues similar to update completion
+
 
+
==== Click/decision count ====
+
* 3 clicks/decisions to get to browsing mode (vs. 7 for UM)
+
* alternate ways to find content (UM by site only)
+
* ability to find by name
+
* once items are selected for install, 3 clicks to finish (Next, I accept..., Finish) as in update scenario.  One click if license was previously accepted.  (UM is 4 clicks)
+
 
+
=== Scenario 3: Found something cool on the web ===
+
Setup:  User finds software with an update site reference on the web
+
 
+
  [[Image:P2WebContent.jpg]]
+
 
+
*Help >
+
*Software Updates...
+
*select Available Software page
+
*drag URL from browser to list (this adds the site and expands it)
+
 
+
[[Image:P2DragResult.jpg]]
+
 
+
==== Click/decision count ====
+
* 4 clicks/decisions to get new content shown in UI (vs. 14 for UM)
+
* once items are selected for install, 3 clicks to finish (Next, I accept..., Finish) as in update scenario.  One click if license was previously accepted.  (UM is 4 clicks)
+
 
+
=== Scenario 4: What do I have? ===
+
*Help >
+
*Software Updates...
+
*select Installed Software page
+
 
+
[[Image:P2InstalledList.jpg]]
+
 
+
==== Click/decision count ====
+
* 3 clicks/decisions to see high level of what user installed (vs. 4 for UM)
+
* No way to get more detail (UM provides drill-down detail)
+
* No link from installed view to more detailed Help > About information
+
 
+
==== Detailed feature view of what's installed ====
+
*Help >
+
*About Eclipse SDK
+
*Feature Details
+
 
+
[[Image:P2AboutFeatureDetail.jpg]]
+
 
+
==== Detailed plug-in view of what's installed ====
+
*Help >
+
*About Eclipse SDK
+
*Plug-in Details
+
 
+
=== Scenario 5: Automatic Updating ===
+
 
+
Like Update Manager, p2 defines preferences for the user to set up automatic update scheduling on every startup of Eclipse, or at daily or weekly scheduled times.  Users can also set a preference so that updates are automatically downloaded before the user is ever notified that updates have been found.  In addition, users can set reminder options so that they can ignore update notifications and be reminded later.
+
 
+
Setup:  User is working and updates have been discovered and/or downloaded
+
 
+
*Popup notifies user of available updates.  User can keep working.
+
 
+
[[Image:P2UpdateNotify.jpg]]
+
 
+
* User can click on the popup to review the updates when ready.  This will result in the update dialog shown in Scenario #1
+
* User can ignore popup until ready to deal with it
+
* User can dismiss popup and retrieve the update list again by clicking on the update affordance in the status bar
+
 
+
==== Click/decision count ====
+
* Work is not interrupted, user can ignore updates until ready or dismiss popup until ready
+
**After clicking on popup, 3 clicks (or 1 if license has previously been accepted) to install the updates (vs. 7 for UM)
+
**If popup is dismissed, 4 clicks (or 2 if license has previously been accepted) to reactivate and complete update dialog (vs. 14 clicks/decisions to manually recheck for updates with UM)
+
**Reminder options allow the 3-click (or 1 if license has previously been accepted) option at specified intervals
+
 
+
=== Scenario 6: What's wrong with my configuration? ===
+
 
+
p2 currently does not provide any diagnostic tools to help users when plug-ins they expect to be installed are not there, or if there are compatibility conflicts with plug-ins.  Users must currently activate a capability to enable "Classic Update Manager" and use the Update Manager manage configuration dialog.
+
 
+
=== Scenario 7: What sites am I using ===
+
 
+
== Problems ==
+
* Implementation has same performance problems as UM did (user may have to wait a long time for content to fill in or for resolution to take place).
+
* Original modeless ("dashboard") design forced modal due to implementation problems with progress reporting, keyboard handling, inconsistency with rest of Eclipse
+
* Too much repo management forced on user
+
* We haven't improved error reporting (some find it worse) - need to decipher resolution errors and report in user-friendly way
+
* We removed detail about software requirements/underlying libraries.  Some users want to know.  Inconsistencies remain due to late-breaking issues (need to show licenses for all things even though user doesn't see those things anywhere else).
+
 
+
== Questions ==
+
* tweak the problems or step back?
+
* unfolding of detail
+
 
+
== Milestone plans ==
+
UI planning information has moved to [[Equinox p2 UI Plan]]
+
  
 
[[Category:Equinox p2|User Interface]]
 
[[Category:Equinox p2|User Interface]]

Latest revision as of 15:30, 3 January 2011

This page provides links to the various design and discussion documents surrounding the p2 User Interface.

Workflows

Design discussions

  • p2 UIWG First Walkthrough includes the both the prep info and the minutes from the 6/25/2008 walkthrough of the p2 UI at the UIWG.
  • Equinox p2 UI Use Cases includes discussion of user personas, important user scenarios, and discussion of changes that may be necessary in the 3.5 p2 UI
  • p2 UIWG Second Walkthrough includes the prep info for the 10/1/2008 walkthrough of the p2 UI at the UIWG

Development Plans

Testing

How-to's