Hi Hank,

>There are some things it is not intended to do: it will not use VCX's, SCX's, etc., nor run existing VFP reports. It will use ActiveX components on Windows; will not use FLL's. So I guess you can say that it's not really VFP running on the these other platforms. It is, however, VFP code (enhanced in several places: no 2GB file limits, parallel processing is a simple command that is cross-platform) running already on Win/Linux/Mac and shortly on iOS and Android.

I have been following the project forums and product roadmap as quite a few members in this forum I reckon. QT as a commanding environment seems a great choice.

I feel that that quite a few among the beta users COULD report on the global feeling about the VFP interpreter here. I understand that beta testers will not or may not report on performance. But an overall feeling feedback on the product would be welcome.

Is this Mobile QT target not getting a bit in the way when re-writing VFP UI?

How comfortable do old-hat VFP users feel with the fox interpreter embedded in the beast? Does the python engine deliver a distinct feeling? I am comfy with both python and VFP but, sure, have a dammed massive set of VFP code to leverage...

François
fox old-hat, 1986 edition
python recent chap, year 2000 and above