>>As I mentioned on this great forum, although I still maintain VFP code, my "development ecosystem" of choice is now python. My current stake: move a relatively significant VFP-client (50k lines) to python with a view to run the UI layers within QT. This is NOT done at this stage:)
>
>50k lines ... FYI, there is a FoxInCloud application with 50k lines / 55 forms running in production for over 2 years
>http://foxincloud.com/shared-projects.php, application named 'bsw' > http://ctb.wanagain.net/ (login required)

I will certainly give a look:)

>http://qtweb.net/
>What interest do you find in QT compared to other browsers?

I am not looking at QT as an HTML-centric Web-platform of any sort. I admit to know very little on Qt HTML support.

This modest app essentially competes with MS-Excel for some highly specialised data crunching and visualisation. It should have been developed with a more appropriative tool set (VB, VC or Delphi). It happens to be a VFP hack. No intention to try to rewrite a graphic tool as a disconnected javascript app (I am no google-payed JS wonder-boy) just deliver a solid old-style application. Possibly document-centric in order to belong the dinosaurs...

In the realm, my feeling is that QT is offering what MS and Java never did: a rich cross-platform experience with both traditional UI à la Mac-Win32, and an evolutionary path on leaner platforms via QML. It is by the way a nice local European effort - digia - that IMHO is worth pushing in front of MS, google and al:)

I just regret that I did moved onto QT earlier.