What is this OO?
The recent discussion on OO programming has created quite a bit of discussion, some with more heat than light, but other thoughts that have been illuminating. Some discussions covered whether or not OO has "won" over procedural programming. Some have suggested that those avoiding OO do so because they are unable or unwilling to learn new things.
My favorite thing, however, was "sipping the [OO] kool-aid" by Matt Williams (I owe you a beer, Matt!).
When I thought of sipping the OO Kool-Aid I had in mind a basic application that simply puts similar logic or queries into a few encapsulated objects and uses those through out the application. Perhaps even just using DataMgr is a way to get into some OO concepts.
As for my personal sipping, I have been using OO frameworks for a few years now, but wouldn't consider myself an OO purist or always able to do it right. Why do it right the first time when refactoring is so much fun? Or at least it can be rewarding.
OK, I think I have the link fixed now.
The term "object" seems a bit loaded to me. I use CFCs that follow most OO principles with some frequency, but they aren't true objects except in rare conditions.
Nonetheless, I still like your thought of sipping the OO Kool-Aid. Good stuff!