Yes, that was a really, really good post! -Joe
On 7/12/05, Mike Tangorre <[EMAIL PROTECTED]> wrote: > Nicely put Nando. > > > Nando wrote: > > Just to add something here, Nathan's post below is a good example of OO in > > practice. As you can see, Nathan is addressing higher level concepts. Namely > > what an object should know and be able to do, and how various objects are > > related and should work together. I can tell you from experience, it takes > > awhile before it begins to click! > > > > You'll very most likely need to get your feet wet on familiar ground before > > you can jump into using MachII. Joe's suggestion to start with attempting to > > implement a little OO in fusebox is a very good suggestion, especially if > > you're trying to work this out on your own, without an experienced mentor at > > your side. That's the route i took, after realizing that even to do the > > simpliest thing in MachII, i needed to know how to develop a an object > > oriented model. In other words, i needed to know how to think like Nathan is > > thinking below. And sometimes you need to think really hard about something > > before you feel like your model starts to click into place, especially in > > the beginning when you don't have much experience. > > > > "What should a user be able to do? Why not just let users authenticate > > themselves and save myself the work? Is a Permission an object in it's own > > right, or just a property of User? What should i call this object? What > > should i call this method?" > > > > And you'll probably change your mind many times on the way as you gain more > > experience about how best to do something. And you'll want to refactor / > > rewrite your OO cfc's and try it out. > > > > To use an analogy, starting OO in Fusebox allows you to begin in a "corner" > > of an app, like the user login for example, experment, and see it working, > > while leaving the rest of the app procedural. Then you get drawn in a little > > deeper as you begin to modify other corners. You then might find yourself > > completely rebuilding 2 "corners" in a different way and adding a "wall" > > between them. Then you might tear it all down, and do it again, this time > > properly encapsulating your objects and experimenting with using composition > > rather than inheritance. > > > > It's a lot of work to learn, but it's well worth it. :) > > > > > > ---------------------------------------------------------- > You are subscribed to cfcdev. To unsubscribe, send an email to > [email protected] with the words 'unsubscribe cfcdev' as the subject of the > email. > > CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting > (www.cfxhosting.com). > > CFCDev is supported by New Atlanta, makers of BlueDragon > http://www.newatlanta.com/products/bluedragon/index.cfm > > An archive of the CFCDev list is available at > www.mail-archive.com/[email protected] > > > -- Get Glued! The Model-Glue ColdFusion Framework http://www.model-glue.com ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
