7330 screen real estate winners and losers

As I was thinking about the find bar UI, I realize one important criteria to evaluate new Editor features is how do they affect screen real estate.

Here are some screen real estate winners and losers for Selena. Please add more if you can think of them.

Screen Real Estate WINNERS____________________________

    • Build->Make Project with "Compile in Background" enabled doesn't pop up the Messages panel if there are no

errors.*

Since 99% of time there are no compile errors, esp. when doing incremental compiles, this is a big improvement.

How to make it better:

I'm waiting for the same feature for Ant target execution (http://www.jetbrains.net/jira/browse/IDEA-14881) I haven't
tried Maven pom.xml with IDEA 7.0. Does that also need the same treatment?

Also there is a request to add an option "Run in background" for Run Configurations (http://www.jetbrains.net/jira/browse/IDEA-14883) This would also you to avoid having the Messages window popup for GUI programs, etc. where you don't care about the output window.

    • Show Usages*


Show usages is like Find Usages except it shows the usages in a popup window inside the Editor pane rather than
showing the Find tool window. If there is only one usage, it jumps directly to it which is really slick. There are
some rough edges to this feature and it doesn't work well in certain use cases, e.g. if there are a bunch of usages
and you want to step throuch each one of them, but the advantage is you don't have to Close or pop down the Find tool
window to regain your Editor real estate. I have Show Usages mapped to CTRL+U and Find Usages relegated to
CTRLSHIFTU for a few weeks now, and so far the good is outweighing the bad for me.

+ How to make it better:+

If Show Usages can be improved so it can handle the case of stepping through all usages, e.g. somehow making Next
Occurrence and Previous Occurrence keybindings work even though the usages aren't displayed in the active tool window,
then we might be able get to the point were you can use Show Usages for all cases. Also, does it make sense to do
something similar for Find in Path or just a Find All in current file. It might be nice if while in Find or
Incremental Find mode, if you hit another key then all the matches would be shown in a popup list similar to Show
Usages. Another idea: Find shows "x matches" at the right-hand-side of the find bar. You could add an accelerator to
Matches so hitting ALT+M would popup a list of all the matches.

    • Inspection - Fix all 'x' problems*


Now when you see a much of the same warning in a file you can fix them all by hitting ALT+ENTER,RIGHT_ARROW, select
'Fix all 'x' problems, ENTER.

Before, you would have to run Inspect->Analyze Code which would show an Inspections Results tool window, which you had
to Close or pop down to regain your Editor real estate.

How to make it better:

I'm waiting for Code->QuickFix/Cleanup Code (http://www.jetbrains.net/jira/browse/IDEADEV-17781) so I can run a bunch
of quickfixes in a few key presses/clicks and also SRRS's Inspector General's Rationalize Control Flow / Normalize Code
feature has great potential, esp. if Jetbrains can pay them to roll it into IDEA V.NEXT. (See
http://www.sixthandredriver.com/inspectorgeneral.html)

Screen Real Estate LOSERS_______________________________

  • XML/JSP/HTML bread crumbs bar.] If you don't want it, then this sucks up valuable real estate right under the

editor tabs.

How to make it better:

It should be possible to turn "xml/html bread crumbs" feature off
http://www.jetbrains.net/jira/browse/IDEADEV-14992

(I can't believe this hasn't been fixed before Selena release. Really, you should just disable this feature altogether
if you can't add an option to turn it off. I bet more than 50% of people working on J2EE find this thing annoying.)

    • Inline Find Bar*


The new inline find bar doesn't cover up your editor screen like the old find dialog, but.. once you started searching
the old find dialog was gone, whereas this inline find bar sticks around while you search. What's worse is if you click
away without hitting ESCAPE first, the find bar stays put unless you X it out.

How to make it better:
Find bar should be disposed as soon as the search box loses focus.
http://www.jetbrains.net/jira/browse/IDEA-15600

3 comments

You can cancel the find bar and still sequence through matches with F3.

RRS

0

+I can't believe this hasn't been fixed before Selena release. Really, you should just disable this feature altogether
if you can't add an option to turn it off. I bet more than 50% of people working on J2EE find this thing annoying.+

+1

0

+1 for the ability to disable it

0

Please sign in to leave a comment.