Just to clarify, it seems from your piost you think I work for FoxInCloud. I am a developer, I do not work for them.

Most of your info is not correct, at least as of today. You can run a complete demo quite easily; but importing forms without adapting them des not make sense - adapting them is what FiC calls the process of adding the HTML. Not much sense without that!

There has never been a case of not being able to run FiC, but I think what you are referring to is that there is minimal documentation. But the docs do show how to do a trial setup - albeit the docs may not be great.

You are comparing apples and oranges. The purpose of FiC is to take VFP and run it as HMTL/JS while still keeping the VFP project and code. Just like anything that requires a website, as opposed to a desktop, you are going to need a website - which means IIS in the Windows world. I can deploy a new FiC website in under 10 minutes.

It is almost alays irresponsible to convert something to another platform solely to do so, and almost always doomed to fail. It may be fun, but I can take any VFP app and adapt it to HTML/JS/CSS in a small fraction of the time and money it would cost to convert.

I could say "Hello, client. I would like to charge you a lot of money to take you working app and convert it to another platform. As we agreed, this new platform is terrific. Of course, it is a niche platform, and not the industry standard HTML/JS, but don't worry. If our new niche platform becomes obsolete, I will find an other new niche platform and we can spend the money all over again. And the best part is that you get, in the end, the same app you have now! Can I get a check, please?"

Or I could say "Hello, client. For a pretty small fee I can adapt your app to run as HTML/JS with every possible HTML feature available today - look at my cool jQuery libs -- and then you can develop enhancements either in VFP or HTML/JS. You can also have your desktop version, and a mobile HTML site. And you risk nothing in potential obsolete platforms -- HTML/JS/CSS ain't going anywhere anytime soon. And if a really great, widely accepted new platform were to be invented in 10 years, you are set for that. The only catch is the server should be IIS (not Linux)."



>Ok, as I have been helping people here to run FIC I have noticed that the process is somehow harder than competing products.
>It would have been easier to have something like a "central Launcher" installed in wich you can have example apps, your own apps, importers and so on, Look at Lianja's App Builder to have an idea of what it would look like. In that central launcher you can incorporate a "simplified" mode with can import forms w/o the need to adapt, adding callbacks and some stuf needed to make them work without the conversion. Now you have to go through a paper wich explains some concepts, wich of course will be needed later but for a test drive is a no-no.
>I agree that FIC is a very good option and that the cost is very reasonable, but I have hear in many groups about people that are unable to even run the product properly. Those are lost customers and maybe that would explain why FIC doesn't have te customer base it deserves.
>So my sugestion is that you take a look at Lianja, WebDev, Wakanda or any other RAD and get some ideas about improvements that could help you to get the user base you need,
>
>>I am not sure what you are referring to. The point of FiC is to run VFP apps/forms as HTML/JS on the web while still maintaining complete VFP native capabilities and usage. The FiC demo "adapts" forms by adding FiC classes for various web translation functions and then displays those forms in HTML from a demo local website it adds to IIS. Part of that process is installing WWWC, which FiC uses for various "behind the scenes" tasks.
>>
>>No conversions needed, no new languages necessary (you are free to use any javascript, jquery, prototype etc. but it is not required), entire apps that would take who knows how many hundreds of hours to convert to a different platform can be both VP and the largest most long term plaform of HTML/JS.
>>
>>Almost a no brainer. Hard to see why anybody would convert a VFP app to a different platform - a rewrite - when they can have HTML/JS with no rewrite. Cost is also pretty reasonable.
>>
>>
>>>I did that but first you have to convert forms. Seriously, think about an easier way to make your customers setup FIC environment. Compare your install with Lianja or even wakanda. Maybe a central base for FIC apps, a FIC importer and so on.....Sadly you can't make a virtual machine due to the IIS restriction.
>>>>That exists already, the FiC wizard makes an HTML page with links to all your forms.
>>>>
>>>>>I mean WWC license for trial FIC instalations, limited to 30 uses or so, w/o the nagscreens.
>>>>>Also, I now that its not rocket science to have your FIC instalation in production, but I think you could get more users with a "simple" mode wich makes assumptions about forms and callbacks> The idea is to have the testers looking amazed at their forms on the web only with a couple of clicks.
>>>>>
>>>>>>You can do a point and click install of FiC on a developmet server, and WWC is fully licensed.
>>>>>>
>>>>>>
>>>>>>>My point with FIC is that it can be used a developmente environment on its own for new projects. They have enought VFP characteristics translated and they generate the JS/CSS stuff needed. For the West Wind stuff, they may negociate a version with 30 or su uses w/o the nagscreen. But you can't simply run the FIC installers and watch the magic happes, you have to set up IIS, permisions, change your VFP code and so on. One downside, of course, is IIS itself. You can't target a standard Apache server.