**************************** Peon King ****************************
Hal introduced some absolutely brilliant ideas that go beyond just
programming syntax and introduced a handful of ways to deal with better
overall application management. Extended Fusebox helps Fusebox solve the
dilemma of managing a LARGE development team.
Extended Fusebox introduces:
1) Fusedocs - A standard method of documenting each fuse, describes in
plain english what the fuse does and the variables that will be passed
into and out of the fuse.
2) Test Harnesses - a way to do unit testing on each fuse, works
directly with fusedocs. This simply means that before the fuse can be
added into the Fusebox it needs to properly deal with a small group of
variables
3) Wireframes - Commonly when designing an application we use
prototypes. Although prototypes make the client focus on how the
application looks instead of what it does. Wireframes helps us to create
a business logic prototype before we do a visual prototype
4) Dev Notes - After you have determined the business logic through
wireframes it is time to build the visual prototype. Dev notes are a way
to make notes on each of the pages in the prototype. I've actually found
them useful on live sites too for future additions to the application
5) Query Sims - A technique to separate the fuse from the database. You
don't need to know anything about the database structure to build dsp
and act fuses. You simply need to know the variables being passed in.
The problem is that often the variable being passed in is generated from
an SQL query. Well we don't want to wait for the DBA to finish designing
the database before our CF developers start working on the dsp and act
files. Query Sims allow us to simulate a recordset coming from the
database.
6) Nested Fuseboxes - This is a technical issue that has been pretty
hard for people to grasp it's power, it took me a long time too. The
thing that it solved for me is the issue of links, forms and cflocations
within a fuse. If I have a fuse that gets called in multiple circuits
(directories) I need some way to make sure the link still works. With
nested fuseboxes ALL links, forms, and cflocations point to "index.cfm"
not ../index.cfm or /directory/directory/index.cfm, just plain old
"index.cfm". That way regardless of which directory the link came from
it will still work.
7) XFA - Another confusing but VERY powerful technical idea. XFA stands
for eXit FuseAction. An exit fuseaction allows the fuse to be separated
from the application. Basically it allows you to dynamically change the
fuseaction of a link or form or cflocation. This allows a fuse to be
used multiple times having the links, forms and cflocations go to
different pages depending on what you want it to do.
Steve Nelson
Peon King
Nathan Stanford wrote:
>
> Opps typing to fast FuseBox and Extended FuseBox or is there no such thing?
>
> What is the difference between FuseBox and Extended FuseBox?
>
> Nathan Stanford
> Senior Programmer/Analyst
> [EMAIL PROTECTED]
>
> > -----Original Message-----
> > From: Nathan Stanford [SMTP:[EMAIL PROTECTED]]
> > Sent: Tuesday, May 29, 2001 8:54 AM
> > To: Fusebox
> > Subject: What is the difference between FuseBox and Extended FuseDoc?
> >
> > What is the difference between FuseBox and Extended FuseDoc?
> >
> > Nathan Stanford
> > Senior Programmer/Analyst
> > [EMAIL PROTECTED]
> >
> >
> >
> >
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
