Difference between revisions of "Equinox p2 UI Plan"

Revision as of 15:31, 21 February 2008

Definition of priorities

At this stage in the 3.4 release, we are prioritizing the remaining work items for the 3.4 delivery.

• P0 = must have before turning the p2 switch on in the SDK
  • At this point these should be done.
  • In some cases there are patches waiting, such as the switch itself.
• P1 = must have for 3.4 release
• P2 = should have for 3.4 - makes UI more usable
• P3 = nice to have for 3.4 - "wow factor"

Remaining work items

• P1 = "functionally complete"
  • Verify trust and insert UI for signature verification <Tim>
  • Detection of install handlers and launch UM when found <Susan>
  • Ability to add repos by just pointing at a jar, dir that is not already a p2 repo (UM extension locations) <Susan>
    • May be a chance to add discovery while doing this
  • Integration of directory watcher/drop-ins folder prefs <Susan>
  • Repo login and user verification issues <Tim>
  • Recovery application <Tim>
  • Integrate artifact GC and any prefs needed <Susan>
  • Handling of fix packs/patches
  • Representation of product base
  • Representation of locked IU's in shared install

• P2 = "Usability"
  • Review where we are wrt the UM usability issues Bug 205517
  • Usability improvements in available and installed IU views
    • Flat/repo/category view switch with filtering
    • Cross-page context - affordances for updates available on installed page, already installed on available page
    • Other improvements as identified in usability review
  • Quick and easy ways to add repos from web (drag/cut/paste to available IU's target)
  • ECF Discovery of repos integrated into add site
  • Streamlined revert UI/history page as peer to installed/available view
  • Review where we are with reporting invalid plans, keeping info at appropriate level for user
  • Alternate presentation of licenses to emphasize when multiple licenses must be accepted and eliminate duplicates

• P3 = "Wow"
  • Drag/drop implementations for extension locations, drop-ins
    • Drop zones in update UI and consider drop zones on task bar
  • Additional affordances in update/install dialog for licenses, signing, etc.

Milestone plans

M6

• P0 Understand the tie between the UI and the Update manager, UM hides its contributions if p2 is there <Tim>
• P0 Fix annoying auto-update popup bugs and overeager error reporting
• P0 Detect invalid update plans before notifying user
• P0 Fix remaining unacceptable UI bugs (duplicate categories, etc.)
• P1 Verify trust and insert UI for signature verification <Tim>
• P1 Detection of install handlers and launch UM when found <Susan>
• P1 Ability to add repos by just pointing at a jar, dir that is not already a p2 repo (UM extension locations) <Susan>
• P1 Integration of directory watcher/drop-ins folder prefs <Susan>

M5

• P1 Performance issues
  • Background resolving/sizing for user-triggered updates
  • Rework model to reference ids (profile ids, repo URLs) in lieu of objects
• Restructure available IU viewer for PDE consumption
• API for profile change requests
• Automatic updates life-cycle, affordance and popup workflow
• Improve property pages for IUs in end user UI
• Summary info for install/update wizards
  • Timing of resolves once inside an install/update wizard

M4

• Polish install and update scenarios
  • Notify of auto-download separate from install
  • Preferences for reminding user of available updates Bug 207493
  • Performance/progress when resolving/planning
• Improved support for browsing repos
  • IU categories Bug 203115
  • remove duplicates, better sorting
  • show only latest versions
• Refactoring and code polish items
  • Clean up adapter usage
  • Clean up/simplify colocated repo handling
  • Use deferred content providers for repo content
  • Allow UI app to specify repo taxonomy via queries
• UI for Revert Bug 205223
• Improved way to present licenses and remember accepted licenses Bug 205232
• Admin UI features as needed by team

M3

• End user UI
  • Improve workflow and information pre-<install/update/uninstall>
    • Prompting replaced by informational wizard Bug 204321
    • Size/time estimation on install/update (Depends on Bug 201488)
    • One entry point per group Bug 204823
    • Detect invalid states on install/update/uninstall
  • Polling for software updates and associated user prefs
    • Automatic updating
    • Alert me when updates available
    • Ability to download and then notify
• Admin UI
  • Artifact repo view shows artifact descriptors, processing steps, etc.

M2

• Install, Uninstall, and/or update IU's from running profile
  • user views installed IU's in the current profile
  • user can manage repositories as an advanced feature (separate button on dialog)
    • repositories are colocated (no distinction between metadata and artifact repo)
  • UI prequalifies the install
    • figure out if the install is valid using oracle
    • [deferred] use advanced oracle to flag any invalid states
    • [deferred] use advanced oracle to precompute info such as download size/time, etc.
  • user can uninstall an installed IU
  • user can update an installed IU
• Repository naming
  • repo level
  • [deferred] user can override repo name
• Better filtering of repos and IU's (show only what's relevant to end user)
• Refactor drag support into common UI project
• Filtering of IU's based on entry point concept
  • Give the ability to name what is being installed
• Admin UI can launch end user UI from selected profile in profile view
  • should be able to disable colocated repo management
• AdminUI views show enhanced info about objects (multiple columns)
• AdminUI and User UI contribute different property pages

M1

• Browse repositories
  • Add/remove repositories
  • Browse IU's in a metadata repository
  • Install IU from a metadata repository into a selected profile
• Browse profiles
  • Add/remove profiles
  • Browse IU's in a profile
  • Uninstall IU

Additional Requirements

This is a list of some original UI requirements that are not on the 3.4 plan.

• Installation by drag and drop on a running eclipse
• Install from a click on the webpage
• Silent installation
• Support installation even when there are errors in the configuration