>>As I have said on my previous UT posting, we tried 3 frameworks, (CM, FE, MF - just a code in fairness to the vendors), they are good, but ohhh my…, a serious programmer, not a ‘Layout Artist’, could do even much better.
>
>That really depends on your way of thinking. As a professional contract programmer I wouldn't dream of writing an application framework. One of the prime tenets of OOP is reuse of code and not 'reinventing the wheel'. Why should I waste my time writing a framework when there are very good commercial ones available for me to use instead. Bear in mind that a good framework takes a long time to write. F1 Technologies took 3 years, Les Pinter took 2 years or so to write the one he uses, it's isn't a five minute job and it certainly isn't easy.
>
>You say that you evaluated 3. How long did you take for this evaluation? Why those three and isn't just 3 a bit of a small sample to then be saying that serious programmers could do better than this?
>
>Your implication is that the creators of the frameworks you evaluted are not serious programmers and you are, which is a laughable sentiment since these frameworks were written by probably the most respected programers in the FoxPro world. You also imply that since these three, in your opinion, are not suitable that the rest of the frameworks aren't either. Yet more nonsense.
>
>Mark Austen
>[Schooner Software Limited]

Thanks for your constructive comments.

I would appreciate if you map and read this specific topic in its entirety, so that you will understand the whole insights that I want to emphasize. I am absolutely not against Frameworks…

Besides, I am not referring to developers of frameworks but rather to the users of the frameworks (re: serious programmers). I must admit that developers of frameworks are serious and even better programmers than I expect them to be.

I would to clarify my stand on this matter:

Frameworks will be helpful if you want to develop End-User Apps and Make $$$ the faster way, but using them as your foundation to become a respective and serious VFP developer, IMHO, is counter productive because you will absolutely go back to the BASICS / STANDARDS of the language. It would be better if a developer, specifically beginners, will start from the BASICS of VFP rather than go directly to frameworks for a long term impact, and for them to have the right foundation, and then use frameworks, if they don’t want to have their own (it’s tiresome though), as a help for RAD purposes. On our case, no need, because the 3 frameworks I have mentioned, will not help us in a way because it is not applicable to our own frameworks. What we are expecting is get frameworks and get some tidbits to add it to our own, but it will not work because we must conform to their approach. And it is really hard to synchronize three different approach.