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

Re: Feature request: Vizualization of 'fsvs' properties.

From: Simon Large <simon.tortoisesvn_at_googlemail.com>
Date: Sat, 6 Sep 2008 22:08:54 +0100

2008/9/6 mmm4m5m <mmm4m5m_at_gmail.com>:
> Also, from my point of view, there is huge difference between
> 'svn:bugtraq' and 'svn:mode', 'svn:time', 'svn:owner', 'svn:group'.

Actually the property is bugtraq:xxx not svn:bugtraq, but that was
probably a typo.

In general I don't think it would be right for TSVN to start adding
support for specific properties for one particular system - where
would that end? But we could bypass all the arguments and polemic
about using "svn:" properties by asking the question a different way -
"Can you customize the CfM columns (and maybe repo-browser) to show
user-defined properties?". If the user chooses to use svn: properties
against Subversion's guidelines then that is their problem. We just
provide a means to display *any* property. That seems to me to be a
reasonable feature request.

The down-side to this in the repo browser, is that AFAIK properties
have to be fetched for each item individually, so adding such
properties could slow the browser down a *lot*. But hey, that's the
user's lookout. They choose to display props and take the
consequences. An improvement would be to have the props fetched in a
separate thread and filled in as they become available, but that might
be just too much work.

Displaying as Explorer columns is not worth the effort as M$ seem to
have phased out custom columns in Vista.


: ___
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
To unsubscribe, e-mail: dev-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: dev-help_at_tortoisesvn.tigris.org
Received on 2008-09-06 23:09:06 CEST

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

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