> Stefan Kung wrote:
>>John Norris wrote:
>> I am interested in adding user defined property names to the drop down
list
>> in the add property dialog.
>> I believe the best way to do this is to allow the user to add the names
to
>> two text configuration files (one for files, one for directories). I
>> considered adding them as a registry value but it would need to be done
for
>> each PC - this way the files can be stored on a shared drive and so
reduce
>> admin as well as provide some security.
>> The values for the configuration files could be stored in the registry as
>> other admin values are.
> Please no. I really don't like to have a setting to point to another
setting.
> Either store this in the registry, or in a config file. If you use a
> config file, store that file in %APPDATA% like Subversion and any other
> good program does.
But then there are dozens of copy of the config file so that is not good.
Anyway as I said later there is a better way.
>> It was suggested that instead of storing the file locations in the
registry
>> they could be stored in a property.
> Even worse: that way you will force to have each user set up the path to
> the network share equally. Or if you use local paths, you have to make
> sure that no user has an OS with another language or another setting than
the rest.
I agree. It was an idea I never liked. But it was suggested by yourself so I
thought I should consider it.
>> I took this a stage further and stored the property names in two
properties
>> (once gain, one for files, one for directories).
>> This approach has a number of advantages. There is no need for a separate
>> admin dialog from the original approach. There is no need to read files
and
>> convert from ASCII to Unicode. Admin may be easier as there is nothing to
>> set up on the PC.
>> The disadvantage is where the properties should be attached. So that the
>> whole directory structure (trunk, branches, tags) is covered when the
>> properties are applied, the whole repository has to be checked out rather
>> than just trunk. Also, its possibly not as obvious. Security should be OK
as
>> the directory the properties are attached to can be made read only.
>> So, I am not sure where the properties get attached but other than that,
>> "the user defined property names defined in a property" approach is the
>> preferred option.
>> Comments?
> You could create a new "project property" (like e.g. tsvn:logminsize).
> That property then could have a list of other predefined properties.
Which is what I descibe above. Except that I have two properties, one for
files and one for directories. But to go back to my original question. With
this approach, where do the properties get attached in the directory
hierachy? For testing I have put them on trunk but they would be better
placed on the "vob-tag" except that would mean bring down the whole
repository structure. But its only the once to define the properties and
then its back to normal.
Regards,
John Norris
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Nov 3 10:52:53 2006