Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Equinox p2 UI Plan"

(M5 - Jan 30, 2009 - Major Feature Freeze)
(M2 - Sep 18, 2009)
 
(74 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
__TOC__
 
__TOC__
This page describes the work planned for the next release (3.5) of the p2 UI.  This includes improvements for the p2 UI in the Eclipse SDK, as well as issues that have to be addressed for alternate UIs (such as RCP app requirements).  Important fixes will be examined for inclusion/backport to 3.4.x maintenance stream.
+
This page describes the work planned for the next release (3.6) of the p2 UI.  This includes improvements for the p2 UI in the Eclipse SDK, as well as issues that have to be addressed for alternate UIs (such as RCP app requirements).  Important fixes will be examined for inclusion/backport to 3.5.x maintenance stream.
  
The overall p2 plan for 3.5 is located at [[Equinox_p2_Plan]]
+
The overall p2 plan for 3.6 is located at [[Equinox_p2_Plan]]
 +
 
 +
The milestone plans for 3.5 have moved to [[Equinox p2 UI Eclipse 3.5 Plan]]
  
 
The milestone plans for 3.4 have moved to [[Equinox p2 UI Eclipse 3.4 Plan]]
 
The milestone plans for 3.4 have moved to [[Equinox p2 UI Eclipse 3.4 Plan]]
  
==3.5 Milestone Plans==
+
==3.6 Ideas list==
=== M5 - Jan 30, 2009 - Major Feature Freeze ===
+
=== UI/Usability ===
*UI/Usability
+
* Ability to define/share/install/uninstall user-named groups of IU's (Susan, Ian?)
** improved error reporting and explanation of problems between the planner and the UI [https://bugs.eclipse.org/bugs/show_bug.cgi?id=218055 Bug 218055]
+
** "My tool set"
** better presentation of repositories
+
** Extension location use cases that don't necessarily depend on physical location
*** Need to do a better job of deciding which repos to look up against [https://bugs.eclipse.org/bugs/show_bug.cgi?id=234213 Bug 234213]
+
* Transport-related issues
*** Access to sites from all workflows [https://bugs.eclipse.org/bugs/show_bug.cgi?id=250316 Bug 250316]
+
** showing detailed repository status when known
*** user repo naming (regression of UM function) [https://bugs.eclipse.org/bugs/show_bug.cgi?id=194224 Bug 194224]
+
** authentication scoping
*** improve presentation of enabled/disabled repositories [https://bugs.eclipse.org/bugs/show_bug.cgi?id=218534 Bug 218534]
+
** progress reporting improvements
*** discovery mechanisms
+
* Network discovery of repos [https://bugs.eclipse.org/bugs/show_bug.cgi?id=218534 bug 218534] - Scott
** Complete implementation for available view affordances [https://bugs.eclipse.org/bugs/show_bug.cgi?id=216032 Bug 216032]
+
** discover LAN (and WAN) based metadata and artifact repos
** Revert UI improvements
+
** depends on server-side work in bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=258340 bug 258340]
*** history view integrated into about dialog [https://bugs.eclipse.org/bugs/show_bug.cgi?id=250316 Bug 250316], see [http://wiki.eclipse.org/Equinox_p2_UI_3.5_workflows#About Mockups]
+
* Separation of product base vs. "add-ons" [https://bugs.eclipse.org/bugs/show_bug.cgi?id=215398 Bug 215398]
*** background job/progress reporting/UI freeze issues
+
** Differentiating the base product stuff from added content
** investigate streamlined license UI [https://bugs.eclipse.org/bugs/show_bug.cgi?id=217944 Bug 217944]
+
** User shouldn't be able to (unintentionally) redefine what is "the product" by installing something
** Investigate the separation of product base vs. "add-ons" [https://bugs.eclipse.org/bugs/show_bug.cgi?id=215398 Bug 215398]
+
* Fast-path install scenarios [https://bugs.eclipse.org/bugs/show_bug.cgi?id=223264 Bug 223264]
** Investigate fast-path install scenarios [https://bugs.eclipse.org/bugs/show_bug.cgi?id=223264 Bug 223264]
+
* Search based metaphor
*API
+
** Currently the UI is repository centric. It would probably be beneficial to have a more search oriented UI.
** product configures user access to repos [https://bugs.eclipse.org/bugs/show_bug.cgi?id=231039 Bug 231039]
+
** should UI be the one coordinating provisioning operations vs. having scheduling rules [https://bugs.eclipse.org/bugs/show_bug.cgi?id=218216 Bug 218216]
+
  
=== M6 - Mar 12, 2009 - API Freeze ===
+
=== API===
*API
+
* Cleanup and document existing provisional API  
** convert actions to handlers for UI pluggability
+
** javadoc
** javadoc, package.html, and API scrub
+
** wizard page creation should be early and explicit (problems with dynamic page creation)
** automated test cases for all API contracts
+
** ability to insert pages into a wizard
** examples or work with clients to demonstrate/verify that we provide appropriate level of reuse
+
** actions should not be API (make internal or migrate to commands and handlers)
 +
* Supported API for all UI building blocks
 +
** Individual wizards, dialogs, commands
 +
** consider handlers vs. actions for UI pluggability/are some command ID's contracts (so clients can invoke UI by id)
 +
** Content and label providers
  
=== M7 - May 1, 2009 - Development Freeze ===
+
== 3.6 Milestone Plans ==
==Past 3.4.x Maintenance Streams==
+
=== M1 - Aug 7, 2009 ===
===3.4.1===
+
* [[Image:Ok_green.gif]] alternate license UI [https://bugs.eclipse.org/bugs/show_bug.cgi?id=217944 Bug 217944] - (Susan)
* [[Image:Ok_green.gif]] Improved progress reporting and honoring cancellation requests
+
* [[Image:Ok_green.gif]] Improved presentation of errors (resizability, formatting)
+
* [[Image:Ok_green.gif]] Fix confusing restart language
+
* [[Image:Ok_green.gif]] Annoying /low risk bugs
+
** [[Image:Ok_green.gif]] Refresh artifact repos when metadata repos are refreshed
+
  
===3.4.2===
+
=== M2 - Sep 18, 2009 ===
* [[Image:Ok_green.gif]] Enable a site when a user adds a disabled one (workaround until core fixes in 3.5)
+
* [[Image:Ok_green.gif]] Improvements to the installation history (Susan)
* [[Image:Progress.gif]] NLS formatting fixes (awaiting NL team verification)
+
** [[Image:Ok_green.gif]] User management of profile snapshots [https://bugs.eclipse.org/bugs/show_bug.cgi?id=284798 Bug 284798]
 +
** [[Image:Ok_green.gif]] Comparing configurations in the install history
  
==Past 3.5 Milestones==
+
=== M3 - Oct 30, 2009 ===
=== M1 - Aug 8, 2008 ===
+
* Install wizard improvements (Susan)
* UI/Usability
+
** Selection count indicator and popup
** Usability review of general strategy (modality, overall organization, etc.)
+
** non-filtered selections [https://bugs.eclipse.org/bugs/show_bug.cgi?id=235654 Bug 235654], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=257597 Bug 257597], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=278189 Bug 278189]
*** [[Image:Ok_green.gif]] Walkthrough with Eclipse UIWG
+
** Consider modeless operation
*** [[Image:Ok_green.gif]] Solicit usability and user persona input from product teams
+
* Query/load assumptions, better async support (Susan)
*** [[Image:Ok_green.gif]] Write concrete user personas to guide use cases
+
** Get rid of deferred tree content manager and the "load is slow, query is fast" assumptions
** Bugs
+
** Alternate progress indication during fetch job (redirect to the wizard)
*** [[Image:Ok_green.gif]] Bring 3.4.1 fixes into 3.5 stream
+
** incremental fill-in
  
=== M2 - Sep 19, 2008 ===
+
=== M4 - Dec 11, 2009 ===
* UI/Usability
+
* Cleanup dead code and formalize wizard page progression in install wizards (Susan)
** [[Image:Ok_green.gif]] Develop use cases based on user persona input
+
* First class support of explanations in UI (Susan)
** [[Image:Ok_green.gif]] Investigate integration of installed view with about dialog
+
** error indicators and quick fix/alternate actions [https://bugs.eclipse.org/bugs/show_bug.cgi?id=248959 Bug 248959], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=267464 Bug 267464], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=218048 Bug 218048], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=261928 Bug 261928]
** [[Image:Ok_green.gif]] Develop mockups for new workflows and solicit feedback
+
** consolidate "empty explanations" with error indicators
*Performance/Stability
+
** better consolidation of repo errors (repo empty explanation vs. accumulating repo error indicator)
** [[Image:Progress.gif]] revisit checkbox/filter/deferred fetch strategy [https://bugs.eclipse.org/bugs/show_bug.cgi?id=233269 Bug 233269] (continuing in M3)
+
** [[Image:Progress.gif]] investigate resolution in the background [https://bugs.eclipse.org/bugs/show_bug.cgi?id=236495 Bug 236495] (continuing in the scope of new workflows in M3)
+
  
=== M3 - Oct 31, 2008 ===
+
=== M5 - Jan 29, 2010 ===
* UI/Usability
+
=== M6 - Mar 11, 2010 ===
** [[Image:Ok_green.gif]] Complete new workflows (installed view may not yet be integrated with about dialog)
+
=== M7 - Apr 30, 2010 ===
** [[Image:Ok_green.gif]] Begin improved implementation of installed view [https://bugs.eclipse.org/bugs/show_bug.cgi?id=224472 Bug 224472]
+
*** [[Image:Ok_green.gif]] Allow drill-down in installed view of requirements that are visible as groups
+
*** [[Image:Ok_green.gif]] Identify any necessary metadata changes to make this simpler/better (see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=227675 Bug 227675])
+
* Performance/Stability
+
** [[Image:Progress.gif]] finalize checkbox/filter/deferred fetch strategy [https://bugs.eclipse.org/bugs/show_bug.cgi?id=233269 Bug 233269]
+
*** Better/faster filtering without graying out filter box (postponed to M4)
+
*** [[Image:Ok_green.gif]] Eliminate "duplicate nodes" problem on first repo read
+
** [[Image:Ok_green.gif]] resolution in the background to be provided as part of new workflows [https://bugs.eclipse.org/bugs/show_bug.cgi?id=236495 Bug 236495]
+
** [[Image:Ok_green.gif]] Investigate repo adding/loading performance issues and identify necessary changes to core [https://bugs.eclipse.org/bugs/show_bug.cgi?id=236485 Bug 236485]
+
  
=== M4 - Dec 12, 2008 ===
 
*UI/Usability
 
** Finish up installed view changes
 
*** [[Image:Progress.gif]] Complete integration of installed view with about dialog
 
*** [[Image:Ok_green.gif]] Install drill-down info also shown in install/update wizards [https://bugs.eclipse.org/bugs/show_bug.cgi?id=250862 Bug 250862]
 
*** [[Image:Glass.gif]] Investigate the ability to provide optional/related content [https://bugs.eclipse.org/bugs/show_bug.cgi?id=247342 Bug 247342].  (Decision is not to do anything at this time)
 
** [[Image:Glass.gif]] Investigate better affordances in available view to show already installed, available updates, etc. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=216032 Bug 216032]
 
*** [[Image:Ok_green.gif]] Complete initial model/collector work needed to distinguish status and improve "already installed" filtering [https://bugs.eclipse.org/bugs/show_bug.cgi?id=210583 Bug 210583] and [https://bugs.eclipse.org/bugs/show_bug.cgi?id=232632 Bug 232632]
 
* Performance/Stability
 
** [[Image:Ok_green.gif]] finalize checkbox/filter/deferred fetch strategy [https://bugs.eclipse.org/bugs/show_bug.cgi?id=233269 Bug 233269]
 
*** [[Image:Ok_green.gif]] Better/faster filtering without graying out filter box
 
*Usability+Performance
 
** [[Image:Ok_green.gif]] More selective loading of repos when sites are added [https://bugs.eclipse.org/bugs/show_bug.cgi?id=236485 Bug 236485]
 
*API
 
** [[Image:Ok_green.gif]] Separation of contributions from the rest of the code [https://bugs.eclipse.org/bugs/show_bug.cgi?id=221760 Bug 221760]
 
** [[Image:Progress.gif]] Ability to reassemble groups (available, installed, history, repo management) into new locations (pref page vs. wizard, etc.)
 
 
== Items not yet assigned to milestones ==
 
 
=== UI/Usability ===
 
* ability to install/uninstall user-named groups of IU's
 
 
=== API===
 
* Investigate other levels of detail provided by API (listed from most general to most granular)
 
** One callable, preconfigured UI with pluggable policy (query providers, policies, etc.)
 
** Expose all building blocks for RCP apps
 
*** Individual wizards, dialogs, actions
 
*** Content and label providers
 
* Ensure code is structured for managed scenarios (minimal UI that is required)
 
** Silent/automatic updating, user never sees the update UI, it just happens (but may need confirmation, restart dialog, etc.)
 
** User's environment is defined explicitly by someone external (administrator)
 
*** Upgrade or install to a new specification
 
*** Compare current installation to required one
 
  
 
[[Category:Equinox p2|UI Plan]]
 
[[Category:Equinox p2|UI Plan]]

Latest revision as of 18:09, 9 September 2009

This page describes the work planned for the next release (3.6) of the p2 UI. This includes improvements for the p2 UI in the Eclipse SDK, as well as issues that have to be addressed for alternate UIs (such as RCP app requirements). Important fixes will be examined for inclusion/backport to 3.5.x maintenance stream.

The overall p2 plan for 3.6 is located at Equinox_p2_Plan

The milestone plans for 3.5 have moved to Equinox p2 UI Eclipse 3.5 Plan

The milestone plans for 3.4 have moved to Equinox p2 UI Eclipse 3.4 Plan

3.6 Ideas list

UI/Usability

  • Ability to define/share/install/uninstall user-named groups of IU's (Susan, Ian?)
    • "My tool set"
    • Extension location use cases that don't necessarily depend on physical location
  • Transport-related issues
    • showing detailed repository status when known
    • authentication scoping
    • progress reporting improvements
  • Network discovery of repos bug 218534 - Scott
    • discover LAN (and WAN) based metadata and artifact repos
    • depends on server-side work in bug bug 258340
  • Separation of product base vs. "add-ons" Bug 215398
    • Differentiating the base product stuff from added content
    • User shouldn't be able to (unintentionally) redefine what is "the product" by installing something
  • Fast-path install scenarios Bug 223264
  • Search based metaphor
    • Currently the UI is repository centric. It would probably be beneficial to have a more search oriented UI.

API

  • Cleanup and document existing provisional API
    • javadoc
    • wizard page creation should be early and explicit (problems with dynamic page creation)
    • ability to insert pages into a wizard
    • actions should not be API (make internal or migrate to commands and handlers)
  • Supported API for all UI building blocks
    • Individual wizards, dialogs, commands
    • consider handlers vs. actions for UI pluggability/are some command ID's contracts (so clients can invoke UI by id)
    • Content and label providers

3.6 Milestone Plans

M1 - Aug 7, 2009

M2 - Sep 18, 2009

  • Ok green.gif Improvements to the installation history (Susan)
    • Ok green.gif User management of profile snapshots Bug 284798
    • Ok green.gif Comparing configurations in the install history

M3 - Oct 30, 2009

  • Install wizard improvements (Susan)
  • Query/load assumptions, better async support (Susan)
    • Get rid of deferred tree content manager and the "load is slow, query is fast" assumptions
    • Alternate progress indication during fetch job (redirect to the wizard)
    • incremental fill-in

M4 - Dec 11, 2009

  • Cleanup dead code and formalize wizard page progression in install wizards (Susan)
  • First class support of explanations in UI (Susan)
    • error indicators and quick fix/alternate actions Bug 248959, Bug 267464, Bug 218048, Bug 261928
    • consolidate "empty explanations" with error indicators
    • better consolidation of repo errors (repo empty explanation vs. accumulating repo error indicator)

M5 - Jan 29, 2010

M6 - Mar 11, 2010

M7 - Apr 30, 2010

Back to the top