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 Galileo Features"
(→User Interaction) |
(→User Interaction) |
||
| Line 32: | Line 32: | ||
; '''Tighter desktop integration''' | ; '''Tighter desktop integration''' | ||
| − | : Provide ways to better integrate an Eclipse based application with the desktop (e.g. desktop shortcuts, registry keys...) | + | : Provide ways to better integrate an Eclipse based application with the desktop (e.g. desktop shortcuts, registry keys...). Priority: 1. |
Revision as of 10:22, 4 September 2008
This page highlights the features and function available to end-users in p2 Galileo. The general themes for this release are robustness, ease of use, more direct value-add to our users, and be a better platform. Readers interested in additional under the covers details should see the ????? and also bugzilla
User Interaction
- Improve overall usability
- Review the overall usability of the current UI. See also p2 UI plan. Priority: 1.
- Improve the error messages provided in case of inability to install. Priority: 1.
- Allow for selection of the optional pieces. Priority: 2.
- Better shared install
- Improve the management of shared installs to allow for the end user to not lose the extensions installed. Priority: 2.
- Browser-based installation
- Installation of new function can be triggered by users clicking on a link in a browser. Priority: 2.
- Closer integration with the VM
- Provide a way to change the VM being used by Eclipse through the UI and thus trigger the appropriate provisioning actions. Priority: 1.
- Ease the installation of extension and bridges plug-ins
- Ease the management of complementary items
- Provide a way to change language in the UI (and always automatically install the language pack)
- Provide a way to install doc automatically when available
- Provide a way to install source for the installed bundles
- Installation duplication
- Provide a way to create a new install from the existing one. Priority: 2.
- Promote the usage of an installer
- In order to promote bundle pooling, we need to promote the usage of an installer and make it more robust than it is today. Priority: 1.
- Tighter desktop integration
- Provide ways to better integrate an Eclipse based application with the desktop (e.g. desktop shortcuts, registry keys...). Priority: 1.