Re: Becoming a fisherman

see comments in the text

Petr Kuzel wrote:

>Hello,
>
>I added a concept document under taslist/www/barracuda/
>which describes my intentions. It descibes a use case.
>Its (stable) implementation is in my opinion deliverable
>for next IDE release. I'll be working on it :-).
>
>  Please comment on
>  Cc.
>
>-- text transcript: --
>
>  Abstract
>
>   This  paper  defines  high level goals for tasklist module
>   functionality integration into Barracuda release.
>
>  Supported Use Case
>
>   You write a code and decide to keep focused and defer some
>   task  leaving  a  recognizeable note in source code. After
>   some  time you want to navigate to these notes and resolve
>   them.
>
>  Unsupported Use Cases
>
>   Code  analysis  tools  (PMD,  compiler, i18n checker, HTML
>   checker,  copyright  checker, unused imports checker, ...)
>
compiler is not a code analysis tool. It replaces standard 
org.openide.windows.InputOutput.
It shows messages of the last build.

>   create  virtual  notes.  You can navigate though these and
>   some  of  them  have  Autofix  action  performing  default
>   problem solution.
>   It's  a  concept  that should be consistently supported by
>   all  relevant  IDE  analysers (now user actions). It's too
>   expensive right now.
>  
>
Current implementation of the suggestions view shows suggestions for the 
currently opened
source file. What about "Search for suggestions"-action? Will it get 
into 4.0?

>   Bug  database  adapter creates virtual notes corresponding
>   to  bugs  filled  against developed code. You can navigate
>   through them and mark selected ones as fixed.
>   Defer  and  try  to  solve  as  coupled  task with version
>   control operations related to the fix.
>
>   Calendar  support which lets you record your own todo list
>   independet  from source code (however a source info can be
>   optionally attached).
>   It  duplicates  calendaring  application  and  it  is  not
>   significantly  tied  to  code  developing  workflow. To be
>   really usefull it should bridge to Issuezilla TASKs etc.
>
>  Projection to Existing Code
>
>   Following  modules need to be stabilized and customized to
>   fullfil  the  goal:  suggestions,  docscan,  api, core and
>   editor.
>
>  Work to be Done
>
>   Create  navigateable  list  all  tasks  in  project.  It's
>   content  should  contain  only  tasks based on source code
>   notes.
>
This needs the new "projects" module. When will it be ready?

>
>   Hide  calendaring  support (just do not deploy the module)
>   and  suggestions  from code analysis tools, still allowing
>   advanced   users   to   install   these.  However  without
>   cluttering the supported use case user interface.
>
>   Write  unit tests for core functionality. Cover API module
>   by the ARCH process.
>
>   Test and fix bugs.
>
>  
>