Well yes, it's pretty slick and schmick. I'm not sure what you mean by "what information can be passed into it?". There's basically nothing that you can put into the wireframe except for a description of each page-state, and a set of exit-destination pairs for each page-state.

The whole idea is to constrain the user into concentrating on a barebones description of the apps logic and interface flow, without encouraging or even permitting anything else to be defined. Many suggestions have been made about expanding the data-model to allow definitions of the FuseBox structure (a la FuseDocs) etc, but Hal has resisted (and I agree), in an effort to keep the wireframe concept tightly focused on requirements gathering.

If you want something with similar, but much broader, the Wiki concept is pretty spick as well. Have a look at http://www.meta-magic.com/cgi-bin/fusewiki?FusePhilosophy or check out http://www.wikiweb.com for a good free wiki-farm.

Was that any help, or have I completely misunderstood your question?

Thanks anyway for the interest, Lee Bjork Borkman

>From: "Nick Massaro" <NMASSARO@co.jefferson.co.us> >Date: Fri, 04 May 2001 13:53:56 -0600 > >This is a very slick tool. What information can be passed into wireframes? > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm

Archives: http://www.mail-archive.com/fusebox@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists