FoxInCloud adapts an existing VFP app to run on a Web server through an HTML/CSS/JS user interface modeled on the original VFP forms.

FoxInCloud server is a VFP wrapper around the application which:
(1) produces HTML/CSS/JS,
(2) interfaces app to the web server through west-wind web connect
(3) executes VFP app's event methods for whatever action user performs on the (generated) HTML page.

Application UI can be totally redesigned based on HTML CSS.
Developer does not need to program in javaScript as it is either 3rd party or generated by FoxInCloud based on original VFP controls behavior.

FoxInCloud concept is quite similar to VisualWebGUI's, with 2 main differences:
(1) FoxInCloud concept was invented over 10 years ago, and shared along times with the community (on our web site and/or west-wind message board)
(2) With FoxInCloud, over 98% of your code base needs absolutely no change/rewrite/rework whatsoever (http://foxincloud.com/shared-projects.php), VisualWebGUI claims 80%.

2 hot news about FoxInCloud:
(1) We shall shortly release a brand new licensing policy, in response to the various - and very pertinent - feedback the community kindly provided us;
(2) You can test a real-life, 50-form, 25-report, 2,000-object, 1,200-event, PostGreSQL-backend FoxInCloud VFP application here: http://foxincloud.com/BSW/
This is a test database, you can go ahead testing, saving, etc.
PS - sorry for the French texts - application is about managing a set of biology laboratory shops (where you give blood sample, etc.)





>I don't think FoxInCloud does desktop apps so they can run natively like on Mac though, which Servoy does do.
>
>>>I looked at some videos. Servoy looks nice but...
>>>
>>>Not sure I have everything but here's what I need
>>>
>>
>>
>>FoxInCloud deserves a look too I think. It uses JavaScript/Ajax and keeps the backend in VFP. If Servoy does it right they too will have a JavaScript/Ajax frontend but the backend logic will be converted to Java (which I see as the expensive part) and the database is converted (which also may be expensive). So you may end up after a year or so saying why couldn't we have just converted the frontend to JavaScript/AJAX (what everyone is doing anyway) and kept our royalty free backend?? Just food for thought - I think Servoy needs to make their value proposition better.