John, I agree with your incremental approach. I transfer the wireframe logic to a Visio form flow chart. Then we mock up individual Form layouts which are linked to their respective boxes in the flow diagram. As we add more forms they are linked to the flow diagram as well as to each other. Visio can generate the HTML with all the form links and serve as the complete prototype with out writting any code or native HTML.
----- Original Message ----- From: "John Jonathan Kopanas" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, May 24, 2002 4:59 PM Subject: Re: my issues with wireframe tools I have seen > It did but I just see it differently then everyone else. Everyone sees > everything sequentially and I see prototyping having different views done in > parallel and then merged when the two views are authorized. The two views > are graphics and what I guess I will refer to as wireframe on steroids. > > > 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! > > ==^================================================================ 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 ==^================================================================
