I have checked out FIC a while back and decided not to argue pro or contra on a similar question.
First of all, look not only at the time estimate from the conversion run, but check out how that estimate is composed.
My guess is that for "typical" conversion tasks the estimate was quite high compared to my guess.
Back then FIC had no support for TeeViews - make certain all your controls are covered (Dotnet / activeX controls used?)

FIC could be viewed as a special kind of fwk along "typical" JS fwk lines - good as it allows easy porting, bad if too dependant/tightly coupled to the implementation of the fwk. Reset your mind from all project knowledge and try to estimate how much the 'ported app would be coupled to the FIC layer implementing the base vfp stuff. Perhaps have a JS developer look it over, as you probably feel at home with more vfp base assumptions than a web developer.

Spot checks on sources and perf did not turn up something ugly - solid stuff, not up the the stellar comparison Rick creates but wth more attention to detail than many other sources.


>Tore,
>sorry about the slow response. In Message ID 1642728 Thierry said:
>
>"> Hopefully FoxInCloud can do the initial conversion and then the web developers can take over and run with it changing out whatever they see fit.
>
>Yes, FoxInCloud can / is meant to do that.
>
>FoxInCloud generates a Web app where you have full control over user events.
>You or any developer can, at any time, instruct FoxInCloud to ignore some user events that are implemented using another framework such as Angular or React, and another backend such as asp.net, Java or PHP. Of course you can also adapt the HTML generated to fit into these frameworks."
>
>
>>What has Thierry written that contradicts what I wrote? I have worked with FiC, and it was mostly VFP programming together with FiC base classes. FIC converts your VFP code to HTML, javascript and CSS. You can freely add your own javascript code, but it's still VFP code and VFP doing most of the work.
>>
>>>That differs from what Thierry has stated
>>>
>>>>FoxInCloud depends on doing most of the actual programming in VFP, with West-Wind Web Connection as back end.
>>>>
>>>>>Thanks. No, the client does not expect everything to be in javascript. They are looking at a quick way to move away from maintaining a VFP system as they are seeing it more and more difficult to find developers with the necessary skills.
>>>>>
>>>>>I am hoping that FoxInCloud can do this initial conversion for them and then they can get their web developers to take over.
>>>>>
>>>>>>The JavaScript every movement is as ridiculous as the Java everywhere movement. It's just not practical nor does it make sense. It's difficult to maintain.
>>>>>>
>>>>>>I'd ask your customer what he expects to gain from going all JavaScript and research the good and bad of each piece of the application and explain to him the good and bad of that.
>>>>>>
>>>>>>>Please expound on this.