Simon Large wrote:
> The only way this could work efficiently would be for your program to
> add a line to the revision's log message, which is a bit risky. In that
> case you could use some sort of coding like that which is used for
> *bold* and _underline_, or use a regex to pick out special information
> in the same way we do for bugtraq properties. This could also be used
> for colour coding revisions according to whether they are bugfixes, new
> features, cleanup, etc. But it all sounds like a lot of work.
method 1: store the regex in properties
+ project independent
- colors need to be set in the property/properties. Which means the
colors are hard-coded. And from experience (search the mailing list) I
know that's a bad idea, because if people don't have another color
scheme they can't read the text anymore.
method 2: store the regex globally in the settings
+ colors could be configured individually
- not project independent. That means coloring of log entries in
completely unrelated projects can happen which will confuse users.
overall:
coloring the whole log entry (top pane of log dialog) is a bad idea,
because a regex parsing needs a lot of time (i.e. it's an expensive
operation) and could slow down the whole drawing of the log dialog.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Fri Sep 22 18:48:10 2006