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

Re: Wishlist for enhancements

From: Stefan Küng <stefan_kueng_at_catv.rol.ch>
Date: 2004-04-01 21:36:57 CEST

SteveKing wrote:

> Ben Collins-Sussman wrote:
>
>>> So I'd like another entry in the status struct indicating the number
>>> of bytes or lines which have changed.
>>
>>
>>
>> ...so it makes no sense to add this field to the status struct. We
>> absolutely don't want to force brute-force comparisons!
>
>
> You don't have to force this comparison. Just fill in that struct-member
> if you do the brute-force comparison and leave it if you don't. Maybe
> leaving it 0 or set it to an 'illegal' value (e.g. -1) to indicate that
> this member isn't valid.
> Or: another flag passed to svn_client_status() to force those comparisons?

Or: give this information in the ctx->notify_func when committing.
Because at that time you already must have this information.

Which reminds me: I'd also like to have a better progress indication
about how much data is already sent/received and how much data still has
to be sent/received in commits/updates/checkouts/...
This would improve the user experience a lot, especially for big
projects/files. Imagine you download a big file from the internet and
your browser wouldn't show you the progress of the download...

Please don't take me wrong. Sure I'd like to have these features
implemented (and so do most users of TortoiseSVN), but all these are
just 'nice to have' - no need to focus on these.

Stefan

---
"The whole problem with the world is that fools and fanatics are always 
so certain of themselves, but wiser people so full of doubts." - 
Bertrand Russell
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 1 21:38:06 2004

This is an archived mail posted to the Subversion Dev mailing list.

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