On 17 Feb 2004, at 19:52, Barry Scott wrote:
> At 15-02-2004 17:09, Calum Robinson wrote:
>> I'm in the process of writing a GUI client for subversion (which is
>> going very smoothly thanks to the nice API), but have run into a
>> problem with getting the versions associated with a file or
>> directory.
>
> How is your GUI different to the others in development? What do you
> think is
> missing from the other GUI's designs?
Mine is a Mac OS X only GUI, which will support some Mac OS X-only
features like drag & drop. There's also a lot of stuff you get for free
in a Mac OS X-only app, like spell checking in text fields (e.g. the
commit message field) that you don't seem to get with other toolkits.
> In my WorkBench GUI (see pysvn.tigris.org) this is what I display with
> the
> History command for a file. I only see info for the revisions that the
> file
> was modified in (that interesting ones), Just as you want.
Same here.
> The delay is the round trip time to the repo, not the amount of data
> returned, so
> losing the text of the log message should not make that much
> difference to the delay
> unless you are on a very low bandwidth connection.
I hadn't benchmarked it yet, but if there are 10,000 log messages for a
file/directory (e.g. the root of the subversion repos.) and each
message is ~100 bytes, isn't that ~1MB that could be taken off the
amount to be downloaded?
> Is the problem that you want this data for all the files in a working
> copy?
No, just one. But if my GUI allows the user to select the root of a
repository then every message has to be downloaded. I would cache the
log messages, but that isn't possible with the current API. Being able
to get just the revision numbers would let me fetch only the log
messages I need.
Calum
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 18 14:03:09 2004