Re: New WireFrame Beta with easy GUI editing

[Lee Borkman]

Hi Andy, "Menu" items are my own little addition to the wireframe concept.  You may choose to use them or not, of course. In simplest terms, Menu exits are the kind that you want displayed in global navigation, instead of in the page-specific navigation. But there is a real conceptual difference between "normal" exits and "menu" exits.  Normal exits are those which are involved in the flow of a particular task, scenario, use case, etc.  For example, in an issues tracker application, a user may want to "find a particular issue, and then update its status".  There is certain trail of exits that the user will need to follow to accomplish this.  All of these exits should be available as "normal" exits.  They are part of the central flow of the application. But then there are exits that break you out of the scenario you are currently performing.  In the example above, let's say I have searched for, and found, my particular issue; I have even brought up the form for updating the issue, but then I get a phone call from my boss, asking me for the status of an entirely different issue.  So I want to bust out of my issue-updating scenario, and jump straight into a different scenario.  My application therefore needs some "emergency" scenario-shifting links to allow the user to get around in a discontinuos fashion. Hmm..  not the best explanation, but I hope that makes some sense. More soon on your other comments, gotta go make brekky. Thanks heaps, LeeBB ----- Original Message ----- From: Andy   Looks good Lee ... hope to see it integrated with the devnotes version of wireframes on SourceForge soon :-).  Supplementary question ... Can anyone explain to me the difference between  a menu and "non-menu" XFA in Wireframes. It seems that the menu XFAs are left out at the "generate code" step. However I've got to say that when I did some code generation (home-grown tool, using data from wireframe tool and spreadsheet) I found it useful to generate XFAs based on the menu items too, it helped a lot in getting a skeleton app up and running. On my home-grown generator ... although it's in a fairly ragged state at the moment (true fb3 app though), I did manage to generate, almost completely automatically, a skeleton website that could be clicked through as easily as the wireframe. What's more all my fusefiles were created complete with fusedocs (responsiblities section only) just ready and waiting for code to be added to create a working site. I could create the fusefiles because my (manually created) spreadsheet contained the breakdown from fuseaction to fusefile. The only stuff my generator doesn't address at the moment is the directory structure of the final app. However since it's all strict FB3 I was able to create the directory structure then map that in the circuits template to get it all working. That and a tiny bit of tinkering with FBX_layouts was all I needed to get my click-through site. If anyone's interested in this, let me know. I will be going back to work on it later anyway for my own benefit, but if it sounds good to anyone else, it may prompt me to get back to it sooner. Cheers,    Andy. On 27 Apr 02, at 3:56, [EMAIL PROTECTED] wrote: To:             [EMAIL PROTECTED] From:           [EMAIL PROTECTED] Subject:        Digest for [EMAIL PROTECTED], issue 722 Date sent:      Sat, 27 Apr 2002 03:56:46 -0700 > -- Topica Digest -- > > Date: Sat, 27 Apr 2002 10:53:51 +1000 > From: "Lee Borkman" <[EMAIL PROTECTED]> > Subject: New WireFrame Beta with easy GUI editing > > > Hi all, > > About a year ago, Brian Shearer and Patrick McE came up with some > excellent ideas for making the WireFrameTool easier to use. > > I have finally got around to implementing the most important improvement - > providing a GUI for editing PageStates.  The interface now features > drop-down lists of available Pages, so you can choose you Destinations > without worrying about typos, etc.  Often I have found that trying to > impress a client by quickly wireframing an idea results in a lot of > cut-and-paste, adn a whole lot of fiddling to fix broken "links", etc. > Hopefully that will be a thing of the past soon. > > Anyway, it's still pretty rough, but quite useable. > > Please have a look here: > http://bjork.net/wireframegui/index.cfm > > Let me know what you think. > > Thanks heaps, > LeeBB > ==^================================================================ 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 ==^================================================================