ok, so then - not wanting to do any 'coding' because you're using html
programmers, not cf programmers, don't you need some amount of cf to
navigate thought the application with fuseactions, xfa's etc? so it is a
'wire frame' in cfm, not htm - with graphics, functionality (simulated),
navigation... and devnotes for the customers input.
je
-----Original Message-----
From: Hal Helms [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 06, 2001 5:44 PM
To: CF-Talk
Subject: RE: hal's wireframe
That's right. The wireframe's purpose is just to get us to the point where
we can do a prototype. Once we're into the prototype phase, the wireframe
isn't used anymore. BTW, if anyone wants the wireframe code, you can get it
at www.halhelms.com.
Hal Helms
== See ColdFusionTraining.com for info on "Best Practices with ColdFusion &
Fusebox" training ==
-----Original Message-----
From: Jason Egan [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 06, 2001 4:00 PM
To: CF-Talk
Subject: hal's wireframe
I've just been looking at Hal's wireframe - this is for development correct?
This isn't intended for use in the actual application right?
je
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
