Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Sharing some stuf on VFP migration
Message
De
01/07/2013 15:07:59
 
 
À
01/07/2013 13:07:05
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Versions des environnements
Visual FoxPro:
VFP 9 SP2
OS:
Windows Server 2012
Network:
Windows 2008 Server
Database:
MS SQL Server
Application:
Web
Divers
Thread ID:
01577352
Message ID:
01577551
Vues:
115
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.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform