>Hi everybody,
>
>>BTW, some guys said don't have the nerve to jump in as if they see that participants are VFP big shots excluding me.
>
>That's too bad. The VFP community has always been known for their online discussions and the ability to involve people with different levels of expertise in one thread. I don't think we should loose this great aspect of our community.
>
>So, if you have to add something to this thread, please jump in!
>
>Christof
Hey All UTers!
I know I'm jumping in late, but couldn't help avoiding this thread. :)
IMHO, the major benefit of OOA/OOD/OOP is code reuse. Avoiding the reinventing of the wheel, as its been known. I have found this to be very true, even when it comes to app frameworks. This is the case with any ActiveX controls/VFP classes/procedure libraries/ and the entire shared DLL concept. Why would I want to recreate a control that already exists? If I can pay 200-300 for a control that would take me 3-4 times that to create, why would I?
In reference to using versus creating a framework, the cost saving for me are incredible regardless of project budgetlines. When I don't have to concentrate on the basics of the app, I have more time to work on how the app will work overall. More bang for the buck, in the end. The client gets more functionality or a smaller invoice, because I spend more quality time with the main functionality.
As for a new VFP programmer attempting to create a framework, IMHO, NOT WISE!
OOA/OOD/OOP are very intricate concepts, and attempting to learn these concepts and how they work into VFP can be a very daunting task. Using a framework can be a better learning experience as well.
Thank you for your ears. And I now regress.
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only