As a more intelligent response, let me point out one of Our Messiah's (Hal)
main points in wireframing -
"When yonder client be force-ed to look at pictures naught of style and
color, he adopts abilities remarkable of visualizing funtionality of the
utmost purity. Rounding wee buttons and adopting blue in cornflower is to be
expected, but site-flow and justification goals be-est something that can be
pried from a client's cold steel trap of a mind only in the absence of said
aesthetic."
Amen, brother.
NAT
> -----Original Message-----
> From: John Quarto-vonTivadar [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 22, 2001 8:41 AM
> To: Fusebox
> Subject: Re: WireFrame Demo Online
>
>
> > What I'm afraid of is I'll be presenting a wireframe to a client and
> > he'll say, "Can you make that a pop-up window?" or "Can you add a
> > marker that shows which pages are have access restrictions?"
> > Simple little things like that could make the wireframe a much more
> > effective communication tool.
>
> but you can do that with the wireframe, already. You'd simply add a link
> that says something like "after clicking here a popup window will
> appear and
> blah-blah-blah". If you make it actually *do* the popup then you aren't
> wireframing, you're developing. The whole point, I think, is to get
> something in front of the client that mimics the site's work flow and
> business logic. That's the purpose of the wireframe. Anything else is
> development and GUI design, which are handled later.
>
> Fur
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
