Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Equinox/p2/User Interface"
(New page: __TOC__ == Equinox Provisioning UI Overview == == UI Structure == === Admin UI === === Eclipse SDK UI === === Common UI Components === == User workflows == == Milestone plan == [[Category...) |
|||
| Line 2: | Line 2: | ||
== Equinox Provisioning UI Overview == | == Equinox Provisioning UI Overview == | ||
| − | + | Work on the Equinox Provisioning UI is in the very early stages and is currently focused on building a UI that helps the team develop, test, and use the provisioning infrastructure. Thus 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. | |
| + | We call this user interface the '''Admin UI,''' although this is a bit of a misnomer, since we are not building a UI focused on repository administrators or enterprise provisioning administrators. | ||
| + | For M1, the goal was to deliver a UI that allows early adopters to browse the infrastructure, and install/uninstall software into profiles. After M1, work will continue on several fronts. The current UI will continue to evolve as we add function for the team, but we will shift our focus to end-user workflows and defining a provisioning UI that can successfully replace the current Eclipse Update Manager UI. | ||
=== Admin UI === | === Admin UI === | ||
=== Eclipse SDK UI === | === Eclipse SDK UI === | ||
Revision as of 14:40, 6 August 2007
Contents
Equinox Provisioning UI Overview
Work on the Equinox Provisioning UI is in the very early stages and is currently focused on building a UI that helps the team develop, test, and use the provisioning infrastructure. Thus 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. We call this user interface the Admin UI, although this is a bit of a misnomer, since we are not building a UI focused on repository administrators or enterprise provisioning administrators. For M1, the goal was to deliver a UI that allows early adopters to browse the infrastructure, and install/uninstall software into profiles. After M1, work will continue on several fronts. The current UI will continue to evolve as we add function for the team, but we will shift our focus to end-user workflows and defining a provisioning UI that can successfully replace the current Eclipse Update Manager UI.