Community
Participate
Working Groups
In 2.1, Lists, Maps and other collection classes are treated no differently from other objects when represented in the VariablesView. We should investigate an extensible mechanism for providing a more useful representation of Java collection classes. For example, when viewing a HashMap, internal variables such 'loadFactor' & 'hashCode' may not be interesting, and the user may prefer to see the keys & values in a side-by-side fashion without having to drill down into the table of HashMap$Entry objects. Will also investigate whether this can be done in existing VariablesView, or if a new view is required.
Will investigate an approach that enhances the 'details pane'. The idea is to promote this pane to a full-fledged view (as in the hierarchy view). There will be an extension point where an implementation for this view can be contributed for a specific type. By default, the existing String-oriented view will be used for all types that are not otherwise assigned.
*** This bug has been marked as a duplicate of 36942 ***
