I've heard three good suggestions on this list before
that I think would really deal with the standarization
issue well, and should make everyone happy.
1) REFERENCE APPLICATION
The best way to learn is by looking at and playing
with code. It would be nice to have one standard
application with 3-4 circuits that perform some
very simple tasks, just to illustrate how fusebox
works. Then everyone could have their own version
of the reference application, with modifications
to show the specifics about how they do things.
We could also have a repository on fusebox.org for
people to upload their versions of the reference
app.
2) DESIGN PATTERNS
Rather than trying to document Fusebox as a whole, why
not just document the various techniques that fall under
the category of Fusebox? That way we can have sort of
an ala carte standardization.
http://www.c2.com/cgi/wiki?DesignPatterns
3) FUSEWIKI
If you're going to have a standard, you need a place
to put it. Fusewiki IHMO already is host to the
evolving standard. It documents most of the design
patterns in fusebox, and because anyone can
modify its content, it will always be an up-to-date,
collaborative effort. If there's an aspect of
fusebox that you can't find documented here, by
all means add it (or if you don't know much about
it, add what you do know or add a message asking
for it).
http://www.meta-magic.com/cgi-bin/fusewiki
Patrick
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
