Comments on: Plug-in Development Tip http://aniszczyk.org/2008/04/22/plug-in-development-tip/ work. life. open source. diatribes. Thu, 02 Sep 2010 21:30:00 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Robert Konigsberg http://aniszczyk.org/2008/04/22/plug-in-development-tip/comment-page-1/#comment-760 Robert Konigsberg Wed, 30 Apr 2008 16:16:00 +0000 http://aniszczyk.org/2008/04/22/plug-in-development-tip/#comment-760 Nice, thanks. Nice, thanks.

]]> By: Robert Konigsberg http://aniszczyk.org/2008/04/22/plug-in-development-tip/comment-page-1/#comment-2848 Robert Konigsberg Wed, 30 Apr 2008 16:16:00 +0000 http://aniszczyk.org/2008/04/22/plug-in-development-tip/#comment-2848 Nice, thanks. Nice, thanks.

]]> By: Chris Aniszczyk (zx) http://aniszczyk.org/2008/04/22/plug-in-development-tip/comment-page-1/#comment-747 Chris Aniszczyk (zx) Wed, 23 Apr 2008 11:16:00 +0000 http://aniszczyk.org/2008/04/22/plug-in-development-tip/#comment-747 Eugene, we may be doing an ugly trick, but it is a very useful trick. It has worked for many people for a long time :)<br/><br/>Yuri, that's just from experience. One straight people do is simply select everything in the plug-ins view and add it to java search... but I don't really recommend that approach. Usually, you're only interested in the plug-ins you're developing against (eg., EMF)<br/><br/>Martin, that is an interesting question. JDT UI has a concept of Type Filters that you can apply to that dialog. However, I don't think there is anything that will help you just browse by EE... however, that would be a very reasonable enhancement reques to be raised against JDT UI. Eugene, we may be doing an ugly trick, but it is a very useful trick. It has worked for many people for a long time :)

Yuri, that’s just from experience. One straight people do is simply select everything in the plug-ins view and add it to java search… but I don’t really recommend that approach. Usually, you’re only interested in the plug-ins you’re developing against (eg., EMF)

Martin, that is an interesting question. JDT UI has a concept of Type Filters that you can apply to that dialog. However, I don’t think there is anything that will help you just browse by EE… however, that would be a very reasonable enhancement reques to be raised against JDT UI.

]]> By: Chris Aniszczyk (zx) http://aniszczyk.org/2008/04/22/plug-in-development-tip/comment-page-1/#comment-2847 Chris Aniszczyk (zx) Wed, 23 Apr 2008 11:16:00 +0000 http://aniszczyk.org/2008/04/22/plug-in-development-tip/#comment-2847 Eugene, we may be doing an ugly trick, but it is a very useful trick. It has worked for many people for a long time :)Yuri, that's just from experience. One straight people do is simply select everything in the plug-ins view and add it to java search... but I don't really recommend that approach. Usually, you're only interested in the plug-ins you're developing against (eg., EMF)Martin, that is an interesting question. JDT UI has a concept of Type Filters that you can apply to that dialog. However, I don't think there is anything that will help you just browse by EE... however, that would be a very reasonable enhancement reques to be raised against JDT UI. Eugene, we may be doing an ugly trick, but it is a very useful trick. It has worked for many people for a long time :) Yuri, that’s just from experience. One straight people do is simply select everything in the plug-ins view and add it to java search… but I don’t really recommend that approach. Usually, you’re only interested in the plug-ins you’re developing against (eg., EMF)Martin, that is an interesting question. JDT UI has a concept of Type Filters that you can apply to that dialog. However, I don’t think there is anything that will help you just browse by EE… however, that would be a very reasonable enhancement reques to be raised against JDT UI.

]]> By: Martin Oberhuber http://aniszczyk.org/2008/04/22/plug-in-development-tip/comment-page-1/#comment-745 Martin Oberhuber Tue, 22 Apr 2008 20:34:00 +0000 http://aniszczyk.org/2008/04/22/plug-in-development-tip/#comment-745 Nice. Does it also work the other way round? - My workspace has lots of projects associated with different Execution Environments, and my Preferences actually have those. So when I Ctrl+Shift+T e.g. "String" I get matches from JDK 1.6, 1.5, 1.4, and J9 Foundation-1.1 ... opening all those Classpaths kills my Performance for Ctrl+Shift+T.<br/><br/>Can I disable some classpaths from Ctrl+Shift+T? Nice. Does it also work the other way round? – My workspace has lots of projects associated with different Execution Environments, and my Preferences actually have those. So when I Ctrl+Shift+T e.g. “String” I get matches from JDK 1.6, 1.5, 1.4, and J9 Foundation-1.1 … opening all those Classpaths kills my Performance for Ctrl+Shift+T.

Can I disable some classpaths from Ctrl+Shift+T?

]]> By: Martin Oberhuber http://aniszczyk.org/2008/04/22/plug-in-development-tip/comment-page-1/#comment-2846 Martin Oberhuber Tue, 22 Apr 2008 20:34:00 +0000 http://aniszczyk.org/2008/04/22/plug-in-development-tip/#comment-2846 Nice. Does it also work the other way round? - My workspace has lots of projects associated with different Execution Environments, and my Preferences actually have those. So when I Ctrl+Shift+T e.g. "String" I get matches from JDK 1.6, 1.5, 1.4, and J9 Foundation-1.1 ... opening all those Classpaths kills my Performance for Ctrl+Shift+T.Can I disable some classpaths from Ctrl+Shift+T? Nice. Does it also work the other way round? – My workspace has lots of projects associated with different Execution Environments, and my Preferences actually have those. So when I Ctrl+Shift+T e.g. “String” I get matches from JDK 1.6, 1.5, 1.4, and J9 Foundation-1.1 … opening all those Classpaths kills my Performance for Ctrl+Shift+T.Can I disable some classpaths from Ctrl+Shift+T?

]]> By: Eugene Kuleshov http://aniszczyk.org/2008/04/22/plug-in-development-tip/comment-page-1/#comment-744 Eugene Kuleshov Tue, 22 Apr 2008 18:23:00 +0000 http://aniszczyk.org/2008/04/22/plug-in-development-tip/#comment-744 I also agree with Yury. PDE is doing somewhat ugly trick and creates hidden "External Plug-in Libraries" project in order to trick the Open Type dialog. But I talked to JDT guys and they said that there is now better API that could be used to plug-in custom sources into the search engine and there is also new extension point for quick fix for missing types/jars. I also agree with Yury. PDE is doing somewhat ugly trick and creates hidden “External Plug-in Libraries” project in order to trick the Open Type dialog. But I talked to JDT guys and they said that there is now better API that could be used to plug-in custom sources into the search engine and there is also new extension point for quick fix for missing types/jars.

]]> By: Eugene Kuleshov http://aniszczyk.org/2008/04/22/plug-in-development-tip/comment-page-1/#comment-2845 Eugene Kuleshov Tue, 22 Apr 2008 18:23:00 +0000 http://aniszczyk.org/2008/04/22/plug-in-development-tip/#comment-2845 I also agree with Yury. PDE is doing somewhat ugly trick and creates hidden "External Plug-in Libraries" project in order to trick the Open Type dialog. But I talked to JDT guys and they said that there is now better API that could be used to plug-in custom sources into the search engine and there is also new extension point for quick fix for missing types/jars. I also agree with Yury. PDE is doing somewhat ugly trick and creates hidden “External Plug-in Libraries” project in order to trick the Open Type dialog. But I talked to JDT guys and they said that there is now better API that could be used to plug-in custom sources into the search engine and there is also new extension point for quick fix for missing types/jars.

]]> By: Michael Scharf http://aniszczyk.org/2008/04/22/plug-in-development-tip/comment-page-1/#comment-743 Michael Scharf Tue, 22 Apr 2008 17:59:00 +0000 http://aniszczyk.org/2008/04/22/plug-in-development-tip/#comment-743 This is one of the things we let our participants of the <a HREF="http://www.eclipsecon.org/2008/?page=sub/&id=429" REL="nofollow">RCP tutorial</a> run into.<br/><br/>The interesting thing is that "old" eclipse users expect to see all classes from all plugins in the "Open Type..." dialog. It used to be that way until eclipse 3.1 or so... This is one of the things we let our participants of the RCP tutorial run into.

The interesting thing is that “old” eclipse users expect to see all classes from all plugins in the “Open Type…” dialog. It used to be that way until eclipse 3.1 or so…

]]> By: Michael Scharf http://aniszczyk.org/2008/04/22/plug-in-development-tip/comment-page-1/#comment-2844 Michael Scharf Tue, 22 Apr 2008 17:59:00 +0000 http://aniszczyk.org/2008/04/22/plug-in-development-tip/#comment-2844 This is one of the things we let our participants of the <a href="http://www.eclipsecon.org/2008/?page=sub/&id=429" rel="nofollow">RCP tutorial</a> run into.The interesting thing is that "old" eclipse users expect to see all classes from all plugins in the "Open Type..." dialog. It used to be that way until eclipse 3.1 or so... This is one of the things we let our participants of the RCP tutorial run into.The interesting thing is that “old” eclipse users expect to see all classes from all plugins in the “Open Type…” dialog. It used to be that way until eclipse 3.1 or so…

]]>