Summary: | [variables] Java Detail Formatters bugs and enhancements | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Radek Wikturna <Roderick> |
Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | curtis.windatt.public, Piebandit, schrepfler, scolebourne |
Version: | 3.2 | Keywords: | bugday |
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: | stalebug |
Description
Radek Wikturna
2006-04-21 08:30:10 EDT
Deferred for post 3.2 consdieration. Note that for when using columns in 3.2, you can see type name and instanceid in seperate columns, as well as the detail formatter in the value column. *** Bug 104479 has been marked as a duplicate of this bug. *** Marking as bug day for anyone in the community is interested. Seems like there is interest in the first enhancement, only using detail formatters in the variables view (not the detail pane). #1 is handy, but the priority enhancement for me is #3. I do agree with these enhancements in general, though comment #1 does reduce the priority of issue #2. The use case is DBObjects. I have a detail formatter for all my DBClasses to use the PrimaryKey as the DetailFormatter, but in a list (as with selectWithWhere) it uses the default logic instead of the primary Keys. It would also be nice if it would be possible to apply Detail formatters on annotations (ex. if class is a jaxb annotated class it should be possible to write easy unmarshallers. It would be nice also to have a default eclipse detail formatter but also be able to redefine it per project (and reuse project classpath for instance). Also, detail formatters should be exportable/importable so that their re-use and sharing is easy. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |