Sammy, As someone who is self-taught, I'm saying that the language, the pattern lingo that is used, can be a barrier to understanding what ColdSpring can do for you in simple terms. It tends to imply to the learner that they need to study OO patterns before they can use a framework.
If instead, one says to an aspiring OO newbie who is self-taught: ColdSpring can instantiate (linked to a clear and simple definition) the objects or CFCs that your whole application needs for you, and wire them together so that they can work with each other. As anyone who has tried to architect an application that uses CFCs can tell you, working out how the CFCs should work together can be one of the most difficult parts of designing and coding your application, especially for a beginner. As you progress, it often involves reworking of your code significantly, and can easily introduce mistakes. This is particularly true if someone is inexperienced with object orientation and hasn't come to the point where they have a preferred way of organizing their objects to work together. It's also certainly true for an experienced programmer, because new requirements or unrecognized aspects of the application can pop up at any time, forcing you to rethink your design. ColdSpring uses a simple XML language in it's configuration file that is easy to pick up. Depending on your level of experience, it can take anywhere from a hour or two to learn the basics, to perhaps a day if you are really new to all this. To reorganize the way your CFC's work together or add another CFC to your app, you can simply and quickly rewire them in the config file (and perhaps add a bit of code to your objects). Here are some examples to get you started: .... .... .... Then show some comprehensive examples, so they can start using it immediately (although certainly not as well as an experienced OO architect). Explain a few cavets along the way. And that opens doors to further learning, as experience is an excellent teacher. At the end, you can say: By the way, ColdSpring is based on the Java framework Spring. In object oriented pattern speak, it's an Inversion of Control container. For further reading and study, http://www.martinfowler.com/articles/injection.html is a good place to start. On 3/14/07, Sammy Larbi <[EMAIL PROTECTED]> wrote:
Nando wrote, On 3/13/2007 5:02 PM: > > > IF ... someone is new to CFCs and OO and all this lingo, they can > certainly use ColdSpring without conceptually understanding Inversion > of Control. But it probably doesn't at all seem like it to them. > They could, but how would they know they wanted to, or that it would be beneficial in particular cases? 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]
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]
