fusebox.xml:
<classes>
<class alias="controller" classpath="fbmg.controller.Controller"
mg:needStuff="getStuff" />
</classes>
<circuits>
<circuit alias="do" path="controller/" />
</circuits>
<parameters>
<parameter name="mode" value="development-no-load" />
<parameter name="defaultFuseaction" value="do.welcome" />
</parameters>
</fusebox>
circuit.xml:
<fuseaction name="welcome">
<mg:broadcasts>
<mg:message name="needStuff" />
</mg:broadcasts>
<mg:views>
<mg:include template="main.cfm" />
</mg:views>
</fuseaction>
</circuit>
Controller.cfc:
<cffunction name="getStuff" returntype="void" access="public" output="true">
<cfargument name="attrs" type="struct" required="true" />
<cfset arguments.attrs.stuff = "1234" />
</cffunction>
</cfcomponent>
views/main.cfm:
<p>This is the main Model-Glue view.</p>
<p>This is the stuff: #viewState.getValue('stuff')#.</p>
</cfoutput>
This is using what will be the Alpha 2 codebase...
The example above uses a custom lexicon ("ModelGlue") that contains a handle of custom verbs I wrote ("broadcasts", "message", "views", "include") to allow Fusebox applications to be written in the style of Model-Glue applications - there's no Model-Glue framework here, just a similar grammar style. It's intended to show how custom lexicons let you extend the Fusebox grammar.
In terms of "speaking for itself", I'm assuming readers know both Fusebox and Model-Glue...
I think it also shows how custom lexicons let you seamlessly use CFCs with Fusebox which was one of my goals for this release.
I really want to take Canvas Wiki and drop it into a FB format and the lexicon would be a great process.
http://corfield.org/entry/Fusebox_5_in_a_ModelGlue_style
