Community
Participate
Working Groups
We have sample code (rcp.cloud example) that shows how an RCP app could use the UpdateSingleIUWizard to get a branded update notification. Two problems with this approach: - the wizard itself is internal - if an RCP app decides to use the p2.ui.sdk.scheduler bundle to control automatic updating, then the default update wizard will be used. Both of these problems could be fixed by introducing Policy API to control whether the branded notifier is used. Policy.setUseBrandedUpdateWizard(boolean useBrandedWizard) ProvisioningUI would consult the policy when clients call getProvisioningUI.openUpdateWizard(...) By doing this, the automatic update notifier would just get the correct behaviro for free, as well as the SDK Update Handlers.
I'd like to add this early in 3.7, as this would be the last known policy API needed to completely configure bolt-on update without having to write any code.
another thing to consider here is how the branded update wizard size should be determined. We might want a preference that allows apps to specify the size of the image so that the wizard can be layed out optimally.
these bugs will be my holiday projects...
Fixed in HEAD. The new API on Policy is: get/setUpdateWizardStyle - rather than use a boolean, which locks us into only two styles of presentation, I define constants, which are currently UPDATE_STYLE_MULTIPLE_IUS UPDATE_STYLE_SINGLE_IUS get/setUpdateDetailsPreferredSize - this is used to size the browser that contains the update notification page. RCP Cloud example now reads these values from preferences.
verified through source inspection, I20110124-1800