@arroncupid: The process becomes - sketching and discussing ideas,
refine, and then build the greyscale wireframes in the XHTML.
Brilliant, this is exactly where I'm headed. My current method is
sketch then prototype w Fireworks, soon it'll be sketch then build
in XHTML. Thanks.
@ Richard
On Nov 12, 2009, at 8:09 AM, Andy Howard wrote:
And Todd - your prototyping book looks very cool. Will be buying it.
Thanks, Andy. BTW, if you use http://bit.ly/19Hiir Discount code PRPUBNOT you
can get 15% the purchase price.
Cheers!
Todd Zaki Warfel
Principal Designer
Messagefirst |
On Nov 12, 2009, at 9:43 AM, Richard Rutter wrote:
We avoid using CSS frameworks in production, but if they speed up wireframing
that'sa good thing.
So, do you recode everything then? Or do you strike some balance between some
of the framework stuff and a more optimized version for
Has anyone used a fluid 960 grid framework for rapid prototyping?e.g.
http://www.designinfluences.com/fluid960gs/
I'm particularly interested in how usable it is for a UX person like
me with *some* (i.e. junior level) CSS/XHTML knowledge. I've had a
quick play with it, but wondering how practical
What about an easy and quick CSS/XHTML rapid prototyping with any
CSS/XHTML knowledge?
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=47347
Hi Andy,
I found it a practical way to skip the mock-up stage, not the
wireframe stage. Indeed, as doing mock-ups i.e: using Photoshop tends
to produce unrealistic screens (i.e: typography with photoshop is
always better/different than typography on the browser).
However, I would say it requires
On Nov 12, 2009, at 3:07 AM, Nicolas Leroy wrote:
I found it a practical way to skip the mock-up stage, not the wireframe stage.
Couldn't you just wireframe in HTML?
Cheers!
Todd Zaki Warfel
Principal Designer
Messagefirst | Designing Information. Beautifully.
On Nov 12, 2009, at 2:37 AM, Andy Howard wrote:
Has anyone used a fluid 960 grid framework for rapid prototyping?e.g.
http://www.designinfluences.com/fluid960gs/
I'm particularly interested in how usable it is for a UX person like me with
*some* (i.e. junior level) CSS/XHTML knowledge.
Any wireframes we don't do with pen and paper end up being done in
HTML. To speed things up we use our own CSS framework for layout, but
I would say there's nothing too much wrong with using one of the
popular frameworks for HTML wireframing/prototyping.
We avoid using CSS frameworks in
My experience is that building wireframes in applications such as
Axure or Visio are wasted effort. They quickly become a maintenance
overhead.
I have put effort into creating a prototype framework using Polypage,
JQuery and 960grid. Over time I'm building up a library of greyscale
XHTML
I've used the 'Blueprint' framework extensively on various
projects. It's a great starting point to develop quick prototypes.
For the final production pages I always use a highly custiomised
version but it still uses many of the underlying principles such as
the css reset, typographic hierarchy
Great input everyone, much appreciated.
Todd's overview seems spot on to me - a good summary of the
frameworks available, their practical uses and the suitability of
code for production. Very handy, definitely answers my question.
And Todd - your prototyping book looks very cool. Will be buying
12 matches
Mail list logo
