Bug 102601 - [misc] Improve display and code navigation of decompiled classfiles editor
Summary: [misc] Improve display and code navigation of decompiled classfiles editor
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2005-07-03 20:48 EDT by BenH CLA
Modified: 2012-06-19 12:33 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description BenH CLA 2005-07-03 20:48:59 EDT
Like probably many other Java developers, I often reach the editor screen that 
appears when Eclipse displays a classfile without source code. I think that 
screen's appearance and featureset could and should be improved in some simple 
but effective ways.

1. Layout and appearance: Currently, the screen looks like an error message to 
the unfamiliar - "Source not found" in large font! In truth, there are many 
libraries without source that we have to work with; its not an error and 
shouldnt seem like one. IMO, the most informative text is the classname, so 
that should have the largest font.

Maybe the Attach Source controls should be displayed in a mini-header frame, to 
separate them from the actual classfile display (which would help for point 4 
below).

Secondly, the info is rendered in black and white mono-font, without any 
formatting. This is very diffierent from that nice way that Eclipse can display 
source code structure.

2. Code navigation.The ability to hyperlink across to other symbols should work 
for classfiles exactly as it does for source code. There is no difference 
between them.

3. Find references. It should be possible to find references to symbols defined 
in classfiles, just as can be done in source.

4. Incoming link behavior. When coming into a classfile screen from a hyperlink 
jump, the editor makes no effort to scroll to or select the relevant symbol. It 
can even be off screen. It should highlight the field and place the cursor on 
that line.


5. Copy Text should be supported from the classfile editor view.
Comment 1 Dani Megert CLA 2005-07-04 10:12:28 EDT
>5. Copy Text should be supported from the classfile editor view.
see bug 21904