RE: Display list of updates

> -----Original Message-----
> From: Stefan Küng [mailto:tortoisesvn_at_gmail.com]
> Sent: Friday, May 01, 2009 10:02 AM
> To: users_at_tortoisesvn.tigris.org
> Subject: Re: Display list of updates
>
> We've discussed this before, and we won't do that. Because whatever we
> bundle, we have to support - and supporting TSVN is more than enough
> work already.

Like I said, I don't blame you. I wouldn't either, for the same reasons.

> > On to the specific problem mentioned above...I think I have a similar
> > use case. Basically I want to commit files that have been generated,
> > as long as they have not been updated by users. So I run
> > TortoiseProc.exe /command:repostatus /path:[path] (aka "Check for
> > modifications") But then I have to click "Check repository" to see
> > what has been updated there, and filter through my "changes" that
> > haven't been changed already in the repo (if they have I feel safe
> > reverting those files).
> >
> > So it would be useful if you could run the "Check repository" right
> > as you opened that window. Even better if you could tell the window
> > what column to sort on.
>
> Added param /remote in r16292.

Thanks!

> Sorting the columns is not really suitable, since the user can rearrange
> the columns and that new arrangement is remembered.

I don't follow how rearranging columns relates to sorting on them. Just because the user may switch "Path" and "Property status" doesn't seem to connect to the possibility that a script might want to pop this window up so you can review changes pre-sorted by Path, Author, or Revision. It would be great to have something like, for example, /sortby=Revision /sortorder=Descending

That said, it's a nice-to-have, because it's quick to re-sort using any column (much quicker than waiting for Check repository to return).

> > Asking for external control over the view does not seems like an
> > unusual UI scripting request, so I hope you'll take it under
> > consideration.
>
> For apps that don't have a command line client, sure, having scripting
> ability over all UIs is good. But there already is a command line client
> which provides everything you need to script commands for Subversion -
> there's no need to provide our own scripting too. At least not for tasks
> that don't require an UI (or users don't even want the UI).

Right--the key is whether the task requires a GUI. Now you could argue that my task doesn't--everything I do with generated files could be done by an intelligent script. But it isn't painful enough to do with the slick TSVN UI for me to go to that level of scripting...at least not yet. So instead I've settled on the simpler goal of making the GUI work as efficiently for me as possible.

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

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-05-01 18:27:16 CEST