Hi, Is my notion of a wireframe somewhat different to what the general community understands?
I use "wireframes" for development planning. To understand the ins and outs of an application's behaviour, as opposed to a one- or two-liner for each screen. As an example lets say I have: ----- >8 snip ----- Page Title: Check In Page Entry: When checking in an entry, a user can: * Optionally change the stage of the entry (default is from the previous version) * Optionally change the deadline for the stage (default is from the previous version) * Optionally select to flag the entry (default is from the previous version) * Opt not to select a stage or to flag (default is from the previous version) * Notes: Deadline or stage can't be changed without checking a document in. Also any user with editing rights (not just the author) can change the stage or the deadline. ----- >8 snip ----- If this kind of information is not laid out in a wireframe, where is it / should it be laid out? Should it be in the fusedocs? I don't think so, as this is still planning - understanding the issues involved, e.g. "I cant do this, before I do that". Cheers, Steve ==^================================================================ 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 ==^================================================================
