Community
Participate
Working Groups
Created attachment 156758 [details] Patch with feature. As of v3.6M5 Eclipse Debug Platform now supports columns in the Expressions view. For java, the expressions view should show the Instance ID and Instance Count columns just as in the variables view. See bug 235646.
It would be nice to be able to implement the feature without implementing the IExpressionManager interface (which is specified as @noimplement). I guess the alternative is to have a content provider that subclasses the ExpressionManagerContentProvier (which is internal...). As is, some columns don't render properly for expressions, since it's the "variable" label provider that renders them, and for expressions they don't appear. This to could be fixed up by having an specialized expression label provider for the Java debugger (and subclassing the internal one).
Created attachment 156983 [details] Support for instance ID and instance count values for expressions. (In reply to comment #1) > It would be nice to be able to implement the feature without implementing the > IExpressionManager interface (which is specified as @noimplement). I guess the > alternative is to have a content provider that subclasses the > ExpressionManagerContentProvier (which is internal...). Not necessarily, the content provider doesn't really need to reference the viewer input. I got rid of the IExpressionManager interface proxy thing in this implementation. > As is, some columns don't render properly for expressions, since it's the > "variable" label provider that renders them, and for expressions they don't > appear. This to could be fixed up by having an specialized expression label > provider for the Java debugger (and subclassing the internal one). This is actually even more complicated. We can't easily override the expression label provider, because there's only one implementation of IWatchExpression, so this patch adds a new provisional API in platform: IExpressionAdapterDelegate. I'm afraid that the whole thing is not very pretty... though it works. On the upside, it should also allow for supplying a custom cell editor for expression value, so that expression values could be modified too. However, this would require some extra work in JDT.
Not planned for 3.6
