RE: Wireframes and Nested Fuseboxes

[BORKMAN Lee]

Title: Message

Hi Jerzy,   The WireFrameTool has no concept of Fuseboxes or nesting, or any other architectural issue, and neither should you when you are wireframing.  To get the most out of wireframing, just concentrate on documenting all of the application's pages and all of the paths that connect them.  Put all thought of architecture, of circuits and fuseactions out of your head.  In fact, put all thought of Fusebox out of your head ;-)  All you are doing with a wireframe is documenting pages and paths.  Pages and Paths.   When you are finished doing the wireframing, AND the static prototyping, then and only then should you begin to think about Fusebox, Nested circuit, layouts, fuseactions, etc.  In fact, at that point, you might decide to build the application using CFOBJECTS, or Perl/CGI, etc.   Hope that helps, though I bet it doesn't ;-)   LeeBB -----Original Message----- From: Jerzy Kalat [mailto:[EMAIL PROTECTED]] Hello,   When I am using wireframes editor, can I somehow pass information of nested fuseboxes? Or should I use this tool for functional specification for each fusebox and later integrate them myself?     ==^================================================================ This email was sent to: archive@jab.org 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 ==^================================================================ IMPORTANT NOTICE: This e-mail and any attachment to it is intended only to be read or used by the named addressee. It is confidential and may contain legally privileged information. No confidentiality or privilege is waived or lost by any mistaken transmission to you. If you receive this e-mail in error, please immediately delete it from your system and notify the sender. You must not disclose, copy or use any part of this e-mail if you are not the intended recipient. The RTA is not responsible for any unauthorised alterations to this e-mail or attachment to it.