I have built into the next version of FireFly Visual Designer the ability for the programmer to embed special comments into his code that will later display in a grid (sort of a way to track to-do items throughout the code base).
I know that this idea is certainly not new, but I have never used it in other products such as Visual Studio. I would like to know if the way that I have it implemented is consistent with other products that have this functionality. Your comments are appreciated.
Here is how I have it working:
(1) The programmer inserts a special series of characters (prefaced by the comment character and two double forward slahes). For example:
- or -
(2) FireFly parses the code and identifies the special tags (currently the only tags that are searched for are '//TODO and '//HACK.... are there others?)
(3) When a special tag is found, FireFly saves the tag type (e.g. TODO, HACK), the description (e.g. Fix up the options...), the source file (e.g. modGeneral.inc), and the line number in the source file where the tag occurs.
(4) The programmer selects "Project Notes/Tasks" where a popup dialog presents the user with a ListView showing each found tag.
(5) The programmer can double-click on a Listview entry (or press ENTER) to close the popup dialog and then position itself at the point in the code editor where the special comment tag exists.
Sound reasonable? Am I missing something else?
Thanks!
I know that this idea is certainly not new, but I have never used it in other products such as Visual Studio. I would like to know if the way that I have it implemented is consistent with other products that have this functionality. Your comments are appreciated.

Here is how I have it working:
(1) The programmer inserts a special series of characters (prefaced by the comment character and two double forward slahes). For example:
Code:
'//TODO Fix up the options for the popup men
Code:
'//HACK Optimize the payment searching algorithm.
(3) When a special tag is found, FireFly saves the tag type (e.g. TODO, HACK), the description (e.g. Fix up the options...), the source file (e.g. modGeneral.inc), and the line number in the source file where the tag occurs.
(4) The programmer selects "Project Notes/Tasks" where a popup dialog presents the user with a ListView showing each found tag.
(5) The programmer can double-click on a Listview entry (or press ENTER) to close the popup dialog and then position itself at the point in the code editor where the special comment tag exists.
Sound reasonable? Am I missing something else?
Thanks!
Comment