>...
>>A few years ago I seriously tried out both WinDev and Lianja and the conclusion was "not yet" on both, simply because both had the usual demo stuff to do simple things, which tells me nothing. Saw that with too many products before, where things get complicated really fast if you try to do something not similar to the demo. So I went looking for other things - the files, file structure, elements of a project, the basic plumbing, with one thing in mind: if I were to switch, how hard would it be to write a converter from vfp into this.
>>
>>With Lianja, as it was then, it would be cumbersome, it would take a lot of time, but in the end it sounded like something doable. With WinDev, sorry, I couldn't find where the code goes. I couldn't even find a way to write code any other way but keyboarding or coding into _cliptext and then manually pasting into a method whose name I'd have to type (or put into _cliptext separately and alt-tab thrice). With tens of thousands line of code this is... unacceptable. I may be the 2nd kind of lazy programmers, but not being able to write code writing code is a non-option for me.
>>
>>Now it was a number of years, so if I'm wrong I'd like to hear about it.
>
>Dragan,
>
>Wow - I have no idea how you could not figure this out. I do not consider myself a particularly great programmer but I had a basic, simple, test project up and running in days. There are 2 primary places where you write code: (1) in the code of the control (e.g. a button). You can double click the control and then choose the code button to open the code window. Or just right click the control and choose the code option, or (2) create a procedure file and then add procedures to it. Really these 2 options are identical to VFP. There are other places to add code but those are the 2 most common imo.
>
>The only thing I can think of is this: you should not approach WinDev (or really any other IDE/Dev-tool) with the VFP mindset/approach. One must learn the way that the new IDE/Dev-tool works. And to do this PCSoft always asks every new user to go through the entire course that they provide which I reckon someone of your caliber would get through in less than 1 week part-time. It's basic purpose is to introduce the basics of the IDE, windows (forms), databases, etc. It creates a project, a window, a few controls, some code, etc.
>
>I can say this, and have said so before in numerous posts: you can almost duplicate a VFP project into a WinDev project routine-for-routine, database-for-database, table-for-table, function-for-function, line-by-line. I have given examples of code in VFP compared to code in WinDev in this forum before - it is essentially a line for line comparable process.
>
>You create a project, you define the first Window (if it is a desktop app), you add code to the INIT, add controls, add code to the controls, create routines in procedure files, etc. it is so similar to VFP. If you like I am happy to give you an AnyDesk/TeamViewer access to my laptop where I can show you that what I write above is true.
>
>Now, whether WinDev can handle everything that VFP can handle - I cannot categorically say yes only because I dont know everything VFP can do, I dont know everything WinDev can do, I dont know everything that you are doing in VFP, etc. In other words, there are too many unknowns for me to be categorical in my answer. However, I would be willing to wager the answer is yes and even give odds that it can do everything and much more than VFP can.
>
>.

Jos, are you of the opinion that VFP was used by the WinDev people as a basis for their shipping product (easy to use.design/ etc. etc.)? Or was VFP developers targeted by WinDev once it became clear that VFP was at the end of line in development?