Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#418 Simple taks management function

open
nobody
3
2014-08-14
2013-03-17
Anonymous
No

For larger files it would be great to have a separate task list derived from comments. I found it sketched in issue 163, but there it is described too shortly. That would be helpful in larger projects and files where you have to follow several tasks at the same time.

I would personally prefer having the task list in the log panel, but it would be ok anywhere, as a preview replacement or like the bookmarks list in the left panel.

The task list should have different scopes selectable on the fly, like current file, current project, all openend files, or maybe even all files in the same folder as the current file. (The jedit plugin Task List has this kind of functionality and it is very useful.)

It should provide the ability to jump to the code line (and file) the task entry is derived from. This was especially useful if the list scope is more than the current file.

I would be happy with the standard task labels like TODO, DONE, NOTE, INFO, IDEA, FIXME, DEBUG, QUESTION, but it would best be configurable, so one could add labels that are better for document writing like WRITE_OUT, EXTEND, REVIEW, or REPHRASE.

Discussion

  • Blackhawke
    Blackhawke
    2014-08-14

    Let me add my vote to this. We work on projects ranging from novella length to multiple book series. The standard "%TODO" functionality has been great for issue tracking, but the improvements suggested above would be FANTABULOUS! :)

     
  • Tim Hoffmann
    Tim Hoffmann
    2014-08-14

    Have you considered the package todonotes. Using TXS and \todonotes you can combine the best of both worlds (source code and output). See this demonstration:

     
    Last edit: Tim Hoffmann 2014-08-14