Foxpro and subversion

Does anyone have any experience with committing FoxPro code to subversion?
The problem I have ran into is that most of the FoxPro code files, except
for .prg, are binary and unreadable as text files. So basically all the
reasons to commit your code are gone if the repository can't compare line by
line code and show you the differences. I found one solution here
http://paulmcnett.com/scX.php, but it appears that nothing has been
developed on it for quite sometime and it was never completely
finished\tested. Does anyone have any suggestions as to the best method of
version FoxPro code?

Thanks,
Curtis

Olaf
Fri Feb 29 08:19:48 CST 2008

Hi Curtis,

go here:
http://www.foxpert.com/docs/cvs.en.htm

Bye, Olaf.

glene77is
Wed Mar 05 04:30:20 CST 2008

On Feb 29, 8:53 am, "Curtis" <csch...@hotmail.com> wrote:
> Does anyone have any experience with committingFoxProcode to subversion?
> The problem I have ran into is that most of theFoxProcode files, except
> for .prg, are binary and unreadable as text files. So basically all the
> reasons to commit your code are gone if the repository can't compare line by
> line code and show you the differences. I found one solution herehttp://paulmcnett.com/scX.php, but it appears that nothing has been
> developed on it for quite sometime and it was never completely
> finished\tested. Does anyone have any suggestions as to the best method of
> versionFoxProcode?
>
> Thanks,
> Curtis

'USE filename.scx'
'Browse'
'USE filename.vcx'
'Browse'

You should be able to 'see' all the methods in forms, and classes.

I wrote an application (first version in '88) which reads a project
manager, gathers a filename list, and pulls out all text for
searching. Very useful for debugging.

Glen Ellis, Memphis, TN
www.GeoCities.com/glene77is

***

Rush
Wed Mar 05 09:12:01 CST 2008

glene77is wrote:
> On Feb 29, 8:53 am, "Curtis" <csch...@hotmail.com> wrote:
>
>> Does anyone have any experience with committingFoxProcode to subversion?
>> The problem I have ran into is that most of theFoxProcode files, except
>> for .prg, are binary and unreadable as text files. So basically all the
>> reasons to commit your code are gone if the repository can't compare line by
>> line code and show you the differences. I found one solution herehttp://paulmcnett.com/scX.php, but it appears that nothing has been
>> developed on it for quite sometime and it was never completely
>> finished\tested. Does anyone have any suggestions as to the best method of
>> versionFoxProcode?
>>
>> Thanks,
>> Curtis
>>
>
> 'USE filename.scx'
> 'Browse'
> 'USE filename.vcx'
> 'Browse'
>
> You should be able to 'see' all the methods in forms, and classes.
>
> I wrote an application (first version in '88) which reads a project
> manager, gathers a filename list, and pulls out all text for
> searching. Very useful for debugging.
>
> Glen Ellis, Memphis, TN
> www.GeoCities.com/glene77is
>
> ***
>
>
Or use the "View class code" option in the class browser. (This works
for scx files as well as vcx's.)

- Rush