Re: Features brainstorming

Petr Kuzel wrote:
> Found problems are paired with solution (java code in tasklist/pmd) 
> to form a suggestion. Custom rules miss the solution part (subject of
> planned PMD enhancements).
> 
> Also compare currently provided solutions from user's point of view:
> [...]
> 
> you can see that most common suggestions come from non-PMD provider
> in spite of fact it could be provided by PMD. Simply actual
> implementation is irrelevant for most users. We need to identify
> crucial suggestions and provide their fast implementation.

FWIW I never use the "fix" feature; just want to see the problems. If I 
see an unused variable, and F12 to the line where it is declared, I can 
surely press Home - Home - Shift-Down - Delete faster than it would take 
to open some suggestions window, read it, accept what it is offering, 
and check that it did what it promised (even if it were KB-accessible, 
which currently I think it is not). Even faster for adding an import: 
F12 then Alt-Shift-I is all that is needed.

The only suggestions I can realistically imagine using a "fixer" for (in 
preference to just typing a correction in the editor) would be certain 
parser errors - e.g. missing cast, though usually I am still on or near 
the line where the error is if this comes up, and typing '(' - 'Interf' 
(or some such prefix) - Ctrl-K is not hard; and uncaught exception 
(which BTW the current parser does not even notice!), though here I 
would much prefer that the editor just have a proper shortcut to insert 
the correct try-catch block. Maybe also the PMD warning about 
if-statements without braces would be more easily fixed thru a dialog.

Again, just feedback re. my personal usage - can't guess how many people 
use and like this feature.

-J.

-- 
Jesse Glick <mailto:[email protected]> x22801
NetBeans, Open APIs  <http://www.netbeans.org/>