Dave, I can understand how it seems at this point that you're just creating more work for yourself, but if you can hang in there for awhile and follow thru with these principles, you're probably going to find that suddenly the momentum shifts. You'll be going downhill a lot of the time, rather than uphill. You'll have a fully developed model that you can adapt and use anywhere in your application.
Once you understand how to create a decent model and use it, your development will clip along much faster than it does today, and you'll come up with better solutions. At least that's been my experience so far. But i can understand how it doesn't look like that at all in the beginning - because it just doesn't! It's hard to see the benefits, but they are there. <snip> all MVC really does in this context is make you add new methods to three CFCs instead of one. Not to make light of the great framework work folks are doing, but the Fred part of me still likes that better than editing XML files just to tell the engine about a new method (that I also have to write code for), or where to find existing components (;-). </snip> ---------------------------------------------------------- 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). An archive of the CFCDev list is available at www.mail-archive.com/[email protected] ---------------------------------------------------------- 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). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
