Please use the Apache issue tracking system for new NetBeans issues ( !!

Bug 211784

Summary: UI review of the inspect hierarchy dialog
Product: java Reporter: David Strupl <dstrupl>
Component: NavigationAssignee: Tomas Zezula <tzezula>
Status: RESOLVED FIXED QA Contact: issues <>
Priority: P3 CC: pjiricka, psomol, tmysik, tzezula
Version: 7.2Keywords: PERFORMANCE, UI
Target Milestone: 7.3   
Hardware: All   
OS: All   
Issue Type: DEFECT Exception Report:
Bug Depends on:    
Bug Blocks: 99978    

Description David Strupl 2012-04-26 13:15:34 UTC
The inspect hierarchy dialog functionality overlaps with Navigator and also with the new Go TO implementation functionality.

This task is to review the use cases and flow when the user wants to navigate to the type hierarchy and jump to the desired class in the code.
Comment 1 Tomas Mysik 2012-04-27 11:55:46 UTC
Let me describe my - unfortunately quite bad - experience with the Inspect hierarchy dialog. My task was to study quite a lot of classes from a few Spring libraries. So, I needed easily to review:

- Javadocs of classes, methods etc., and
- type hierarchy.

Unfortunately, none of these tasks is as easy as in Eclipse, for example. Try to open any Interface from any library (some jar file) - if one wants to see all descendant or implementations, Find Usages does not help here (it returns no results). If one opens the Hierarchy window, it is not docked so if one wants to see source code of any of its element, it is quite difficult (the dialog is not modal so one can double-click an element, "hide" the window, review the code, "open" the window, double-click other element, "hide" the window and so on).

So, the problems I see are:
- it is a standalone window (why? IMHO it should behave exactly like e.g. Projects, Navigator, Files, ...)
- it takes ages to get the type hierarchy (Eclipse is nearly instant, really)

Comment 2 Petr Jiricka 2012-05-21 11:31:26 UTC
I think inspecting type hierarchy and associated Javadoc is such a common use case, that we should try to make some improvements for 7.2, even if we don't have the complete solution for 7.2. As 7.2 is a performance release, it would be good to at least analyze and improve the performance of this feature. 

Also, per and based on Tomas's experience I think this is really a (usability and performance) defect, not an enhancement. Maybe even a P2.
Comment 3 Tomas Zezula 2012-05-21 12:00:38 UTC
The inspect hierarchy dialog was a community contribution. It it was able to block EDT for minutes which is now at least rewritten to be out of EDT and cancelable. Even it's possible to speed it up (but it's not very easy due to the current design - it's O(exp(n))). I don't want to spent any time with it until there is a final UI spec. As far as I know the current inspect hierarchy dialog will be removed from the next version and replaced by something which is not even designed. So any work on it is useless as there is not much to be reused in it.

Maybe we don't even need it and it should be just a view in current Navigator or it should be a top component which can be docked somewhere. I don't know. But I don't think that such an UI change is doable in NB 7.2.
Comment 4 Petr Jiricka 2012-05-21 12:03:18 UTC
Ok, fair enough.
Comment 5 Tomas Zezula 2012-08-16 11:39:22 UTC
Fixed jet-main 393a703b5b49
Comment 6 Quality Engineering 2012-08-21 15:08:51 UTC
Integrated into 'main-golden', will be available in build *201208211308* on (upload may still be in progress)
User: Tomas Zezula <>
Log: #211784:UI review of the inspect hierarchy dialog
By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo