all warning panel...

Here my proposals to implement in next version of "IntelliJIdea" :


a) To have a panel where you can navigate all warnings and errors in your application...like your "TODO_panel" or the "ALL_PROBLEMS_panel" in "the old" visual age for java 3.5

b) To make so that when the user moves to a different class/file on rigth panel AUTOMATICALLY sinchronize "project panel" with focus on the class on which the user has moved and "structure panel" with focus on the class-method on which the user has moved.

c) When you are editing a class with a main method make so that class came the Application to run (automatically)

8 comments
Comment actions Permalink

It's not everything you want, but "Autoscroll from Source" in the Structure
panel will cause the focus within that panel to track the cursor position
w/in the editor panel.

"Antonio Ballerini" <antonio.ballerini@mailcity.com> wrote in message
news:2424722.1037868349881.JavaMail.jrun@is.intellij.net...

Here my proposals to implement in next version of "IntelliJIdea" :

>

>

b) To make so that when the user moves to a different class/file on rigth

panel AUTOMATICALLY sinchronize "project panel" with focus on the class on
which the user has moved and "structure panel" with focus on the
class-method on which the user has moved.
>



0
Comment actions Permalink

b) To make so that when the user moves to a different class/file on rigth panel AUTOMATICALLY sinchronize "project panel" with focus on the class on which the user has moved and "structure panel" with focus on the class-method on which the user has moved.


But make it optional! J++ had such a feature and I daily needed to
spend a lot of time to collapse all the expanded package nodes in our
mid-sized project.

Tom

0
Comment actions Permalink

c) When you are editing a class with a main method make so that class came

the Application to run (automatically)

Options -> Keyboard -> Other -> Run

It automatically creates a new run entry, so it's not exactly what you want.

Carlos


0
Comment actions Permalink

ok....
the points b) and c) can be object of argument but what do you think of the point a) ?

0
Comment actions Permalink

Your suggestion a) is straightforward, but maybe its the wrong strategy. Let's see:

Within an open file, errors and warnings are visible at the side bar; but if errors and warnings are scattered all over the source tree, one could loose the overview.

That's why I keep the panel with build messages open after it reported errors. But the build often stops for other reasons, the compiler stops after a few errors, and the helpful warnings of idea are not mentioned by the compiler anyway.

The code inspection finds many more problems than the editor, but one must run it manually, and wait some time for the results.

I think the most benefit would come from an option to make the code inspection persistent and incremental, plus a feature to filter the displayed results by type.

Once the code inspection was run for a project, the results would be stored with the project and updated while editing files. One could select with a drop down box to see only errors, or errors and the warnings visible in the editor, or all. When more control is needed, the code inspection's option panel offers checkboxes to choose from the supported problem types.

0
Comment actions Permalink

I would just like an option (something I would purposely invoke) that would
go through a hierarchy of the source tree, and "color" or otherwise add an
indicator of the file status for each file in the project tree.

In other words, it would be too much of a drain to do this 'in the
background' or keep it constantly updated. But I'd love to just say "hey,
show me the status -- red, yellow, or green -- of all the files in this
directory, or package, or from this directory on down, or in the whole
project". Maybe with an option to just go ahead and do it on start-up
(defaulting to NO). I mean, start-up is already a long time, what's another
several seconds :)

Mostly though, I'm interested in anything in the package I'm working on, and
it would be great to see "at a glance" where warnings are, errors are
(mostly javadoc), etc, etc. Then be able to click directly do the problem
files and work on them.

It's rather tedious to double click on each file in the project pane in
order to load it, hesitate the second it takes to light up the status
indicator, and then continue for every class file in the package, just to
verify there are no 'issues'.

It might also be nice to have the option of having the status indicator
(red, yellow, green) appear in the file's editor tab.

"Nischkaa Kovacs" <nischkaa@gmx.de> wrote in message
news:4735841.1037959923298.JavaMail.jrun@is.intellij.net...

Your suggestion a) is straightforward, but maybe its the wrong strategy.

Let's see:
>

Within an open file, errors and warnings are visible at the side bar; but

if errors and warnings are scattered all over the source tree, one could
loose the overview.
>

That's why I keep the panel with build messages open after it reported

errors. But the build often stops for other reasons, the compiler stops
after a few errors, and the helpful warnings of idea are not mentioned by
the compiler anyway.
>

The code inspection finds many more problems than the editor, but one must

run it manually, and wait some time for the results.
>

I think the most benefit would come from an option to make the code

inspection persistent and incremental, plus a feature to filter the
displayed results by type.
>

Once the code inspection was run for a project, the results would be

stored with the project and updated while editing files. One could select
with a drop down box to see only errors, or errors and the warnings visible
in the editor, or all. When more control is needed, the code inspection's
option panel offers checkboxes to choose from the supported problem types.


0
Comment actions Permalink

+1

Filed an SCR?

0

Please sign in to leave a comment.