Re: RFC: Log Message Templates via new hook.

Simon Large wrote:
> TSVN is not just a GUI front end for the CLI. It does things that the
> CLI cannot do, the commit dialog being a good example. The TSVN Commit
> dialog is not directly equivalent to the command line commit. It does a
> status crawl first to present you with a list of changed files and you
> can select which ones to include in the commit. You can also opt to
> show unversioned files and select any of them for adding to the commit.

This is the piece that I was not aware of, and it makes many things clearer.

Personally I don't use TSVN, not because it is slower than the CLI but
because I don't like the Explorer extension model in the first place. I
had TSVN loaded for a day or two and it made *all* Explorer access
slower (not strictly TSVN's fault).

On those rare occasions that I need a GUI in Windows, I'm currently
using Subcommander (RapidSVN seeming to have gone temporarily dormant).
  For my normal operation I use a SCC plugin from PushOK which actually
drives the Subversion CLI (this is the same way I used CVS and WinCVS).
  Most of my heavy Win32 development is file by file (typically web apps
these days), so I rarely commit more than a single file at a time.

> That is putting it a little strongly. The GUI clients should certainly
> not drive anything, but they do have (almost) as much validity as the
> CLI.

I'm sorry, that was a little strong. However, as I said in my other
message, design decisions made in the GUI clients have to be open to
change if it conflicts with proposed changes to the core API.

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org