[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: UI Proposal for Code Collaborator settings

From: Friedrich Brunzema <brunzefb_at_yahoo.com>
Date: Fri, 14 Jun 2013 21:13:34 -0700 (PDT)

Stefan wrote:
>You could write a client-side hook script:

>in this situation, I would recommend using the post-commit hook, since
>you don't want to mess with CC if the commit fails but only if
>commit succeeded. That script is called after the commit is finished so
>you can mess with CC at a time when all the info about the commit is
>already available.

There is enough info there to do it with a client-side script -- but it was
tempting to do it in the CommitDlg because I already have C++ infrastructure.
But I agree with you that it does not belong the commit dialog if it can be avoided.
I will build a little UI-less MFC Dialog-based app with the string decryption, reg
classes - actually I don't even need UI.  I will check the parameters and see
if Ctrl is still pressed - if so, I launch the collaborator program with the revision#.
One problem:  I need to convert the current working directory into a URL - how
would one go about doing that?

If I build such a little program and borrow TSVN code, I think the license tells me that I have to publish
the source, right?  Any suggestions as to where to publish it?  GitHub?  Recently looked at Git,
powerful, but not very
 intuitive.  The decentralized model works well for OpenSource, but not
as well for corporate organizations who like control.

Thanks for pointing the client-side hook script out to me -- shows you how
little I know of TSVN...




To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-06-15 06:13:39 CEST

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.