Problem
Say you put a todo pragma in a method. The IDE is consistent with the docs, in that the IDE integration is supposed to show the "file name", line number and message. But. The "file name" appears to be the name of the enclosing class. So if I say "Move to a shared module" the pragma listing doesn't tell me "move what". I have to include it in the message, e.g., "Move Foo() to a shared module" or perhaps "Move MyClass.Foo() to a shared module" to be able to see at a glance.
Yes you have but to click on the pragma and Objo will put that line of code before you. But it would be nice to see the method name at a glance in the list as it grows, or maybe the class and the method.
Proposed Solution
Change "ClassName Line 1 message" to "ClassName.MethodName message".
As you can see, I'm suggesting leaving the line # out also, as that is more clutter than helpful in the summary since the IDE knows the line # and can take you to it -- so long as the pragmas for any given method are shown in line # order I suppose.
I guess when the pragma isn't in a class method but part of a module then the module name would be shown and if the user isn't certain where that is, they would then click on the pragma in the list to be taken there. When it comes to GUI apps maybe one would want something more like windowname.controlname.eventname -- I haven't thought that one through as I'm focusing on lower level, library-like things at the moment.
But my general point is that the pragma list should convey as much context as practicable before the user must resort to navigating around. That way it serves as a more effective reminder list in its own right.
Finally ... and you probably felt this coming ;-) if one is really going to use pragmas at scale as a development aid in a growing solution, I think the list should be collapsible by pragma type and/or perhaps filterable by type, particularly given that the amount of space to display them is relatively at a premium (for me anyway I am greedy for as much real estate as possible for my code). In fact, eventually I think one should be able to filter by the container type (class / module / window).
For now if we could get the routine name that would be good. The rest, I would suggest putting on the road map even if it's for v2 or whatever.
