This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Product Version: NetBeans IDE Dev (Build 071105) Java: 1.6.0; Java HotSpot(TM) Client VM 1.6.0-b105 System: Linux version 2.6.20-16-generic running on i386; UTF-8; en_US (nb) Userdir: /tmp/ud -------------- can be considered as RFE - have a javaapplication (main project), some java sources opened in editor, and besides some ruby project opened - invoke Go To Type dialog - i see the some ruby types (i'm not actually interested in those, since i'm currently editing java sources)
I think this works precisely as designed; it currently scans all open projects. When working on NetBeans I definitely wouldn't want only the current project to be scanned since I'm typically jumping from one class in one module to another. Even for mixed language development (Ruby and Java) I may have a reference to a Java class in my Ruby project that I want to go look up over in the Java projects. The point is that I have both projects open at the same time, so it's quite plausible that I'm working on both and need to jump between them. One thing we -could- do is do something similar to the "Go To File" dialog where matches in the current project are sorted to the top and shown with a different background highlight (green). This behavior is up to the Open Type dialog and infrastructure itself, not a type provider like the Ruby module, so reassigning to the category for this dialog (utilities/jumpto).
Yes, the original report is nonsense. However the check box should be there if not for anything else than for the consistence with go to type.
I would find this item useful in that I only want to see the types that I have created; I have no desire to see the types located in the JDK jar files or even in the jars within my "lib" folder. It might be useful to see these types sometimes, but not 99% of the time.
there should definitely be an option to not show classes from libraries. I work on a large project with 3800 java source files _and_ it uses about 75 3rd-party libraries. 99% of the time, I could care less about the thousands of classes that are in the 3rd-party libraries - but they continuously get in the way when I try to find one of our own. Less importantly, I also would like the option to hide classes that are not in the *main* project. Sometimes, we have to work on multiple releases of the above-mentioned project. Most of us set these releases up as distinct Netbeans (or Eclipse) projects. As a result, when I do ctrl-o, I would see the same class multiple times. Whatever is done, it should persist across NB restarts.
Another thought: why not combine "Go to Type" with "Go to File" into a single dialog that lets you choose what you want to see? Seems like "Go to File" is already a superset of "Go to Type" - with the exception of it not showing 3rd-party library classes?
I agree. I think this should definitely be improved upon. I find myself using jEdit's openIt plugin for jumping to files more frequently, due it its configurability.
Later
"The bugs reported via report exception or with votes/duplicates can't be resolved as LATER". Reopening.
Reassigning to utilities/jumpto owner
I've noticed that this discussion is actually about adding the "Scope" options to the "Go to Type" dialog. It is the same as in the "Find in Projects" dialog (Ctrl+Shift+F), but with scopes that are specific for the types. We need have clear specification for this feature. It should be addressed to the next release.
See another viewpoint on this issue in the Bug 188834. I'll close this bug. *** This bug has been marked as a duplicate of bug 188834 ***