|
|
| (54 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. |
| | | | |
| − | == Milestone plans == | + | == Workflows == |
| − | UI planning information has moved to [[Equinox p2 UI Plan]]
| + | * [[Equinox p2 UM workflows]] summarizes the Eclipse 3.3 Update Manager scenarios |
| − | == Goals of a new Provisioning UI ==
| + | * [[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. |
| − | With the delivery of a new provisioning infrastructure must come a new UI. The following goals have been driving the development of the UI for p2.
| + | * [[Equinox p2 UI 3.5 workflows]] provides mockups for proposed changes in 3.5 |
| − | * Gradual discovery. "The best update UI is no UI." Consider the user of an eclipse-based RCP product in addition to SDK. The update UI should be unobtrusive and the RCP app user shouldn't even have to know about it to get their basic updates and work done. | + | |
| − | * Operate using modeless interaction and background processing to keep from blocking user when performing network operations
| + | |
| − | * Most update functions should be consolidated in a simple "dashboard." Managing the current configuration and looking for what's out there should be better integrated.
| + | |
| − | * Code should be structured so that eclipse-based products can easily extend, reuse, assemble their update UI without having to rewrite.
| + | |
| − | * Notifications and errors reported should be understandable by the user. If something wasn't directly triggered by user, the notification should not interrupt their work. | + | |
| − | * Make it easier for the user who finds something cool via the web to get it into Eclipse
| + | |
| | | | |
| − | == End user workflows == | + | == Design discussions == |
| − | Different workflows drive the development of this UI. The first priority is to deliver the equivalent functionality of the current Update Manager UI. Note that we are not saying we are solving all of these problems. Part of defining the workflow may be saying that we aren't addressing it yet.
| + | * [[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. |
| − | * User is looking for a specific software component to add to their environment | + | * [[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 |
| − | ** Simple install
| + | *[[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 |
| − | *** user browses repositories for software to install/update
| + | |
| − | *** UI precomputes info such as required software, download size/time, etc
| + | |
| − | *** user accepts licenses, etc.
| + | |
| − | ** Install requires updating (or downgrading) of existing components
| + | |
| − | ** Conflicts arise in the requirements for various components
| + | |
| − | * Software updating | + | |
| − | ** User looks for updates of software already installed
| + | |
| − | ** User wants automatic checking/notification of available updates
| + | |
| − | ** Silent/automatic updating, user never sees the update UI, it just happens
| + | |
| − | * User wants to remove a software component from their environment
| + | |
| − | ** Simple uninstall
| + | |
| − | ** Associated uninstall of required software
| + | |
| − | ** How much does the user care about complete rollback (downgrading components that were upgraded by an install, etc.)
| + | |
| − | * User wants to know what software is available for download (browse, search by function or name, etc.)
| + | |
| − | * User's environment is defined explicitly by someone external (administrator)
| + | |
| − | ** Upgrade or install to a new specification
| + | |
| − | ** Compare current installation to required one
| + | |
| − | * User wants to return to some previously known state (rollback to a named state)
| + | |
| | | | |
| − | == How to Run the UI == | + | == Development Plans == |
| − | The update UI (aka the "end user UI") appears as a new menu item '''Software Updates (Incubation)...''' in the help menu of your eclipse application. To include this UI in your eclipse application, you want to include the plug-in '''org.eclipse.equinox.p2.ui.sdk'''.
| + | * [[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 |
| − | There is also an "admin UI" which allows the p2 team to drive the p2 infrastructure in a multi-profile scenario. This UI is also used as the provisioning agent in the current milestone builds. It can appear as either a perspective in your Eclipse workbench, or as a stand-alone RCP app. Since the intention of this UI is to help the team develop, test, and use the provisioning infrastructure, the UI exposes the underlying infrastructure and associated terminology to the end user, which is definitely not the approach we expect to take for end users. To include this UI, you want to get the plug-in '''org.eclipse.equinox.p2.ui.admin''', or else run the RCP version of the app.
| + | |
| − | | + | |
| − | Currently, if you include both UI plug-ins in your launched workbench, or you include the sdk UI in the launch of the RCP app, you can operate the admin UI and still launch the end-user UI using the menu item in the help menu. If you do this, you will notice multiple property pages for repositories and IU's, one with developer/implementation info, and the other with more end-user info.
| + | |
| − | | + | |
| − | ==Plugin Structure==
| + | |
| − | * '''org.eclipse.equinox.p2.ui''' contains code we think is useful for any SWT/JFace-based provisioning UI.
| + | |
| − | ** Content and label providers for showing provisioning objects in views
| + | |
| − | ** View filtering
| + | |
| − | ** Widget groups for creating/editing provisioning objects
| + | |
| − | ** Common drag/drop adapters with pluggable prompting
| + | |
| − | ** Reusable actions and operations for provisioning commands
| + | |
| − | ** Pluggable update and install UI
| + | |
| − | ** Issues not addressed yet
| + | |
| − | *** Evolve the current undo support to use the underlying engine history, not UI-level implementation
| + | |
| − | *** Scalability issues - lazy content providers for repo access (iteration vs. collection)
| + | |
| − | *** consider UI forms vs. dialogs
| + | |
| − | *** Input validators for provisioning info (repo URLs, capabilities, touchpoint types, etc.)
| + | |
| − | *** Automatic checking for available updates with pluggable notification style
| + | |
| − | * '''org.eclipse.equinox.p2.ui.sdk''' contains the update manager replacement UI. You'll see terminology such as "feature" and "site" used in this UI.
| + | |
| − | * '''org.eclipse.equinox.p2.ui.admin''' is the current developer/administrator UI.
| + | |
| − | * '''org.eclipse.equinox.p2.ui.rcp''' is an RCP application of the admin UI | + | |
| − | | + | |
| − | == Tooling issues ==
| + | |
| − | There are issues outside of the scope of end users that are not covered in the end user UI. It's not clear whether these will be added to the Admin UI or whether they are separate tools for builds or publishes.
| + | |
| − | * Repo management
| + | |
| − | ** Create and populate repos
| + | |
| − | ** Manage repo content
| + | |
| − | ** Category definition
| + | |
| − | * Defining and persisting profiles for mass deployment to users
| + | |
| | | | |
| | + | == Testing == |
| | + | * [[Equinox/p2/UI Manual Tests]] contains the UI manual tests |
| | | | |
| | + | == How-to's == |
| | + | * [[Equinox/p2/Adding Self-Update to an RCP Application]] |
| | | | |
| | [[Category:Equinox p2|User Interface]] | | [[Category:Equinox p2|User Interface]] |
This page provides links to the various design and discussion documents surrounding the p2 User Interface.
