Community
Participate
Working Groups
M4 We have many situations where people want to use our resource based APIs but cannot due to a required dependency on the IDE application. Likewise we have code in the IDE that would like to use other plug-in but cannot due to a circular dependency (specifically the Common Navigator requires the resource parts of the IDE so we can't use it in the IDE without the circular dependency). Looking at the code in IDE the vast majority of it could be moved to a resources based plug-in with only a small amount left in IDE to support the IDE application and the Resource Perspective. This would allow 1) RCP apps to use our views like the Problems View with thier own application. Right now many are forced to subclass our (internal) application class to get this to work. 2) The resource navigator to rely only on the new org,eclipse.ui.workbench.resources plug-in thereby allowing the IDE to refer to it.
(In reply to comment #0) > Looking at the code in IDE the vast majority of it could be moved to a > resources based plug-in with only a small amount left in IDE to support the IDE > application and the Resource Perspective. I thought about this, and if there are no API problems, I believe we should do the following: - Create a new plug-in org.eclipse.ui.ide.application. - Move the IDE application and supporting classes into the new plug-in (assuming none of them are API). - Fix some of the problems that people have when trying to use org.eclipse.ide without running or subclassing the IDE application class. This would solve the cyclic dependency problem, and eventually, make org.eclipse.ui.ide a plug-in like any other.
+1 for Boris's suggestion.
+1.
Created attachment 56647 [details] Patch to IDE and SDK
Created attachment 56648 [details] org.eclipse.ui.ide.application Coupled with the attached patches this will fix Bug 155299, Bug 164108 and this bug. I will release this as soon as the PMC gets the new project added
Patch and new plug-in released for build >20070109
platform feature updated with new org.eclipse.ui.ide.application plugin.
Note that this change can break existing clients, e.g. a client that currently only requires 'org.eclipse.ui.ide' and doesn't provide its own application. Did you discuss and accept that breakage? Maybe a better solution would have been to extract the non-application part into its own plug-in (e.g. 'org.eclipse.ui.ide.base' or 'org.eclipse.ui.resources') and let 'org.eclipse.ui.ide' require that one and re-export all its APIs. Thoughts?
Verified in 20070206-0010
Bug 172517 has reverted the application id to org.eclipse.ui.ide.workbench. What about Dani's concerns from comment 8? Did you add this to the 3.3 porting guide as a breaking change?
