Just to answer some points raised earlier about FoxInCloud... How it works ... (the basics) =============================
FoxInCloud server is a VFP wrapper around your app, interacting with the web server through a standard VFP-to-Web layer, west-wind web connect as of now. FoxInCloud server just needs to know (by property settings) which environment your app needs (SET PATH/PROC/CLASSLIB, etc.) and which forms you want to display as 'top level', IOW in an HTML page. Then FoxInCloud produces HTML/CSS/JS matching your forms as a standard base with your app's look and feel (same controls, layout, taborder, events, etc.); you can upgrade to another design through CSS and/or class or object level HTML generation. All HTML stuff is written into files located in your site's directory structure. When FiC server starts, it instantiates the above mention forms; by default a single instance of form serves all users, FiC takes care of saving and restoring form's state on each request of each particular user. Once you've build the whole page including FiC-generated form(s) HTML, that's what your user sees. Then user interacts with the form. All VFP events handled by the VFP form being also handled in the generated HTML, FoxInCloud client layer (standard javascript identical for any FiC app) sends event signature to FiC server (target object, value if any, keyboard state, mouse state, etc.) FiC server receives event, executes the corresponding event method on the corresponding VFP object. Then FiC server compares form's state before and after the request, identifies the differences for each object (enabled, color, position, etc.), and sends these back to FiC javascript for execution on the HTML page. It's just as if the HTML form was a 'slave' or a 'delegate' of the VFP form living on the server, sending events and getting orders back. Licensing and Pricing ====================== We've been working on this (difficult) subject for the last 2 months in close interaction with other fellows VFP developers. The stakes are not only to cover nearly 10 years of dev. cost, but also to ensure a nice product path and, we hope, being able to finance a 'next VFP' compiler to help VFP ISVs further save their assets and business. As everyone has noticed, the software industry is now for big players; low targeting just makes you sure you'll fail. It also appears that cloud offering can make some business today, and can solve the 'fox stinks' problem: when the fox runs on a web server, just no one can figure it out (foxincloud.com has php extensions though it runs 100% on VFP). Also, please keep in mind that FoxInCloud requires less than 2% code adaptation to let your application to the cloud http://foxincloud.com/shared-projects.php So we came up - I think - with a fair balance between making a solid, world-class product and let you guys make a good business out of it. We'll have both rental and perpetual licencing for a cost per user and per month between $.2 and $2.5 (don't have the exact figures on hand) All details will be soon on line, please stay tuned on http://foxincloud.com/ -- Thierry Nivelet FoxInCloud Give your VFP app a new life in the cloud http://foxincloud.com/ _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/4dbebb52.6080...@foxincloud.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
