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.
| Summary: | While editing source code, would like a way to quickly see high-level view of class | ||
|---|---|---|---|
| Product: | editor | Reporter: | eakle <eakle> |
| Component: | -- Other -- | Assignee: | issues@editor <issues> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | blocker | CC: | bht, jeri |
| Priority: | P3 | ||
| Version: | 3.x | ||
| Hardware: | PC | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
| Bug Depends on: | 35583 | ||
| Bug Blocks: | |||
|
Description
eakle
2002-02-04 17:57:54 UTC
Set target milestone to TBD Set target milestone to TBD A possible way of implementing this would be to give the explorer a "Go to" function. This function would accept a kind of URL that could be clear text and be valid throgh the whole netbeans system. Any GUI e.g. source editor would provide this URL from "self" by copying it to the clipboard. Likewise any GIU would consume this URL from the clipboard. The clipboard becomes the hub that resolves the many-to-many relationship of this "Go to" issue. Without such a hub, it is very complex to present the user with all the options in every GUI. In other words, any GUI has to know what other applications exist that coule open "this" (the currently open object or file) via the suggested "Go to" function. In Windows 95/NT, there is a explorer utility "Send to X" that selected files as a list of file names to the clipboard. Linux KDE solves this even more elegantly via the copy function [Ctl+C] etc. So if you copy a file in KDE what you get when you paste depends on what the application can handle. If you paste in a notepad you get a list of file names, if you paste in Konqueror then you get the files moved/copied. Netbeans should have this too IMHO. It's very smart. On second thought, I think it would be nice if the behavior of this menuitem could be sensitive to where you are in the source file (if that's feasible). For example, if I'm positioned in method "foo" in the source editor, and I select this GoTo/Jump menuitem, then it would open the explorer down to the methods in that class and position me on "foo". If it's possible to do this, then it would be a useful behavior. I'm wondering whether your original issue would be covered by the code folding that will appear in 4.0. There should certainly be an action that would fold all the method bodies so that you would just see the skeleton of the class (fields, method signatures, inner classes skeletons). code folding will be nice and what is described above should offer a useful way to navigate within a file. I still think that providing a way to navigate to the explorer is useful though, even with code folding for 2 reasons: 1. MDR should allow Netbeans to support rapid navigation from the current class to other related classes (superclass, subclasses, etc. -- see issue 25863); these navigations will likely operate from a high-level view of the class, as in the explorer or other yet-to-be-written workshop. So I would like a way to jump from the source editor to the place where navigations can begin for the current class. 2. It's really nice to have both the high- level view of a class (explorer) and the detailed view (source code) on display at the same time. That lets me click a method in the high-level view and see its source code in the detail view; that has better useability than having to fold all the code (losing the detail view), click a method and then unfold the code (losing the high- level view). So, code folding will be great, but I don't think it covers the need for jumping between the high-level and detail views of a class. Works for me. I think the original issue is coverd with the new feature Menu|Window|Select Document in|File Systems[Ctrl+Shift+2]/Project[Ctrl+Shift+3]. This is a very useful feature. |