Posted: Sat 08 Dec, 2007 10:20 am
Another request
Would it be possible to allow custom fields? For example. instead of just the preset fields "Pre", "Post", "Warning", etc, could it be possible for a user to include a custom field in the source and use CSS for layout?
A field could be identified as any string at the start of a double-semicolon line followed by a colon. For instance:
Yes, I know I should just let go of the whole "destroyed" thing, but it feels weird to be listing destroyed registers as output. I want a destroyed field!
Allowing custom fields would give much more flexibility outside of the Vera project. And since I'm not the guy who's writing the program and have no idea of what is involved, I feel it's my right to demand all kinds of crazy features.
EDIT: Also it seems that the < and > are not properly escaped. I use < in one of my comments and the xml parser chokes on it - it thinks it's a tag.
Would it be possible to allow custom fields? For example. instead of just the preset fields "Pre", "Post", "Warning", etc, could it be possible for a user to include a custom field in the source and use CSS for layout?
A field could be identified as any string at the start of a double-semicolon line followed by a colon. For instance:
Code: Select all
;; Pre:
;; This is a normal field
;;
;; Destroyed:
;; This is a custom field
Allowing custom fields would give much more flexibility outside of the Vera project. And since I'm not the guy who's writing the program and have no idea of what is involved, I feel it's my right to demand all kinds of crazy features.
EDIT: Also it seems that the < and > are not properly escaped. I use < in one of my comments and the xml parser chokes on it - it thinks it's a tag.