Stefan Küng wrote:
> Udo Eberhardt wrote:
>> In repo browser when I choose the Checkout (or Export) command on a
>> folder then in the pop-up dialog the Checkout directory is set to
>> empty. It would be nice if TSVN would be able to deduce a default
>> checkout path. This path could be computed as follows:
>> DefaultLocalPath + RepoSubpath.
>> DefaultLocalPath is a TSVN setting available in the Settings dialog.
>> RepoSubpath is the path in the repo relative to DefaultRepoUrl which
>> is another TSVN setting (see also my previous posting).
>>
>> Maybe an example makes this more clear:
>>
>> Settings dialog:
>> DefaultRepoUrl = svn://myhost/repo1
>> DefaultLocalPath = c:\prj
>>
>> When launched on svn://myhost/repo1/foo/trunk/src the repo browser
>> Checkout dialog suggests by default:
>> Checkout directory = c:\prj\foo\trunk\src
>>
>> If one prefers to have the same directory hierarchy on the local disk
>> as in the repository then this feature is great because the checkout
>> paths suggested by TSVN can always be accepted. No path needs to be
>> typed which saves time and avoids mistakes.
>
> I don't like that kind of feature. It sets too much (IMHO) on a global
> level. If you can find others who also want this feature, we can file an
> issue for this. But if there are not enough people who would like this
> feature too, I think we just should leave it.
>
Conceptually this feature creates a connection between a repo URL and a
local path. A more general approach would be to maintain a
user-configurable list of URL to local path mappings. If the current
repo URL is in this list then TSVN deduces a local path by looking up
the associated path in the list and then applying the algorithm I
suggested above.
A configurable set of repo to local path connections would be very
useful in certain usage scenarios. Especially, if developers have to
create and/or checkout new projects frequently then this feature
improves usability and helps to avoid mistakes when typing in paths.
Personally, I used MS SourceSafe for many years. Recently I started
using TSVN (and svn) and I'm enthusiastic about its much better usage
model. TSVNs approach of implementing an Explorer extension is very good
as it works in many file managers (e.g. TotalCommander). What I (and
presumably other former SourceSafe users) still miss is an implicit
connection to local paths that makes it easy and intuitive to maintain a
directory structure on the local disk that corresponds to the structure
of the repository. Are there only CVS users switching to SVN/TSVN?
Udo
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sun Sep 24 20:37:48 2006