I understand how ColdSpring is a little more difficult to get from the documentation, which is in a way high level and borrows terminology from Java and Spring. It wasn't until i just tried it, following a few examples, that it became suddenly really simple to understand, and very useful.
I have a blog post here were i step by step walk through autowiring in Model-Glue: http://aria-media.com/blog/index.cfm/2006/9/22/The-Mystery-of-AutoWiring "To use autowiring, you need to mess a little with ColdSpring. ColdSpring calls everything by a different name, so that makes it seem kind of foreign in the beginning. A CFC is called a bean, a struct is called a map, an array is called a list, and so on. But once you translate the terms used and get to know your way around a little, it suddenly can seem very easy to use." There are ColdSpring examples in there. I'm pretty sure if you read thru the post, it might help you to understand ColdSpring better. Nando
Yes, I've read about both, but Transfer seemed to immediately "click" in a way that ColdSpring didn't. I understand they play different roles. And its nothing against ColdSpring. I just suspect its going to take a bit longer to get comfortable with.
You are subscribed to cfcdev. To unsubscribe, please follow the instructions at http://www.cfczone.org/listserv.cfm CFCDev is supported by: Katapult Media, Inc. We are cool code geeks looking for fun projects to rock! www.katapultmedia.com An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
