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

Re: [TSVN] SubWCRev update

From: SteveKing <steveking_at_gmx.ch>
Date: 2005-04-09 23:41:27 CEST

Molle Bestefich wrote:
> Well, it's just my opinion.
> And I can see how it's not any kind of work for you since you know the
> tool inside-out and you only use it in one single project.
> I'm thinking of putting it into use in more projects, with users that
> doesn't know the tool and it's quirks.
> Anyway, what I'm thinking is:
> - high learning curve compared to the relatively simple thing it provides

learning curve? What's so difficult about having a template file?

> - takes a little too much work to set up for each project for one to
> bother learning it

Not more work than any external tool you use as a pre/post-build step.

> - requires that you educate users needlessly on how to integrate into
> their projects

That's a moo point. You always have to tell users how to use a tool. No
matter what tool it is. And if people don't know how to integrate tools
in VS.NET, then you have to tell them that too, no matter what tool it is.

> I think the above wouldn't be necessary if there was an option to do
> keyword-expansion (in a sane way) instead of keyword-replacement.

Subversion already does keyword expansion. So why should SubWCRev copy that?

> We're getting theoretical here.
> But they're not mutually exclusive.
> SubWCRev could easily be made to replace keywords "the subversion way"
> and still fill in the role that it has just fine. It could also be
> made to do keywords in a new way where it replaces the word before /*
> $WCREV$ */, so you could type:
> #define tuggummi 123 /* $WCREV$ */

If SubWCRev would do that, then you either can't have the file under
version control, or the file would be modified after every build and be
in the committed list. So users would constantly commit a file with no
'real' changes in it.

> I think that SubWCRev is done in a much less user-friendly manner that
> it could've been, you think it's fine the way it is. Conclusion:
> I'll go modify it myself before I put it into large-scale use here.

No, it's as user friendly as it can be. It was designed to do exactly
what it does. You want a different tool, and you use SubWCRev in a way
it never was designed to work. That's why you think it's not user
friendly. If SubWCRev would work as you want, we couldn't use it in
TSVN. And it wouldn't do what it was designed to do.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sat Apr 9 23:42:11 2005

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.