Hi,

I have a suggestion for FiC Web Application Studio which I think will help people, especially those who are just at the experimental/prototype stage and not production - specify a resource file in its AW*.fpw file that is specific to FiC.

I have branched my project into a separate directory (and drive) for the purposes of learning FiC and creating a prototype and have found that sharing a resource file with my production project can occasionally cause problems, particularly with the default search path and menu generator settings.
Using a separate resource file prevents any crossover problems.

Thanks
Paul

Hi Paul,

Thanks for your nice suggestion; we'll work on that.

Hi, I've been trying to install the FIC for a long time without success. So I would like to suggest the creation of a cloud environment, where the FIC team would sell the cloud space, with the guarantee of application functions and support, updates and improvements. This FWAS could migrate the projects directly to this cloud

Hi Sergio,

Controversial subject: many devs interested in FoxInCloud are frightened by the risk that FoxInCloud would impose hosting their app in 'our' cloud, outside of their client premises. Which is a totally wrong assertion or fear: one can host a FoxInCloud Web Application on any server of her/his choice: in-house, hosted, delegated, private, whatever.

Maybe the name 'FoxInCloud' suggests that; downside of choosing a trendy brand name: one get confused with mainstream marketing messages.

Right now you can update your production FoxInCloud app by simply pressing a button (running a program in fact); we could imagine doing the same for installing your app on a remote server (with all due care for delegation of responsibility over data, etc.).

In any case you need to perform some adaptions manually; we could imagine automate more adaptations that are currently manual; however we know how complicated it would be, and consequently how much it'd cost: we'd almost need to write a VFP code parser like in the current compiler, and capable of detecting dependencies across modules (eg. being able to differentiate between variables and table fields). Requires much more revenue than we currently have!

Hi Paul,

re-reading your suggestion I wonder whether you need a different config or resource file.

the items you mention (path and menu generator) are controlled by the config file, the resource file being more in charge of saving windows' font, size, position, etc.

the default config file (awTrial.fpw) is as follows:

; VFP config file for FoxInCloud Web Application Studio shortcut

title=FoxInCloud Web Application Studio - Trial
path=..\..\..\;..\..\..\FFC;..\..\;..\;..\Graphics\;..\AT\;..\AW\
_startup=
command=do (home(1)+"tools\ab\aw\aw.app") with .t.

_startup= removes your usual startup program to avoid altering the required set('path'), set('procedure'), etc.

you can specify your own config file in the FoxInCloud Web Application Studio shortcut, which the installation should not overwrite.

please feedback if such a solution can fit.

Yes, you are right.
So far just specifying a different resource file has made life easier for other reasons, breakpoints for example.

Paul