Bugzilla – Full Text Bug Listing
| Summary: | [ui] Ability to hide 'Available Software' tab | ||
|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Claus Klammer <claus.klammer> |
| Component: | p2 | Assignee: | Susan McCourt <susan> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | contact, susan |
| Version: | 3.4 | ||
| Target Milestone: | 3.5 M4 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Claus Klammer
Claus, do you think hiding the tab is sufficiently useful for RCP applications? Note you can also upgrade or revert the installation from the "Installed Software" tab. This entire install/update UI is not part of the RCP feature, so RCP applications can simply choose not to include it, possibly providing their own simple update user interface if desired. I've to agree providing our own update/install UI would avoid this issue. But since hiding the tab would fit our current requirements perfectly, and propably those of other RCP developers too, I would highly appreciate this enhancement. Our goal is to control which plugins are installed. Therefore we want to preconfigure the available software repositories with 'the one and only' repo allowed. And in addition to prevent the user to add additional repositories the 'Available Software' tab should be hidden. In my point of view this scenario seems to be useful for others too, don't you think so? marking 3.5 milestone. We are looking at the workflows in the 3.4 UI and considering alternatives...some ideas include: - separate available view as separate user action (browse for software...) - integrate install view with about view In the context of this happening, we intend to look at various controls that apps want on allowing the user to add software at all. See also bug #236740 (which I will use to track changes to the overall workflow/user entry points to the UI) and bug #234213 comment #4. I think something will happen in this space, still working on it. If you want to track progress, please cc: yourself also to bug #236740. This will happen as a result of new workflows (see bug #236740) and then separation of contributions from the code base (see bug #221760) I believe we can consider this bug fixed. With the new workflows introduced in M3, we now have put the "available software" view in the Install wizard. This wizard is invoked by the SDK's (org.eclipse.equinox.p2.ui.sdk) menu contribution for "Install New Software...". In an RCP application where users can update but not install new software, you can replace org.eclipse.equinox.p2.ui.sdk with your own bundle that contributes the function as you see fit. For example, you could contribute a menu item to check for updates but not one that invokes the install wizard. You'll also want to examine the preferences surfaced by p2.ui.sdk and determine if you want to surface any of those preferences to your users. You can look at ProvSDKUIActivator to see how the preferences influence the policy used by the various wizards. If you wish to reuse the sdk's automatic update functionality, you can configure your RCP product with the org.eclipse.equinox.p2.ui.sdk.scheduler bundle. If you wish automatic update preferences to appear underneath your RCP update preferences, you'll want to use the same preference page ID as used by org.eclipse.equinox.p2.ui.sdk verified on WinXP, Build id: I20081209-0100 through source inspection. Examples will come in M5 and M6. |