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.
Equinox p2 UI Plan
Contents
Definition of priorities
At this stage in the 3.4 release, we are prioritizing the remaining work items for the 3.4 delivery.
- P1 = must have - functional completeness for 3.4 release
- P2 = should have for 3.4 - makes UI more usable
- P3 = nice to have for 3.4
Remaining work items
- P1 = "functionally complete"
- Handling of fix packs/patches (unsure of UI implications)
- Artifact GC/Advanced prefs (??)
- P2 = "Usability"
- Ability to browse "discovered sites" (disabled sites)
- Needed for performance improvements so that not all referenced sites are included in all searches
- Ability to import update manager sites
- Review where we are with reporting invalid plans, trying alternative plans with optionality, keeping info at appropriate level for user
- Ability to browse "discovered sites" (disabled sites)
- P3 = "Extras/Wow"
- Additional repository discovery mechanisms (generic extension and ECF discovery implementation)
- Additional auto-install drop zones in update UI and consider drop zones on task bar
- Additional affordances in update/install dialog for updates, licenses, signing, etc.
- Streamlined revert UI/history page as peer to installed/available view
- Alternate presentation of licenses to emphasize when multiple licenses must be accepted and eliminate duplicates
Milestone plans
M7
The focus for M7 should be functional completeness (finish P1s). Some P2 items are being worked before P1 when the underlying core support isn't there yet for a P1 item.
- Progress reporting affordance in install dialog?
- Preventing parallel provisioning requests, accumulating restart requests
- P1 Verify trust and insert UI for signature verification <Tim>
- P1 User authentication issues <Tim>
- P1 Handling of fix packs/patches
- P1 Definition of IU locking and prevention of certain actions
- P1 Reenable the revert UI and show only root IU's
- P2 Review where we are wrt the UM usability issues in Bug 205517
- P2 High priority usability bugs reported against p2 UI
- P2 Usability improvements in available and installed IU views
- Flat/repo/category view switch with filtering
- Knowledge of installation on available page - filter out what's installed
- Other improvements as described in Bug 216028 and Bug 216029
- P2 Investigate caching/refresh fix for deferred query mechanism and raise any necessary platform UI issues Bug 224516
- P2 Ability to distinguish between discovered and explicitly added repos (UI for repo enable/disable). May be needed for performance
M6
M6 is defined as finishing the P0 and items and getting as far as we can with P1. Some P2 items are being worked before P1 when the underlying core support isn't there yet for a P1 item.
- P0 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 category duplication, merging, sorting bugs
- P1 Detection of install handlers and launch UM when found <Susan>
- P1 Ability to add repos by just pointing at a jar (auto-drop-in a bundle), jar or dir that is not already a p2 repo (UM extension locations) <Susan>
- P2 Quick and easy ways to add repos from web (drag to available IU's target)
- P2 Drag/drop implementations for extension locations, drop-ins
M5
- P1 Performance issues
- 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
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 duplicate contributions from different repos, better sorting
- show only latest versions
- Refactoring and code polish items
- 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
- Improve workflow and information pre-<install/update/uninstall>
- Admin UI
M2
- Build alternate UI for End User - 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