I saw Hal's presentation at CF_South this weekend. From my understanding the
wireframes is used to create a
"wireframe" of the website/application you are creating from the notes you take during
the client meetings. Then
once you have the "wireframe" done and the client understands the flow of the site/app
you can begin proto typing
the app in HTML with all the controls. Then using his DevNotes stuff have the user
give feedback on the
prototype. Once the client is sick of looking at the prototype you can freeze it and
being coding CF. Then
deliver the CF app. It should match the prototype exactly but now it will have full
functionality. And the
client knew all a long what they were getting. So they cant bitch they don't like it
or want changes without
paying for them.
Later,
Troy Sorzano
In article <[EMAIL PROTECTED]>, Jason Egan wrote:
> Date: Tue, 06 Feb 2001 13:59:42 -0700
> From: "Jason Egan" <[EMAIL PROTECTED]>
> Subject: hal's wireframe
> Reply-To: [EMAIL PROTECTED]
> To: CF-Talk <[EMAIL PROTECTED]>
>
> 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
