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

Re: [TSVN] Needs-lock property in Add dialog and/or context menu

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-06-02 20:14:55 CEST

Owen Shaw <owen.shaw@windriver.com> wrote on 06/02/2005 02:10:17 PM:

>
> >> The needs-lock property is likely something that will be set quite
> >> often. I'd like to propose that the property be exposed in the Add
> >> dialog and/or the TortoiseSVN context menu.
> >
> >
> > That's what autoprops are for!
> > Please open the settings dialog, main page. Click on "Edit" right next

> > to the "Subversion configuration file" label. There you'll find
> > detailed instructions on how to set up the autoprop feature.
>
> I'm well aware of the autoprops feature, but as I outlined at the end of

> my previous message, it does not help at all.

It doesn't help for you because you need to have different policies for
different projects. That will not be true for everyone, and it is really
a Subversion limitation. Luckily, this is tentatively the focus for the
1.3 release so hopefully that will resolve the issue.

> >> For the Add dialog, a simple checkbox for each file would not only
allow
> >> easy access to the property, but would also be a reminder to users
> >> (especially the ones who aren't aware subversion has "versioned
> >> properties") that the feature exists.
> >
> >
> > The add dialog already has checkboxes for each file. You can
> > select/deselect files for adding there. Two checkboxes just would
> > confuse the users (which box is for what?).
> >
> I hardly think users would be confused by a second checkbox, especially
> if it's labeled. But if you insist they would be, how about a toggle
> control that looks like a lock?

Bad UI is bad UI. We shouldn't be adding a bunch of check boxes because
someone wants to use a feature. There will be many, many more users that
do not want to use this feature. Setting this property recursively from
the top of your WC is trivial.

> >> I know that the auto-props feature exits (thanks for the interface
> >> config in Settings!), but it has two drawbacks: 1) only works for new
> >> files and 2) the rules apply to any repository I access with
Tortoise,
> >> which could very easily have different locking policies.
> >
> >
> > 1) By adding such a feature to the add dialog, it still would only
> > help for new files!
> >
> Hence the context menu option I also suggested.
>
> I don't pretend to have the greatest ideas on interface design.
> However, I'd appreciate it if you'd respond to the general suggestion
> that the needs-lock property will be heavily used by many users and
> deserves a more prominent, easily accessable interface.

I agree with Stefan. TortoiseSVN already provides more than adequate UI
for using this feature. The Subversion autoprops enhancement is what is
really needed. I would hate to see the UI cluttered up as a stop-gap.

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Jun 2 20:15:16 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.