Hi Jordan,

That is the direction we are taking. We have developed classes that perform certain functions that we require (like a form manager) and they have been incorporated into the app but not an actual framework. The original application was originally created in 1993 and developed over a period of 10 years so I don't see any major redesign (other than those classes and 3rd prty controls we have incorporated during the vfp8 conversion) in the near future.

I have used frameworks in the past so I know what a boost they can be in creating new applications. We are still researching the frameworks to choose one for future development in VFP. I have worked with a couple and have my favorites but it will depend on our longterm goals of course.


>>A pre-existing VFP application built entirely in VFP with no framework or third party components at all. Typically, frameworks are used entirely for new development or in other words, all new apps created from scratch. There is typically no way to bring any of the classes/controls from a framework into an existing app and have them function correctly without the underlying framework dependencies bomb. I was hoping one of the frameworks out there allowed this.
>>
>>
>>
>>
>>>What do you meant "vanilla Visual FoxPro app"?
>
>I suppose that you build your own frame work. It is most suitable for it.
>Only you need to add to it a few classes. Unfortunatelly all fimrs which offer framework try to catch you and it is more easy to develop class from scratch than to transfer apps on the framework. Some times apps do not need to be tied to framework. According it specifications it could become slowly if you try to put on the framework. Using framework you should add a bunch of useless code.
>For our applications we create framework according RFP and add only this classes and libraries which application needs.