|
First cut at a potential FB6 feature: implicit circuits. Pure proof of concept.
Right now, if you ask for fuseaction=somecircuit.someaction, and no somecircuit alias is
declared, FB6 will look in the controller/ subdirectory of your app for a CFC called
somecircuit.cfc and call a method someaction() passing in myFusebox and event. If it can't
find that, it looks in the somecircuit/ subdirectory for a CFC called someaction.cfc and
calls a do() method on that. If that doesn't work, it looks for somecircuit/someaction.cfm
and simply includes it.
I have a lot of notes on why this is not the cleanest way to handle things and I think I
can come up with some slick ways to make XML-free Fusebox a very simple and natural way
to build applications quickly.
Definite plans include: adding a dynamic do(action="circ.faction") method to myFusebox and
include(template="fusename",circuit="alias") method as well; extending the compiler to be
able to compile a single fuseaction to do.somecircuit.someaction.cfm (to support the do()
method); adding automatic conventions for CFCs in controller/ and model/ circuits as well
as view/somecircuit/someaction.cfm view files; also allowing somecircuit/someaction.cfm
in controller/ and model/ for consistency.
Again, this is all just proof of concept scrapbooking right now. Once we have an agreed
set of features, those will get integrated against the trunk.
|
