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

Re: hooks to facilitate source conversion from binary form to text and back

From: Simon Large <simon.tortoisesvn_at_googlemail.com>
Date: Wed, 30 Sep 2009 22:48:23 +0100

2009/9/30 Stefan Küng <tortoisesvn_at_gmail.com>:
> On 30.09.2009 17:06, Eduard Alexandru wrote:
>> I'm a visual foxpro developer and the bulk of visual foxpro source
>> files are in binary format (foxpro compatible tables).
>> In order to use the svn's compare and merge facilities compunity
>> members have created tools to perform the convertion of source files
>> from binary form to text (xml files) and back to binary form. The
>> files places and source control are the xml versions.
> Are those tools opensource? If yes, where can I find them?
>> The process is simple, however tedious and i hope that in some future
>> version the TortoiseSVN team will add pre/post hooks to "Check for
>> modifications" and "Checkout" operations so users like me could hook
>> the conversion tools directly into TSVN.
> Actually, it's quite easy to do this now without the need to change
> something in TSVN:
> create a diff script for those foxpro files, and configure TSVN to use
> that diff script (settings dialog->external programs->diff viewer->advanced)
> in your diff script, you should call the conversion tool, then pass the
> converted files to TortoiseMerge (or any other text diff tool you like).
> And if you have that script ready, we'd appreciate it if you could make
> it opensource and send it to us so we can include that script in TSVN.

That would be true if the files were stored as binary in the repo. You
would need to convert both mine and theirs to XML in the diff script.

But IIUC the files are stored as XML in the repo. So after checkout of
the xml files he would like a hook script to convert them to binary
(unversioned, ignored) to do the real work on in foxpro. In order for
CfM to work you have to convert the modified binary back to XML so
that you have something to diff against. And when doing an update you
need to convert the binary back to XML before the update, so that
subversion can merge incoming changes, and convert to binary after the
update so that you can continue working in foxpro on the updated

So client side hooks is what is required here.


:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-09-30 23:48:27 CEST

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

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