That's excellent, Emilio! Would you shoot me a copy of your revisions to the
wireframe/devnotes thing? I've got a class coming up in a week or so and I'd
love to give them the latest and greatest. Also, I'll put it up on my site,
if you don't mind, for others interested.
Hal Helms
== See www.ColdFusionTraining.com for info on "Best Practices with
ColdFusion & Fusebox" training, Jan 22-25 ==
-----Original Message-----
From: Emilio [mailto:[EMAIL PROTECTED]]
Sent: Saturday, January 13, 2001 1:35 PM
To: Fusebox
Subject: Fusebox testimonial
With all the "argument's" against fusebox over the last while I thought it
would be nice to provide a positive example of how well it works.
Basically, our company is swamped with work and we have more projects than
programmers right now. In order to get a project started and out the door
on time we had to horn swoggle one of our db guys. We had about an hour
long meeting on the project followed by another 2 hours of "this is what
fusebox is and how it works".
The next day the db guy was already coding the basic fuses though this was
without any design. I'd say fusebox has allowed us to create a basic
structure which can be used over and over and teach it just as easily.
Fusebox is saving our asses and management is none the wiser ;-P.
The best part is that he can go through the proposal and start all the
sprocs, qry_files, and act_files as none of these require any design
component. We would have used query sims but we already know all the data
requirements as we get to dictate any system data and the rest is defined by
a standards org!!
On a final note, I started using Hal's devnotes/wireframe method for
spec'ing out a project and I can't provide enough positive comments about
the technique. It took about 3 days to get the wireframe done ( as the app
is huge ) but once I had all the pages done it was amazing to sit with the
client and talk them through the application without actually having an
application for them. I made some modifications to the app which I thought
would help. Let me know if you agree but you can't go wrong with the
wireframe/devnotes combo...Hal thank you once again.
modifications:
-now a fusebox wireframe: my idea behind making the wireframe fusebox as
well is simply having access to variables provided by app_model. Since we
already have a fusebox skeleton all I had to do was modify the devnotes
pageID to store the fuseaction vs. the page. Since each step in the
wireframe was a page I figured just make them dsp_files and create a simple
index for them.
-on big wireframes the client could potentially add comments or tasks to
50 or 60 pages, I thought it would be hard to know where they were adding
stuff, so now each entry added by the client has the ability to email me the
fuseaction to which they just added to note. so now when I come in on monday
I can quickly view each entry and go to it directly.
Cheers,
Emilio
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
