Re: [TSVN] Proposal for external tools

Simon Large wrote:
> I have been thinking a bit more about these VB scripts over the weekend,
> as well as other 3rd party tools. Here is another idea for how we might
> make install/uninstall much easier for end users without making it the
> default.
>
> 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.

> [WinMerge]
> 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.

> 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?

> 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.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org