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

Re: [TSVN] Top level menus, Log message dialog

From: SteveKing <steveking_at_gmx.ch>
Date: 2004-10-26 17:40:15 CEST

Francis Irving wrote:
> Hello! A few minor suggestions, some things taken from TortoiseCVS.
> - If I have shortcut to a folder, and right click on it, I don't get the
> TortoiseSVN options. For example, I have a shortcut to my project
> directory on the quicklaunch bar. I'd like to be able to right click on
> it and do SVN Update or SVN Commit.

In the very early days of TSVN, that was implemented. But then we got
all kinds of problems with those shortcuts, so I dropped them.
- The overlays aren't shown on those shortcuts
- Different windows versions treat shortcuts not always the same, which
lead to some very strange crashes
- Shortcuts are _files_, which when treated as shortcuts can't be
versioned anymore (and that's what some people really want to do).

> - The context menu when right clicking on a file which could be added to
> subversion, could contain the Add option on the top level menu (where
> update and commit go), rather than the TortoiseSVN submenu.
> - Similarly, when right clicking on a changed file, the Diff option
> would be better on the top level menu.

Settings dialog, look&feel tab. You can there define yourself which menu
entries should show up on the top menu or the submenu.

> - When I click "Get All" in the log messages dialog, I find the dialog
> "Shall the log stop on a copy" very confusing, and an unnecessary
> interupting modal dialog. It would be better to either 1) Always get
> everything, but mark with a line in the dialog where the first copy was,
> so people can see where a branch started. 2) Have two buttons on the
> log messages dialog "Get to Branch Start", "Get All History", which
> appropriately ghost themselves out.

I guess the second option here is better. But should I add another
button as you suggested or add a checkbox with "stop on copy"?

> - I expect the message log to have everything in straight away, and find
> it confusing that it doesn't. Possible solutions: 1. Couldn't you run a
> "Get All" in a background thread automatically? 2. Could make it
> clearer at the top of the dialog that the log is incomplete, perhaps by
> putting the Get All button inside the top list box (appearing at the
> end, and saying something like "Get more..."), or if it is hard to make
> the buttons just add a row saying "To get the rest of the history click
> Get All".

I don't like (1) at all. You see, if you get the logs for example for
the subversion repository (try an 'svn log -v' > testfile) you download
around 7Megs of text data! That's really a lot, and can bring down a
server really quickly if all people would do that often. Sure, for
smaller projects or new projects the data amount will be much much
smaller, but there are even bigger projects around than Subversion itself.

I think it should be clear without adding additional hints: the "Get
All" button is only visible if you don't have the full log fetched the
first time.


   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 Tue Oct 26 18:49:56 2004

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.