Clarke,
I used to be on the mailing list for CF Wheels in earlier versions.  It has
a solid approach.

Now, one of your statements about your selection of a framework mentions
that Transfer or Reactor was a learning curve point.  My warning to you is
that in the built in model syntax of CF Wheels, that you are trading perhaps
one syntax for another.  I will conceded that both Reactor and Transfer are
quite more robust in features and nuance, but there is still an object
hierarchy that can resemble other ORM approaches.

There is an appeal to using a file system based framework to determine
dependencies on your view and controller.

Also, there is a lexicon of functions in CF Wheels you will need to get
familiar with.  Some of these are to create code for you.  They are handy to
use, but I would learn what code is generated upon using these functions.
Once you understand what these functions are doing, you may want to move
away from some of them as you will probably need to code more strictly or
have requirements that the generic functions do not handle.


Teddy R. Payne, ACCFD
Google Talk - [email protected]



On Tue, Aug 11, 2009 at 10:07 AM, Clarke Bishop <[email protected]>wrote:

>  I was originally going to start with ColdBox to learn a ColdFusion
> framework. But, I quickly got lost in the complexity. To really use ColdBox,
> you end up needing to know Coldspring and Transfer. But, since each of those
> has a learning curve, it really makes things hard.
>
>
>
> So, I switched to CFWheels (http://cfwheels.org/ ). Wheels is a ColdFusion
> framework based on Ruby on Rails.
>
>
>
> Just like Rails, the CFWheels framework use an active record approach, so
> there’s no need for Transfer or Reactor. And, the object dependencies are
> also managed by the framework, so you don’t need Coldspring.
>
>
>
> There’s still a lot to learn because you have to learn to think the way the
> framework expects. And, you have to learn the conventions for how things
> should be named, etc.
>
>
>
> I found a great book that helped me adjust my thinking – Head First Rails.
> But, it’s Ruby/Rails, of course. I’ve found that the ideas translate fairly
> easily to CFWheels, and I’ve started converting the apps in the book to
> CFWheels. To help me learn it more deeply, I decided to blog about the
> process, so if you want, take a look at:
>
>
> http://www.resultantsys.com/index.php/coldfusion/cfwheels-scaffolding-basics/
>
>
>
> Thanks again for all the ideas and support I got from you guys. I’ll keep
> you posted on my progress!
>
>
>
>    Clarke
>
> -------------------------------------------------------------
> To unsubscribe from this list, manage your profile @
> http://www.acfug.org?fa=login.edituserform
>
> For more info, see http://www.acfug.org/mailinglists
> Archive @ http://www.mail-archive.com/discussion%40acfug.org/
> List hosted by FusionLink <http://www.fusionlink.com>
> -------------------------------------------------------------

Reply via email to