Hi Lutz! Over your message:

>'Hi Fernando,
>
>I have a small gap to look again at yout tool.
>
>I have several questions
>
>#1 I see you splt (as we have discauused before) VCX into multiple files. That sounds fine.

When you activate this functionallity, you just tell foxbin2prg that when converting to text generates 1 class per file, but when regenerating the binary, you have again only one binary (vcx/vct), but there are some options you can use depending on your goal:

This functionallity and the options "RedirectClassPerFileToMain:1" and "ClassPerFileCheck:1" are discussed in the Documentation, at this link:

https://vfpx.codeplex.com/wikipage?title=FoxBin2Prg Internals and Configuration


> What troubles me is: You mention that your header holds a list of the classes.
>

First of, it's assumed that you work with the VFP9 IDE on the VCX libraries, so here you have only one library with all the classes.

The thing is that if you want the "ClassPerFileCheck", then this list in the .vc2 file is used to make sure that only class names annotated here are included later when reassembling the VCX/VCT when searching the external "library.class.vc2" files.

Test case: Suppose you have a VCX with 3 classes, export it to text (1 .vc2 header and 3 .vc2 files generated) and then delete one of the classes in VCX within VFP9 IDE. If you re-export to text the 3rd .vc2 class file is not generated, but the old one is not deleted, so if you want to reassemble the VCX and have configured "ClassPerFileCheck:1" this 3rd file is not usd, because in the header it is not anymore (was overwriten in 2nd text regeneration and taked off the list).
But if you don't use "ClassPerFileCheck:1", then this 3rd file is included again (because the internal list is not checked) and when regenerating the VCX the deleted class is there again, except if you previously delete the 3rd class file.


>Whats your idea how to merge a new class? simple add the line to the header representation and make sure the file for the class exists?
>

Yes, if "ClassPerFileCheck" option is enabled. If it is not enabled, then all the filename.class.vc2 files that begin with the corresponding filename are included without checking.

If you don't enable "RedirectClassPerFileToMain", then you can create individual VCX files with each filename.class.vc2
This option is useful if you want to phisically separate a big classlib in individual classes, or want so separate one or more classes of the classlib.


>#2 Will calling the prog with a pjx just transform the pjx or will it run through the files included? If not, do you have a prog doing this? (I just do not see it, I can do myself and provide it, if you like)
>

Calling with ["PJX"] just convert to text (PJ2), but calling with ["PJX", "*"] converts the entire project with all the files contained to text.
This is explained in the examples of the Documentation on VFPx:

https://vfpx.codeplex.com/wikipage?title=FoxBin2Prg


>#3 If I fix same slight mistranslations how should I ship the source back to you?
>

As you saw, the translations are now internal, as a class on the lower part of foxbin2prg.prg program, so you can send me the "CASE" statement block with the translations to my email (you have it on top header of foxbin2prg.prg file)


>Thanks
>
>Lutz