>>>>That's OK. Just remember that with WebDev you will be tackling two things; (1) comparing WLanguage with VFP language, and (2) needing to think about a stateless, "split" application running partly on a client and partly on a server. I mention this because obviously VFP does not do the 2nd aspect.
>>>
>>>Running stateless, and splitting the work between server (done in your language of choice) and client (in javascript + whatever framework you use for it) is the same distance from desktop development, regardless of the language. Some schizophrenia may help there :).
>>
>>Hi Dragan, I'm not quite understanding your post. In a desktop app the state is always there, until the app ends. Variables are maintained, database connections are maintained, etc. ,etc. for as long as the app is running. In a web environment the state between client/server calls must be thought about differently and, imo, more carefully/explicitly.
>
>Exactly. My point is that you have that difference in any tool that can do both. Doesn't matter whether your serverside app is written in Fox, PHP, WinDev or whatever, it still has to be stateless (or to have a way to restore state on each new page from the same visitor). If your app runs on a desktop, it's a different kettle of worms - when the user clicks the next thing, you know it's still the same users, and that he sees whatever your app is holding at the moment - so you can keep your tables open, you can use the values from the current record, you can use the same user settings as a moment ago etc etc. In a web app, you can't.

Yes, I wasn't implying that only WinDev handles the server/client stateless issue. I was just pointing out to Victor that choosing WebDev to evaluate WinDev requires not only evaluating the language/IDE differences but also thinking about stateless application development (assuming he had not already done such apps).