Re: Features brainstorming

Vincent Brabant a écrit :

> Petr Kuzel a écrit :
> 
>> Hi all,
>>
>> next release planning is behind door so I'd
>> like to gather your input (including flashback).
> 
> 
>>
>> Do not feel limited by following questions:
>>
>>   - What's top priority feature you would like to see in next (>NB 
>> 3.6) tasklist version?
> 
> - PMD & Checklist
>     For me, it's important that tasklist continue to support Javadoc, 
> PDM, Compiler, ..., to builf a suggestion list
>     For example:         He, you forgot to import that class. Click here 
> to add it !
>         He, Your copyright is out of date. Click here to update it !
> 
> - Suggestion Provider.
> - Suggestion Merger
> 
>     What I am suggesting here was already suggested in the past and been 
> partially implemented. It was a preview displaying a BEFORE/AFTER. I say 
> it's partially implemented, because now you have a preview when you 
> select a suggestion and ask to fix it.
>     What would be nice is to use to existing merg tool to be able to 
> merge all suggestions in one shot:
>         On the left, user can see content of the existing file.
>         On the right, user can see the same content, but with all 
> suggestion applied. Modification must appears in colors, as if user was 
> in DIFF mode.
>         User can then accept all suggestions, or accepts/rejects somes 
> of them.
>         When he click on OK, the existing file is merged with all 
> suggestions he selects in one shot.
> 
>     That merge tool exists today in NetBeans.
>     "The only thing that must be done" is build the file containing 
> listed suggestions, and permits to call the merge tool even if it's not 
> a CVS repository.
> 
>     - Also give suggestions for JDK1.4/JDK1.5 new features.
> 
>>
>>   - How does tasklist tool window concept suit your workflow?
> 
>     - I like to have in priority feedback concerning what I am doing on:
>         it means:
>             1st the current file I am editing;
>             2nd the other files opened in the editor;
>             3rd the files belonging to the same package;
>             4th the files belonging to the mounted filesystem.
>         And it would be nice if I could limit scan with one of those 
> four proposals. Via the Expert Tab properties, for example.
> 
>     - I would like to see also suggestions for HTML pages (by usage of 
> JTidy), JSP Pages (Jtidy for HTML part, Java Suggestions for Java part).
> 
>>
>>   - What suggestions do you expect in tasklist view?
> 
>     Every suggestions/Warning given by PMD, Checkstyle, Jcsc, findbugs, 
> jalopy, jdepends would be available in tasklist view
> 
>>
>>   - What suggestions do you expect directly in editor?
> 
>     Every suggestions appearing in the tasklist view MUST also appears 
> in the editor. Whith icon in the marge. And when you click on that icon, 
> you can easily fix the suggestion.
> 
>     User must be able to see suggestions in the editor even if the 
> tasklist window is not displayed.
> 
>>
>>   - What current 'feature' do you dislike (or hate)?
>>
>>   - Do you prefer explicit actions (Scan for Suggestions,
>>     I18N wizards, Compiler output, ...) or background
>>     hints (Suggestions, error highlighting in editor).
> 
>     I think both would be possible. Background hints could be enable by 
> default, at least for the currently edited file. But users could have 
> possibility to start explicit actions for a larget target (all opened 
> files, the current package/directory, the current filesystem / the 
> current project / all filesystems) or at least to select which kind of 
> action he want tasklist executes in background.
> 
>>
>>   - What related tools do you use? Why?
> 
> Hereafter the list of tools I am using:
>     - Checkstyle (http://checkstyle.sourceforge.net/),
>     - PMD (http://pmd.sourceforge.net/),
>     - cpd (Copy Paste Detector),
>     - metrics modules of NetBeans (it would be enhanced to give more 
> metrics and display them as graphics)
>     - JCSC (for Metrics part) (http://jcsc.sourceforge.net/),
>     - findbugs    (attention that it works on class files, not on source 
> files. Need to be compiled before)
>     - jalopy    (also for somes refactoring stuff integrated into netbeans)
>     - jdepends    (Imagine that you build dependency rules. Tasklist 
> could detect that you violate it and directly prevent user therefore)
>     - Javadoc use   (when you generate Javadoc with -use parameter, it 
> build the list of package/classes where you are using that class. So, it 
> would be nice if tasklist could contains
> 
>>
>>   - ...
>>   Thanks for your feedback
>>   Cc.
>>
>> PS: I plan to post similar mail to broader nbusers forum
>> after 3.6 beta release. Does it make sense?
>>
> 
> 
Any comments ?
Does I have to fill a RFE for the Suggestion Merger ?

-- 
Vincent Brabant
----------------
http://www.netbeans.org/index_fr.html
http://vbrabant-fr.skynetblogs.be