Julian Foad wrote:
> Martin Hauner wrote:
>> My motivation behind it is to display a list of changed items in a gui
>> client when I like to see the difference between branches/tags. I can
>> then select an item from the list to run a "real" diff on it. So the
>> summarize is something like a diff preview.
> OK. For GUIs we should think mainly about the API. So, what is the
> best that a GUI can do in terms of achieving this goal using the
> existing API? That would be interesting to know before designing an
> extended API.
Not much. Stefan said that he parses the diff output in tsvn to get this
info. I thought about that too but i don't like to implement it that way.
I don't know of another solution.
>> A gui client needs the revisions so it can run diff on that file from
>> the preview if i like to see a detailed diff of the changed file.
> It doesn't need the revision numbers to be reported back to it, because
> it can just use the same URLs and/or revision numbers that were supplied
> to the "diff"
> command in the first place.
Correct. For the gui case the revisions would be sugar information.
Not for #2015 (diff summarize) which likes to see them.
Note that I am more interested in the gui case and was pointed to #2015
as a solution.
> It looks like you would like some help with this design stage (and the
> coding) from others on the list, and that's fine, though I would also
> like to encourage you to have a go at researching the features that we
> want it to be somewhat compatible with (cvs diff, svn diff, svn status)
> and designing and writing up a proposal. A good way to present it would
> be as a patch to the Subversion book and/or on-line help, stating
> exactly what the feature does and what its output means.
Ok, i will write a proposal. It will be from my point of view (gui) (mostly)
ignoring issue #2015 as a first step to avoid a mixture. We can then see
where both features overlap or not.
a crossplatform Win32/Unix/MacOSX svn gui client & diff/merge tool.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Jun 7 22:32:00 2005