Hi Fernando,

thanks for replieing.

Sounds good.

I've thought a bit around it and found two ideas

#1 split and cat athe text file.

#2 split and cat the vcx

I think #2 easier. because it would just create vcx's like
YourClassLib.YourClass.vcx

This could be more or less achieved by scanning the vcx and creating a new table out of header record and the class contents
The rest is your default class to prg - just for more libs

The opposite way build the little vcxs oput of the little prgs and then gather them to one new large one.
Should be simple. :)


In the end it should produce something like

YourClassLib.YourClass.pr2

I find it much more comfortable to merge single classes than large Lbs. :)

So for git I would just include *.*.pr2 classes and that's it.




>Hi Lutz, reviewing this thread, I see that I didn't replied you! Sorry, I do that right now:
>
>>and now the big question
>>
>>As I understand you generate a text file. (And the oppposite) The handling of SVC is not your part.
>
>Exactly, I do just the convertion part, so the SCM tool can do diffs and merges.
>
>
>>
>>You yourself declares that I could cut'n'paste classes between VC2 files. So if I could do that with an editor it could be done with a prg?I simply as a post operation. And to cat the prefacing the VC2-VCX operation should not be a problem as well. I will have look into it.
>
>Yes, you can work on the VC2 files almost as if they were PRG files, with intellisense, Document View, etc. You just can't compile as PRG because it is not a valid PRG, but those modifications are translated to the binary when reconverting later.
>
>
>And now something that you are interested on:
>
>>>>Would it be possible to generate per class like VCXName.ClassName.prg? (And create vcx by VCXName) Then it would be greate with git - very easy to trace changes and collaborate on class level. Also smaller files to merge.
>>>>
>>>
>>>No, sorry, it is not possible to do this separation, because this would require a hard and costly redisign of FoxBin2Prg, and because it is production-ready and many people are using with there systems (our teams included), I can't take this risk.
>>>
>
>I've been asked for this many times, and I'm analyzing the possibility of separating a class per file. I'm doing a proof of concept right now to see what problems I find doing this.
>
>For yes or no, I will say something about it soon. If yes, then surely will be a new option deactivated by default to not interfere with the default functionality.
>
>Keep tuned! :)
>
>Best Regards.-