Playing with the Glue, Again.
Well, yesterday I started looking at Model-Glue, Transfer, and ColdSpring again. After about 14 hours of playing around I am starting to understand the flow of writing MG applications. Also, examining the code for Ray's CFLib2008 project helped quite a bit.
One of the biggest sticking points with MG, when you are not very familiar with MVC architecture it can be frustrating. For example:
<cffunction name="init" access="public" output="false" hint="Constructor">
<cfreturn this />
</cffunction>
<cffunction name="getUsers" access="public" output="false" hint="I return a query of users" >
<cfargument name="event">
<cfset arguments.event.setValue("users", beans.userService.getUsers()) />
</cffunction>
</cfcomponent>
Above is a simple controller with just one member, getUsers(). It works fine as is, but remove the beans="userService" in the component definition and you may find yourself speaking in tongues. Well, I was anyway. ;) I know it may be common sense for some of you, but it is the first time I have ever encountered it. If it wasn't for Ray's CFLib2008 code I would be speaking in tongues still.
I suppose I understand events and event-listeners and handling views. I suppose I need a better understanding of how to use my objects within the framework.
Against someones advice I was playing with Transfer and ColdSpring at the same time as well. Actually, these two apps were much easier to wrap my head around than writing MVC code. After seeing how easy it was to implement Transfer I could almost slap myself for being too stubborn to use it before.
Really I haven't done too much with ColdSpring as of yet as I don't have many components in my "learning application." There is always tomorrow.
