Functionality planned for Barracuda release
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.
The resolution task can be based on listing all notes in project
or listing notes for active document.
Unsupported Use Cases
Code analysis tools (PMD, compiler, i18n checker, HTML checker,
copyright checker, unused imports checker, ...) 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.
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.
Related Requirements
Following modules need to be stabilized and customized
to fullfil the goal: suggestions, docscan, api, core and
editor.
Related Documents
Functional Specification
UI Specification
Design Specification
Petr Kuzel on 5th November 2003
The document is open for feedback