RFE: Global TODO Browser

[burli]

It would be nice to have a browser for all #todos, #fixmes and so on. Would also be nice to costumize these tags

[Mystilleef (mystilleef)]

Can you give an example of how this is supposed to work? Is there a good editor that implements this?

[burli (mb-embedit)]

Similar to the Document Browser or the Bookmark Browser. If you hit a shortcut a browser window should be opend with a list of all TODOs, FIXMEs, DELETEMEs and so on from all open files.

In this browser should be a list with the filename, the line, TODO/FIXME... and the text behind the TODO/FIXME. I attached a Geany screenshot with something similar.

[Mystilleef (mystilleef)]

Makes sense now.

[isatis39871 (isatis39871)]

Nice to have indeed. Before scribes, I used ulipad. It has plenty of good features that can inspire others editors : https://code.google.com/p/ulipad/

[Mystilleef (mystilleef)]

We need to stop thinking in terms of features and start thinking in terms of "experience". As I've said several times before, Scribes is not about features, it's about delivering an experience. :-)

I'm a lot more interested in the impact a feature has in improving the overall experience of Scribes than I am about accumulating random features in an adhoc manner.

[Matěj Cepl (mcepl)]

I think what we are talking here is something like what's going on in Eclipse. When you open a file in a supported format in Eclipse it is parsed on background and all syntax errors and warnings are highlighted by putting red (or yellow for warnings) tiny boxes in the right border of the editor. Placing a TODO (or FIXME) strings in any comment adds a blue box. The equivalent of bookmarks uses this as well.

The result is:

a) one gets immediate overview of the state of the file ... I have used this heavily for converting some 3k lines of Java code to Python. In the beginning the right border was completely red, but by fixing all bugs, I got to the state when now it is completely clean (which means that it is SYNTACTICALLY correct, unfortunately there is still a ton of debugging to do to make it work for real).
b) having a target for mouse makes move in the document much faster than when scribes tell me that there is an error on line 158 and I have to type the line number to Ctrl-I box.

[Mystilleef (mystilleef)]

Matej,

Yes, this will be implemented. And I think GTKSV3 has a less
retarded buffer API so we can make better use of buffer
gutters.

Also if you press F2 you can jump to the line with syntax
errors in Scribes. No need for ctrl+I. However, the error
checking interface needs more work in Scribes. I'll attack
them when I port to gtk3 and gtksv3.