On 3/14/07, Nicholas Albion <nalbion@yahoo.com> wrote:
> I've been using TortoiseSVN for over a year now, but every time I go to add a new project to version control I end up spending hours trying remember how to do it. The process doesn't need to be as complicated as it currently is I think that the developers of TSVN have overlooked the fact that there are different classes of users of TSVN:
>
>
>
> 1) SVN server administrators who want to create a new repository on a server, and import (or export?!) a tarball into the repo.
TSVN is a client, not a server/repository admin tool.
The official SVN apps don't handle a tarball as a starting point.
> 2) networked developers who want to download a project from an existing SVN repo.
Unless I'm mistaken, you're not asking for anything new here?
> 3) developers who want to add source code for a new project to version control
>
>
>
> I'm a type 3) user, and suspect that my use case has been overlooked in the design of the TSVN gui.
>
>
>
> What I'd like to see are new items for the explorer right-click menu designed specifically for each use case. Use case 3) might be labeled "Add to version control". The menu item would give a dialog as shown:
>
>
> +------------------------------------------------------------------------------------------+
> SVN url: [ file://c:\svn ]
>
> Repository name: [ MyProject ]
> Source location [ c:\swdev\projects\MyProject ] (browse...)
>
> [ OK ] [ Cancel ]
> +------------------------------------------------------------------------------------------+
>
> - The SVN url would typically remain unchanged once initially defined by during TSVN install. The default URL should be presented so the user has one less thing to remember. Very rarely would this change, perhaps it's not required at all for this use case.
> - The repository name would be appended to SVN url and the wizard would do "md c:\svn\MyProject; right-click( c:\svn\MyProject )->"Create repository here"
> - Source location would be used to import the existing code into the repo and then the repo would be checked out into this folder. This field would be automatically filled out as the folder selected for "Add to version control"
>
> ...Possibly not the clearest explanation, but basically, all the user would have to do would be to :
> 1) right click on an existing code base,
> 2) select "Add to version control"
> 3) give the project a name (and this might even be defaulted to the name of the current directory)
> 4) press OK.
>
> ...as opposed to:
> 1) navigate to c:\svn
> 2) create new folder "MyProject"
> 3) right click on folder
> 4) select "Create repository here"
> 5) navigate back to project
> 6) right click on folder
> 7) select "check out"
> 8) right click on folder
> 9) select "repo browser"
> 10) drag existing code into repo
I think what you may be missing is that unless you have a repository
already, you can't "Add to version control".
Right-click...Import will import to an existing repository. Setting up
file:/// repositories really is only advised for limited single-user
setups and testing, so I don't see why a special-case menu item should
be added for it. 90% of the time, one should be importing into an
existing repository on the network, which TSVN can't set up for you.
Additionally, once you create your file:/// repository, you can use
Import just like on a networked repository. So really, your 10 steps
should only be 5 - one more than your desired state.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Wed Mar 14 18:01:17 2007