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.
User problem: ----------------------------------- -- User need: ----------------------------------- The user often needs to traverse code via class hierarchy, interface implementation, usages, etc. He would benefit from a tool that allows him to do this fast, and also from a tool that visualizes the object relationships. Product requirement: ----------------------------------- Java structure-based navigation (subclasses/superclasses, usages, ...). The UI of this tool has crucial impact on usefulness of this feature, plain visualization of a class tree hierarchy in a Jtree, where the user needs to click many times to get to the point where he wants to be is probably not going to be too helpful.
Structure part is implemented. Superclasses is implemented. Subclasses part really requires MDR. This issue should be broken out into subtasks based on the different types of view required. Some we already have; MDR based storage is a requirement for a reasonable impl of, e.g., a subclass view. (BTW is there an umbrella issue for MDR/Java integration?) Not evaluating difficulty/hack factor - should be done on a per subtask basis.
Re-assigning Tim's issues to Dafe.
We already have Navigator, which adresses structure and superclasses as Tim said. Subclasses are planned and mentioned is specific enh requests under objectbrowser/navigator. Closing as fixed.