Community
Participate
Working Groups
When the user disables early startup for a particular plug-in, it may not be apparent to them what functionality they are disabling. Currently we are listening for a property change and displaying a warning to the user when they disable our early startup plugin, but this uses deprecated and internal methods (see attached example). We need a mechanism to let the user know what is being disabled so that they can make an informed choice. This could be implemented programatically in the form of a listener similar to the attached example, but using public API, or this could be accomplished declaratively by enhancing the org.eclipse.ui.startup extension with a description that is displayed as a warning to the user when they disable an early startup plugin.
Created attachment 33996 [details] Simple early startup plugin that warns user if user disables early startup for this plugin This plugin uses internal and deprecated methods to listen for user modifications to early startup. When a change is detected, the user is "warned" (System.out.println in this simple example) so that they can make an informed choice about what they are doing. To see the "warning", launch in runtime workbench and watch the console view in the development workbench.
Just to state the obvious... I'm talking about the user disabling early plugin startup using the General > Startup and Shutdown page in the Eclipse Preferences dialog.
Perhaps it would be sufficient to add a "description" field to an early startup extension that could be shown in the preference pag.e
Reassigning bugs to reflect changes in ownership.
Prakash is now responsible for watching bugs in the [WorkbenchLauncher] component area.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
