Yesterday on YouTube, I posted a video of a new developer workflow coming in Model-Glue 3 called "Event Generation."

When in developer mode, hitting a nonexistent event-handler can be configured to generate a conventions-based Controller, listener function, controller, and view.  

Basically, typing "index.cfm?event=order.list" gives you the following:

<ol>
<li>An OrderController will be generated if it doesn't exist</li>
<li>A listener function named "list" will be created in OrderController</li>
<li>A message-listener subscribing OrderController.list() to "order.list" will be generated, along with a controller tag if one does not exist.</li>
<li>A view in /order/list.cfm will be created.</li>
<li>An event-handler tag wiring all of this together is created in the XML file of your choice, defaulting to your main ModelGlue.xml</li>
</ol>

Here's a video of it in action:

One of my favorite features coming in MG3 is purely for developer ease of use:  hit an event that doesn't exist while in development mode, and it'll generate intelligently named controllers, listener functions, and views, wiring them all together with convention-based XML.

Here's a video of Event Generations (and a bit of SES features) in action:

<object width="425" height="350"> <param name="movie" value="http://www.youtube.com/v/qxseJAVsxUc"> </param> <embed src="http://www.youtube.com/v/qxseJAVsxUc" type="application/x-shockwave-flash" width="425" height="350"> </embed> </object>