[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-devel
Subject:    [Bug 68610] Enhance problem reporter for more advanced analysis
From:       Daniel Franke <daniel.franke () imbs ! uni-luebeck ! de>
Date:       2004-04-27 16:00:18
Message-ID: 20040427160018.9273.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
      
http://bugs.kde.org/show_bug.cgi?id=68610      




------- Additional Comments From daniel.franke imbs uni-luebeck de  2004-04-27 18:00 \
------- Concerning priority levels:

An "easy" solution (without having to maintain a list of issues) would be something \
like this:

Instead of 
--
  fixme Your-Issue-Here
--
One could introduce levels as in 
--
  fixme ([1..5]) Your-Issue-Here
--
If the parser hits " fixme" it could peek for "(n)", if found 'n' is the level, \
otherwise level will be defined (e.g. 3).

Doxygen will handle "(n)" as part of the description, so the levels will be included \
in the dox ( todo,  bug) as well (unsorted, though). 

Hiding of issues could be achieved by a threshold "Only show items with priority X or \
higher" - if you want to see a specific one, raise it's priority. (Doesn't make much \
sense in having a high-prior TODO and hiding it, does it?)

_______________________________________________
Kdevelop-devel mailing list
Kdevelop-devel@barney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel


[prev in list] [next in list] [prev in thread] [next in thread]