John,
What I do, is create a wireframe to get the flow in terms of what
pages call each other and this wireframe is then used as the bottom layer of
my prototype. Once I have the site going through the appropriate pages, I
then add the next layer up which is the fusedocs. This gives me what is
coming into the page, and what is going out to the next page. This is then
used to create the full specs for the site that will be signed off by myself
and the customer before moving forward. Since each individual file has
specific variables it needs to see coming in I code the fusedocs to specify
what that particular page expects to receive, and what it expects to send
forward. This is done on my sites for the display pages and action pages.
I view the query pages as pure sql with a cfquery wrapper and as such do not
need to be fusedoc'd as they primarily are based on the needs of a specific
fuse and are named based on the actual fuse. Once this is complete, I build
the files with the form fields with no database back end in place. This
gives me the UI that I taylor to the customer's needs and make any changes
to fields and carry that back to the fusedocs. Once this is complete, I
have a very basic prototype which I use to sit down with the customer and
make sure we are still on the same page. I can then make any needed changes
to the pages and the database structure and hook that in and get basic add,
change, delete functionality in place and then keep going in logical
iterations until the site is complete. Did this help to explain what I
said? If not, I will gladly try again. Take it easy and have a great
weekend!
Joe
-----Original Message-----
From: John Jonathan Kopanas [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 24, 2002 2:49 PM
To: [EMAIL PROTECTED]
Subject: Re: my issues with wireframe tools I have seen
Fusedocs from what I understand is specific to a file. Wireframe is page
specific. We prototype pages not files. Fusedocs is like creating class
diagrams for OO programs.
I did not understand your last sentence. Can you please rephrase. Thanks.
----- Original Message -----
From: "Hayes, Joseph" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, May 24, 2002 1:26 PM
Subject: RE: my issues with wireframe tools I have seen
> After reading each of these posts, it seems to me that the initial
> post
was
> looking for defining form fields in the wireframe... I wonder if there
> is confusion between wireframing a site to get the initial flow of
> pages, and creating the Fusedocs that describe what goes in and comes
> out of each
page.
> I tend to wireframe a site, then once I have the flow, then go back
> and flush it out with fields for the docs after the fact.
>
> Joe
>
>
>
==^================================================================
This email was sent to: [email protected]
EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9
Or send an email to: [EMAIL PROTECTED]
T O P I C A -- Register now to manage your mail!
http://www.topica.com/partner/tag02/register
==^================================================================
