Community
Participate
Working Groups
We have a product that needs the AWT and the SWT event loop to be the same (see Bug 39401). In eclipse 2 we had to patch some code. With eclipse 3 we can simply run our own Application. In M8, IDEApplication was simple enough to copy it. In M9 IDEApplication became more complex and we would prefer to subclass it instead of maintaining a copy. We simply nee two things: - make the class non final - extract the creation of the display into a protected method
Created attachment 11177 [details] Patch for IDEApplication to allow subclassing
*** Bug 64275 has been marked as a duplicate of this bug. ***
I know of other products building on the IDE stack that may want to do something similar. Although we are not prepared to open up IDEApplication as API for 3.0, I've applied the patch under the condition that you will not complain if you get broken by subsequent changes to this internal class <g>. It would also be worth factoring out the workspace prompt and version check code here into separate (internal) classes, to simplify the application class. Moving to Andrew for this, time permitting for RC1.
Thanks! I won't complain about changes, unless there remains a run method ;-). Factoring out the workspace promt would be a good idea....
When the workspace launch prompt is factored out it would be a good idea to think about ways that clients might want to reuse and enhance the dialog. Bug 57440 describes an enhancement that would add a 'More Info' button to provide usage information on past workspaces.
Prakash is now responsible for watching bugs in the [RCP] 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.
