> Simon Large wrote:
>> We ship TSVN with whatever contributed scripts we have, and an INI
>> file which describes them. Format might be something like:
> Whenever I hear 'ini file' a big red light goes on in my mind which says
> STOP! But maybe that's just me.
I find them quite useful as a standard way of holding this sort of
information. Why don't you like them?
>> Descr = Perforce WinMerge
>> Merge = P4WinMrg.exe %base %theirs %mine %merged
> Problem here: the path to the exe is not known, and can't be known
> without crawling the whole harddrive.
Searching the PATH variable would be a start, and if it's not there you
have to ask the user to find it.
>> The idea is that we add a new 'install...' button which brings up a
>> dialog listing the contributed diff/merge scripts, as shown in this
>> ini file. The dialog shows the file extension, the type of document
>> that it refers to and any other comments. Select one line from the
>> list, click [Install], and the command line gets filled in for you. It
>> might be nice to check the path to the tool.
> Wow. That would be a huge amount of work! And for something most people
> don't even use?
Maybe not worth it then :-(
>> Another advantage is that we are not hard coding any of this into
>> TortoiseProc, and it is easy to expand with new scripts.
> We don't have anything hardcoded right now either. TSVN scans the
> diff-utils folder after an upgrade for scripts and sets them to use if
> no other tool is already set.
You are relying on Windows file association to get wscript.exe to
execute the .vbs script. 9 out of 10 Tortoise owners who expressed a
preference thought that might not be a good idea ;-)
And if the user doesn't want that script for some reason, and deletes
it, won't TSVN put it straight back in on the next upgrade?
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Jul 11 13:25:42 2005