The only adventage of using VCXs over PRGs is that: - Descriptions of the methods and properties are shown by intellisense when you scroll them while using an instantiated class, which is not possible with PRGs, except PRG-COM classes instantiated from the registered Windows object. - Can be created (NewObject) from external exes/apps (with PRGs just the main program with SET PROCEDURE)
On the other side, PRGs have plenty of adventages over VCX: - The text never gets corrupted - You can define the type of procs/funcs parameters and their returned values (useful for COM) - Better for merging in a SCM/DVCS tool - It is the only way to use the Session class - Easier for bach-replacing between a bunch of files (you can do that with the tx2 versions generated by FoxBin2Prg, but then you need to regenarate the binaries, which is an extra step)
Fernando D. Bozzo
2017-02-21 15:15 GMT+01:00 Ted Roche tedroche@gmail.com:
On Mon, Feb 20, 2017 at 3:53 PM, Alan Bourke alanpbourke@fastmail.fm wrote:
Yep. In fact I don't think UI code/markup/metadata lends itself well to source control in any language on any platform.
I think that's overly broad. HyperText Markup Language works well in source control. And the corresponding CSS and JavaScript. The minimized and obfuscated versions are like object and executable code and good to run with but less fun to version.
-- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com
[excessive quoting removed by server]