Community
Participate
Working Groups
I am creating an Eclipse based product that is actually smaller than Eclipse SDK itself -- it consists of RCP + Text Editor + other plug-ins. I am also using the org.eclipse.ui.ide bundle because otherwise I would have to duplicate a lot of the functionality. But I need some customized behavior whenever a workspace external file is opened (= IDE.openEditorOnFileStore() is called). Actually, I only would need to execute these lines in the middle of the IDE.getEditorInput(IFileStore) method: ... if (workspaceFile == null) { workspaceFile = WorkspaceFileLinker.getDefault().linkFile(fileStore); } ... What this does is create a new link for any file that is not already linked to the workspace, so that any files opened can enjoy all the workspace dependent facilities such as local history. Maybe this would be called "File Store Opening Strategy" or something like that. Could something like this be created for extenders to (ab)use? If not, then can you recommend a best practice for replacing that part of the IDE? I can't do it in a fragment, can I? Maybe AspectJ is a solution?
I'm willing to help, but I'm not sure how to solve this. An extension point would probably be too much for this single feature? You probably don't want to litter the platform with extension points for small things like this? But I'm not aware of any other nice ways extensions/replacing functionality could be made. What about an extension point that allows several IDE behaviors to be replaced? For example an extension point called "IDE Adapter" that would come with one interface / abstract class that has API to do this.
Could you not just do this with a command? If we moved the action you are concerned about to a command you could just bind it to a different handler. I don't think we want to add new mechanisms if we could avoid it.
"As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009"
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.
