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

RE: Re: Suggestion: Improving language

From: David Balažic <david.balazic_at_comtrade.com>
Date: Wed, 8 Dec 2010 11:46:44 +0100

Andy Levy wrote:

> IMHO, the language needs to be consistent with what's presently used
> for the "original" Subversion,

Yes, nobody is disputing that.

> And Windows administration has been moving back toward the command
> line (example: PowerShell & Exchange Server 2007). GUIs are not a
> panacea,

TSVN is a GUI application. This won't change, will it?

> Random words in ALL CAPS is a poor UI design, IMO.

Good, nobody suggested random words to be all caps.

>> Why not "SWITCH to Branch/Tag"?  "RELOCATE working copy" couldn't hurt.
>>  My point is, these menu choices and dialog boxes are so terse that they hardly
>> help guide new/infrequent users.  It's a "click-until-I-recognize-something" interface.
>>  Thankfully, the dialog boxes have a Help button that opens the manual.

> Visually those ALL CAPS do hurt, at least to me.

Then the svn words can be marked so other way.

I was thinking adding an explanatory tooltip to menu items, but
it seems Windows does not support that (?).

Additional words in the menu text are another option, leaving the standard
SVN command name there, marked as such (by caps, bold, italics,
color or otherwise).

Or each menu item pops up a dialog, which has a short explanation.
Most actions already lead to a dialog, so this is not a big UI change.
The dialogos that just explain what will be done can have a "don't show
this in the future, just do the action" checkbox.

Regards,
David

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2688731

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-12-08 11:46:40 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.