Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Examples of 'Fighting the Framework' in MM
Message
From
27/05/1999 09:27:14
 
 
To
26/05/1999 15:48:14
General information
Forum:
Visual FoxPro
Category:
The Mere Mortals Framework
Miscellaneous
Thread ID:
00223147
Message ID:
00223402
Views:
28
>I'm considering buying mere mortals as my development framework. Every framework has limits -- not merely in what it's can't do (all decent frameworks have hooks for customization) but in what is harder within the framework than outside it. Every framework has certain things which are 'fighting the framework' -- harder to do inside the framework than they would be outside.
>
>My question: As MM users, what have you tried to do that turned out to be outside the framework? Please give me some examples.
>
>Don't worry about scaring me off. In making the decision to use a framework, I'm making the decision to live with this type of limitation. But I do not want major suprises in this regard.
>
>Thanks
>
>Gar
>
>P.S every framework has bugs as well. But if anyone has run into a deadly bug, one that just destroys or drastically lowers the value of MM for you, of course I want to know that too.
>
>Thanks again

I've been using the framework for a number of years now, and it is very flexible if you are willing to invest the time to learn it. One of the things I found, though, is that business objects don't have a lot of flexibility in terms of updating records in table buffered cursors. I would like the option of scanning the modified records, updating one record at a time, and the option of presenting a user with oldval and curval if there are any update conflicts. In some situations this would be useful.

Kevin is aware of this request, and will probably address it. One thing I know, if you have any issues, Kevin is very responsive about incorporating changes into the framework if everyone will benefit from them. Most of the time, the framework suits my needs, and I have developed some fairly complex applications.

Codebook is not for everyone. The concepts are hard to grasp if you are new to OOP, and codebook starting using the concept of separating the business rules from the interface and data source long before it was actually possible to do so. Now that VFP supports multithreaded COM objects, the framework's use of business objects is uniquely positioned to take full advantage of this new functionality.

I love the framework, and I have run into some limitations. But I have always found a way around them that did not violate the framework's overall design and intended functionality.


Sincerely,

Jim Weil
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform