Richard D. Worth wrote:
> Simon Large wrote:
>> Richard D. Worth wrote:
>>> One more thing: The current filename (ExplorerFileMenu.png) is a little
>>> too general. The image is an example of a Shortcut menu, showing
>>> multiple TSVN menu entries. Perhaps rename to:
>>>
>>> /doc/images/en/ExplorerFileMenuShortcut.png
>>
>> I disagree, it is exactly what it says on the tin. It is the file menu
>> (from the menu bar) of explorer, not a context menu.
>>
> My point was simply that it's not an example of any old TSVN Explorer File
> Menu (as the name might suggest). As it has three menu entries, and one of
> them has a shortcut overlay, it's use is limited to this specific example.
> Having shortcut in the name helps and is consistent with the
> ContextMenuDir*.png and ContextMenuFile*.png filenames.
OK. point taken ;-)
>> There is a file called ImageStatus.txt in the doc folder, and in a few
>> cases it describes how the screenshot was taken. As a status list it
>> is not really worth anything as it is permanently out-of-date, but it
>> might be worth adapting it to give better instructions for awkward
>> cases like this.
> Thanks for the tip. I had seen it, but hadn't looked at it since I
> wasn't doing translation.
This probably needs a new document altogether, as 'ImageStatus' doesn't
describe the required function at all. Maybe 'ScreenshotHowTo' OSLT.
>>> [*] The extra menu item 'TSVNtestC' is slightly distracting. The first
>>> time I saw the image, I thought this was one of the three TSVN entries
>>> being discussed.
>>
>> You're right there. I have a few test repos & WCs which I use for
>> documentation, and they all have rubbish names like this. It would be
>> much better to use a completely different name unrelated to TSVN.
> I used 'paint' in Rev 8936, borrowing from the SVN Book. I have been
> thinking it might be good to stick with that (or something) for
> consistency in most/all screenshots as they're done/re-done.
Agreed.
>> If you feel like generating some better ones, the TMerge screenshots
>> showing 1, 2 and 3 pane examples are really rather poor. The 3-pane in
>> particular is awkward because you need to force a WC into the
>> conflicted state.
>>
>>> The non-standard entries (Scan dug.xml, UltraEdit-32) can
>>> be distracting as well.
>>
>> True. It's just a pain getting rid of all the other shell extensions
>> to create screenshots. I think some of them can be suppressed
>> relatively easily from the programs' options.
> I understand completely. I guess I'm at a small advantage since I've just
> started contributing - my menu is pretty clean ;). I am volunteering to go
> through the extra effort to clean up a menu (VMWare, Photoshop, etc).
> I'm not asking anyone else to do the same. I only made the comment to
> explain why I was re-creating the image. Cosmetic update.
Thanks for your work so far.
Simon
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Mar 14 21:53:59 2007