It would be useful for various dialogs to invoke the dialog via API in similar way implemented for options.
Added friend contract in rev/3f2fe7a4fa33. It should be reviewed and make as official API soon.
Integrated into 'main-golden', will be available in build *200811041401* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Jiri Rechtacek <firstname.lastname@example.org>
Log: #146153: API providing programmatic way to display Plugin Manager dialog
Reassigning to the new "autoupdate/*" owner dlipin.
I guess I will expose a context sensitive action (sensitive to OperationSupport object) that one will be allowed to invoke with proper context.
I plan to remove the existing friend API.
(In reply to comment #4)
> a context sensitive action (sensitive to OperationSupport object)
Seems odd; is there any use case for this being a context-sensitive action? This would only make sense in case there were e.g. several nodes, each with its own OperationSupport instance, and you wanted to add a context menu to them.
I would rather think that the factory would simply take a OperationSupport parameter (assuming one is needed at all), and return a non-context-sensitive action... or just return void and actually open the dialog, which is what the API currently seems to do (the caller can create an Action wrapper for this if appropriate but might call it some other way too).
Is there anybody who needs such API anyway?
(In reply to comment #6)
> Is there anybody who needs such API anyway?
These definitely use PluginManager today.
Does not seem to exist anymore (and no such dep from dlight.* in current sources).
They may still be using it.
OK, thanks. I don't want to encourage usage of cross cluster friend APIs.
(In reply to comment #7)
> (In reply to comment #6)
> > Is there anybody who needs such API anyway?
> Does not seem to exist anymore (and no such dep from dlight.* in current
Exists in close source part of Solaris Studio IDE group products, part of DLight product
> They may still be using it.
They do use it.
OK, I've contacted com.microchip.mplab representative and started change of the PluginManager into stable API in bug 194518.
*** This bug has been marked as a duplicate of bug 194518 ***