Community
Participate
Working Groups
As Eclipse grows, so does this problem. It has been brought up before, e.g in bug 15428, and now more recently in bug 136500. If there are multiple plugins, especially from multiple providers, that all have their preferred editor they want to contribute, and they'd all prefer it to be the by default. The solution worked out in bug 15428 is showing its age ... it is no longer feasible to think of "one product wants to override one editor' since, more and more, there can be many plugins installed together and none of them, per se, are "products". And, it would be inappropriate to expect a number of providers to, for example, each declare themselves a 'product', just so they could provide a differnet default editor preference. So, I'd like to re-raise the possibility of the editor manager detecting that there was more than one default declared, and ... prompt the user for which they wanted to be the default? Or ... any other ideas for the problem and issues raised in bug 136500? Note, we in WTP can improve the situation described in bug 136500, since we do have too many unnecessarily using 'default' ... but, we can't really solve the problem for all cases, nor the general problem, so, thought I'd open this bug to request the bright minds of platform UI :) to propose a general solution? Much thanks.
A solution I would prefer: Instead of defining default="true", it should be possible to define default="my.project.type.id". So a WTP XML editor could be the default for an WTP project and an other XML Editor could be default for the other XML files. ... I'm stuck in such a problem, too: I have a custom MANIFEST.MF Editor that can only proceed the manifest files located in a special project type -> I would need to enable the editor for a specific project type only. When I open an plugin MANIFEST.MF file, the default editor should then be used, not my custom one!
*** Bug 167423 has been marked as a duplicate of this bug. ***
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Remy is now responsible for watching the [EditorMgmt] 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.
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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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. -- The automated Eclipse Genie.
