Community
Participate
Working Groups
Hi, This is just an idea How about having a view called contributors view. The major user for this view will be extension point developer.He can configure the view such that the contributors of his extension points are listed in runtime. This view as mentioned has to be configured with the extension point id and once configured the view gets generated and shows the contributors. For e.g. in case of builders a 'builders' view will be generated listing down the builders. Obviously this will be upto the discretion of the extension point creator to use this view or not. This is just an idea, please provide you suggestions ,comments or if you thing this does not make sense at all :). I can anticipate one problem if everyone starts to use it then hell lot of views will be generated but it can be useful.Because we often have this requirement,need for debug to find out the contributors. cheers, Saurav
It sounds like you are just reimplementing the search functionality. If you want to see all of the places where plug-ins are contributing to an extension point, you can run a search to find references. This is available through the search dialog and in the context menu of an extension point in the plugin editor.
(In reply to comment #1) > It sounds like you are just reimplementing the search functionality. If you > want to see all of the places where plug-ins are contributing to an extension > point, you can run a search to find references. This is available through the > search dialog and in the context menu of an extension point in the plugin > editor. Well yes but my point is little different in the below points. (a) User doesnt have to go through opening the extension point editor or knowing about the id in the search dialog.It will be an out of the box support. (b) Sometimes as an end user i might want to see what all contributions (read functionality here) are supported in a particular IDE. For example we work on some backend and each type of backend can contribute a specific functionality to the framework code.So having this view can also help me to tell what all backend are supported. cheers, Saurav
(In reply to comment #2) > (a) User doesnt have to go through opening the extension point editor or > knowing about the id in the search dialog.It will be an out of the box support. The user would still need to know the id of the extension point to filter the view. > (b) Sometimes as an end user i might want to see what all contributions (read > functionality here) are supported in a particular IDE. The only information PDE has to work with is the id and contributor of the extension. This is the same information a search would return. PDE cannot provide more detailed UI. It sounds like creating a custom plug-in would solve your problem more effectively. A simple view that would search for all extension points contributing a backend and then displaying them in some helpful format. I'm not seeing the value of a general solution being added to PDE. Also note that the view would not be included in the perspective by default unless it was shown to be very popular.
(In reply to comment #3) > (In reply to comment #2) > > (a) User doesnt have to go through opening the extension point editor or > > knowing about the id in the search dialog.It will be an out of the box support. > The user would still need to know the id of the extension point to filter the > view. Well, what i meant was the extension point developer creates the view for his extension point.The functional users not necessarily aware of the extension point get to know the contributions ( contributed functionality) in the view. > > (b) Sometimes as an end user i might want to see what all contributions (read > > functionality here) are supported in a particular IDE. > The only information PDE has to work with is the id and contributor of the > extension. This is the same information a search would return. PDE cannot > provide more detailed UI. It sounds like creating a custom plug-in would solve > your problem more effectively. A simple view that would search for all > extension points contributing a backend and then displaying them in some > helpful format. > I'm not seeing the value of a general solution being added to PDE. Also note > that the view would not be included in the perspective by default unless it was > shown to be very popular. I agree ,but i am not sure if PDE is the right candidate is for this.I can think this of more of a functional view rather an any tooling view :). cheers, Saurav
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. If the bug is still relevant, please remove the "stalebug" whiteboard tag.
