[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: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Sat, 15 Jun 2013 11:02:44 +0200

On 15.06.2013 06:13, Friedrich Brunzema wrote:
> Stefan wrote:
> >You could write a client-side hook script:
> >http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-settings.html#tsvn-dug-settings-hooks <http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-settings.html#tsvn-dug-settings-hooks>
> >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 the
> >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.

You can still implement your hook script a as C++ application if you want.

> 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#.

Do NOT use Ctrl to determine anything: you can close most TSVN dialogs
directly using Ctrl+Enter - that's useful for all those dialogs where
the focus is on an input edit control where simply pressing Enter will
add a newline instead of closing the dialog.

So all those people who use Ctrl+Enter to fast close the dialog will
always get your special treatment if you check for that.

> One problem: I need to convert the current working directory into a URL
> - how
> would one go about doing that?

If you implement an issue tracker plugin, you get the url of the common
root of all committed files in CheckCommit().

> 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.

You don't have to publish it: you only have to provide the source code
if someone asks and of course you have to indicate that somewhere in
your about box and/or website.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest interface to (Sub)version control
    /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-06-15 11:02:57 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.