On 16/10/2007, Pete Hurst <pete.hurst@gmail.com> wrote:
> On 10/16/07, Hannes Eder <Hannes@hanneseder.net> wrote:
> > TortoiseCVS does only so when clicking on a non CVS folder (or empty space resp.).
> > I'll recommend to the same for TortoiseSVN, and in that case the context menu only
> > contains 7 items (Repo-browser, Export..., Create repository here..., Import..., Help,
> > Settings, About).
>
> To make this into a feature that *would* be useful, how about if the
> context menu included a configurable list of pre-defined checkout
> locations. A default install could populate this list with repository
> locations for TortoiseSVN, and Subversion itself.
>
> There could be a further option to import/export the configuration,
> which would allow project managers to easily distribute common
> repository locations to their teams.
>
> In general I'd find this marginally useful. Probably still not worth
> taking up context menu space for, but at least you'd be able to switch
> it *off* this way.
I really can't see a good reason for doing this. TortoiseSVN already
has the means to checkout from link, so the easiest way to provide a
list of common URLs to checkout is via a web page. We already do that
for the TSVN repository.
Adding fixed checkout locations to the context menu is just
unnecessary clutter, as Andy has said. Adding configurable locations
means another configuration task which is redundant because of the
checkout links.
Simon
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Tue Oct 16 12:15:34 2007