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.
From nbui: ---%<--- Jan Becicka wrote: > From different point of view, the first 3 examples are +- the same. There > are additional groups (methods, fields, constructors) in NB. What about let > user to choose, if he want to see members directly under class, or not. > Advantage of the first 3 examples is tree depth... It's a good point. I have often heard users complain about the excessive nesting in NB's view. Who wants to expand several levels of nodes? I would vote to at least have an option to (1) skip the category nodes like Fields (could still sort all fields together, maybe); (2) put members of the top-level class directly beneath the data node: 99% of all Java classes do not have more than one top-level class, this is an ugly 1.0-ism which NetBeans does not even support by default anyway, and it is annoying to have to expand the outer class node just to see its members, even if this is logically correct.
Isn't this the same as issue 6992?
Looks that way. *** This issue has been marked as a duplicate of 6992 ***
Resolved for 3.4.x or earlier, no new info since then -> closing.
Reorganization of java component