Hi Fernando,

thanks for the reply.

I see your point. Logically it would be an option to create on a per class base.
The multifile problem should not be an problem - it need to be a transparent process anyway. Some prog to create prg and commit and some to checkout create vcx It would be to boring to do this over and over.

You mention to make mistakes. Argh, hm, basically one should do only merges (on source control level). Some mistakes you do here will corrupt the vcx. A large file is more danger if a block merge kills class boundaries.

and now the big question

>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.
vs
>2) Using the PRG-style version generated by FoxBin2Prg: You just copy the parts you want to another SC2/VC2 file and regenerate the binary from that. May be much faster than the other way

As I understand you generate a text file. (And the oppposite) The handling of SVC is not your part.

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.

off topic

>1) The traditional way: Using the VFP IDE (a pain)

Some danger copying classes around. Leaves a trail of problems in the VCX. The ID field will be the same. So if you copy a class to duplicate, you might end up with to classes using the same ID. No problem - until you use the code referenze to replace.

Lutz

>Hi Lutz:
>
>>I'm thinking to move to git (what I use for other problems). Do I understand that you generate one large file out of each vcx / scx etc?
>
>Yes, one VCX => one PRG-style file (as if you code this VCX library as a PRG library)
>
>
>>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.
>
>On the other hand I've used TwoFox which exports scx/vcx to XML in a per-file class basis, as you mention, and worked with it I can tell that it is a hell having thousands and thousands of files on the disk, that are not easy to maintain, and what is worse, if you make a mistake with some of those files you can have a corrupt library, because classes that are included in a library sometimes are designed to work together, so it is risky to maintain them separated.
>
>The real solution for this is separating classes in different libraries, a task that you can do in 2 ways:
>
>1) The traditional way: Using the VFP IDE (a pain)
>
>2) Using the PRG-style version generated by FoxBin2Prg: You just copy the parts you want to another SC2/VC2 file and regenerate the binary from that. May be much faster than the other way
>
>Regards.-