On 9/25/05, John Farrar <[EMAIL PROTECTED]> wrote: > Well, that sounds like an interesting implementation. One of the Rails rants > is to not put config files as such into XML.
That's true, but misses have the point -- the config files that Rails uses are written using YAML instead of XML. For most configuration purposes, they are pretty equivalent except YAML requires a lot less typing :) > That is why I started this thread to start with. I am not trying to > duplicate Rails point for point. What makes RoR so cool is how much it does > and that it is all packaged together. One of the principles of rails is > release fast and release often. If we follow that principle we can build > things one at a time, and keep adding on. That seems to be the way to go... > and I would like to start with the Active Record concept. ActiveRecord, while a crucial component of Rails, is not a new idea. The ActiveRecord pattern (http://www.martinfowler.com/eaaCatalog/activeRecord.html) is a generic application architecture pattern that the ActiveRecord package for Rails implements with great success. Hibernate is really similar in some ways -- both are Object-Relational mappers. And I agree -- CF has several MVC frameworks to choose from. An ActiveRecord implementation provides a needed component (ORM) that can be separated from the VC part of MVC. In Fusebox, the model layer is really undefined (and not strictly required since MVC is a choice) so plugging in vanilla CF code, CFCs, or an ActiveRecord implementation are all possible options. The real question in my mind is how simple can a CF-based ORM be? If extending ActiveRecord.cfc gives me CRUD for free, that's awesome. But knowing some Ruby and a bit about ActiveRecord in Rails, there's a *lot* going on under the hood that's easy in Ruby but probably harder in CF -- not impossible, just harder. -- John Paul Ashenfelter CTO/Transitionpoint (blog) http://www.ashenfelter.com (email) [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). 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]
