That is my point. Building UI's in reality, should not encompass a large part of the development effort. The bulk of the work is in the analysis and design of the business processes that the app needs to put in place and work with. All of that logic is in the middle tier. Putting UI's together should not be that big a deal. However, it always seems to take a dis-proportionate amount of time. You know the deal, getting that textbox in just the right position....

So, I am left with the following...

VFP frameworks provide the most utility for VFP-like applications. Those applications that are primarily desktop, single-two tier applications that access local VFP data. The major utility is derived from the their UI centricity. This is counter to where the rest of the world is.

In terms of it being a complete framework, I would say that it is. After all, application logic does not belong in the UI. For UI's, I would suggest the productivity gains can be made through the use of templates. i.e, there not really framework issues....



>Wasn't it you that was arguing that for middle tier objects, inheritance wasn't much of an issue? I agree.
>
>But I wouldn't call this a fairly complete framework without UI elements. (Complete, I guess for its purpose.) But of the people that I know that choose VFP over VB, it isn't because VFP excels at middle-tier components- its because it makes building a rich UI simple, and speed of access and manipulation of local data.
>
>The framework that yoiu pointed out showed me enough to make me ponder switching to VB for the next project I have to build business objects into COM components on.
>
>>How do feel about the premise that folks shun VB because of a lack of commercial frameworks? Is this an accurate outlook? Somehow, a fairly complete OO framework was put together, all without inheritance.
>>
>>>>It is interesting that after I made this post, only one response, yours, has been made....
>>>
>>>I checked it out. Looks cool.