Seeing as everyone is giving their 2 cents worth, I thought I might as
well join in ....
> That sounds great, but think about it more carefully. Now how many
> combinations of local status and remote status can you come up with?
> How many different icons can you easily distinguish? And given that
> Windows only allows about 12 overlays in total for all applications,
> how is that going to work? And what about remote file renames? Remote
> file adds? You may not even have a local file to pin the overlay onto,
> so you only get half a story.
As an idea, what about changing the folder icons (coding example at
http://www.codeproject.com/KB/files/foldericonsincsharp.aspx) to reflect
that the parent folder needs updating rather than individual files. A
red folder could represent 'out of date', a green folder 'up to date',
etc
I also think you could add a timeout setting, e.g. 24 hours, where if
the client was unable to contact the server (or if it was a 'push'
system, the client has not heard from the server) for this period, the
status is shown as 'stale' or 'unknown'.
> TortoiseSVN has to operate within the boundaries of the features
> Subversion offers, and the restrictions placed on it by being a shell
> extension. What you are asking for does not fit well with either of
> these constraints.
Judging by the intensity of discussion each time this topic is raised,
it seems that this 'feature request' is a genuine need of the community.
Maybe it needs to be added to the development path ? Any technical
stumbling block *can* be overcome - that is the essence of engineering
and development.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-07-23 10:28:27 CEST