Please make sure you send future mails about TortoiseSVN to the mailing
About your request, see my comments inline:
>> -----Original Message----- From: Brian Marquis
>> The main issue we have centers around Foxpro's use of DBASE style
>> tables for storing class, form, report and project definitions.
>> Each is a pair of tables, a .dbf file and a corresponding memo file
>> (.fpt) with varying deviations on the file extension to allow
>> Foxpro to recognize whether it's a class, form, report, etc.
>> I'd like to offer a few ideas, and as time permits some assistance
>> with writing code to implement them.
>> 1. I'd like to see a Tortoise Hooks feature, where a user could
>> define pre/post actions for updates and commits. I'm assuming we'd
>> want hooks corresponding to each server side hook.
That's a request which has come up once in the past. I think it's even
in our old issuetracker but got lost when we moved the issuetracker.
I'll added a new entry for this in our issuetracker:
>> 2. The ability to use wrapper scripts for any Tortoise menu option
>> (or OLE automation).
The menus you see in the explorer don't use OLE at all. When you click
on them, the TortoiseProc.exe is called with specific command line
options. Those options are documented in our docs, so you should be able
to use all TSVN commands just fine without the overhead of OLE.
If you think something is missing there, just tell us.
>> 3. Support for file interdependencies.
>> Because we work primarily with Foxpro, I'd like to elaborate on the
>> features above using Foxpro as an example. As mentioned earlier,
>> Foxpro uses file pairs to define the components within it's
>> applications. In order to diff these components we need to have
>> four files instead of two.
So that means you would call a custom diff tool for those files?
That's already possible. Please check the our scripts we use to diff
Word and OO-Writer files here:
(login: 'guest' - password: 'guest')
You can then write such a script (it doesn't have to be a vbs script,
anything running with wscript.exe will work). The script receives the
filenames to diff, so you could examine the filepaths, find out the
filenames of the other two files you need and then call your custom diff
tool with those four files.
Of course, if you write such a script, we would appreciate it if you
send it to us so we can include it in our next release. You don't have
to if you don't want, but it would be nice.
>> 1 & 2. The ability to wrap or hook into Tortoise at various points
>> would allow developers to perform pre or post processing in order
>> to prepare their files for versioning. In our case, we would add a
>> hook to convert the files to/from a textual representation.
Just be aware that such hooks would only work with TSVN. Other
Subversion clients won't have those hooks implemented and therefore if
you use another client than TSVN, you might get into problems.
>> 3. File interdependencies would allow us to ask Tortoise to
>> checkout the related files before performing a diff or merge. In
>> many cases, it is also necessary to maintain the original file
>> makedir /tmp/tsvn5623 copy .svn/text-base/MyClass.vcx.svn-base
>> /tmp/tsvn5623/svn-base/MyClass.vcx copy
>> svn checkout http://svnpath/MyClass.vcx
>> /tmp/tsvn5623/head/MyClass.vcx svn checkout
>> http://svnpath/MyClass.vct /tmp/tsvn5623/head/MyClass.vct
Just a note:
you can't checkout a single file, only folders! What you want here is
the 'svn cat' command.
>> VFPSourceCompare.exe /tmp/tsvn5623/svn-base/MyClass.vcx
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 Wed Jul 27 17:40:19 2005