>>An old UTer, Peter Robinson, once did convert all of his forms into .prg based classes. The end result: the app was half the old size, and the instantiation of forms was about twice as fast. Of course, he had to have some discipline about it - some kind of semiautomatic layout based on a 12px grid, and he used Courier everywhere - unnecessarily IMO but he did that even in vcx/scx based times - but it worked damn well and he said that it was worth the effort.
>
>CPU power, HDD space, RAM and bandwith are cheaper then me. If I would need to wotk in prg I would be half as fast - the pain to look up an inherited method ..... no NO NOOOO
>This is my sole life. No time to waste.

This was 13 years ago.

>Diff goes through git, this is text based, no problem on that. Using Ultracompare from git diff
>
>work focused per method / event no lurking between methods. Change of Method / object.method is fast through combobox / property sheet / visual representation

Too much scrolling, IMO. There are oodles of properties I never use. Intellisense is faster.

>If I need to work on prg level or with somethin else then VFP I'm confused in all the files or the endless file.

That's why we server only the best drinks at those naming conventions :).

>Normaly I'm not up to visual programing.
>The vcx is a frame to keep it together. Most of the wizzard / drag and drop stuff is not used by me. Also I do not need to fiddle with the class definition overhead, this is done by the VCX.

The vcx is there to keep the presentation in place; the biz_something.prg is there to keep the logic in one place. Once I began separating them, my life became much easier. That, too, began a dozen or more years ago.

>The real good is that everybody can work as it suits - even on old fashioned DBX style or @SAY.

Cobol also still lives :).