I like your idea. One thing I found out about Fusedoc was that creating a
flexible standard that could be added to without breaking was much better
than trying to anticipate and integrate everyone's needs. I think what
you've outlined works fine for a standard. I'll try to come up with a B-N
format to describe a wireframe.
Hal Helms
== See ColdFusionTraining.com for info on "Best Practices with ColdFusion &
Fusebox" training ==
-----Original Message-----
From: DRE [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 16, 2001 10:12 AM
To: Fusebox
Subject: Re: WireFrame Demo Online
Hi Gang,
I'm noticing a lot of comments/worries about having multiple versions of
wireframes. I'll be the first to say that I modified it instantly when I
downloaded it which I think is inevitable. Programmers will inevitably
modify.
The reason I write however, is to suggest that instead of standardizing the
whole thing, we instead create a standard for the source text file. That
way, no matter what you've done to modify the wireframes program, you can
still share the source file and have it work perfectly be it in Hals
version where it converts to a database or the Lee Borkman version where it
goes straight to the browser.
This email wouldn't be complete without a first try at a standard so here
goes.
To summarize what I downloaded from Hal's website.
Description start here.
Each fuse starts with a name which is encased in square brackets. This is
its identifier.
The second line of each fuse has the text "responsibilities:" followed by
more text outlining the responsibility. All on one line.
The following lines consist of ways to get out of the current
fuse. Starting with the name of the way out, then an equals sign then the
name of the fuse identifier to go to.
Description ends here.
Thats it. Very simple. Very Clean. I like it. We fix this in stone. . .
but
I propose one addition.
I agree with Hal that I want a navigation piece that is constantly
somewhere on the wireframe.
Lets agree that if the first fuse defined is called navigation. Then we
include it at the top of every page with the ways out of the fuse listed
below. The navigation piece is the same as all the other fuses in that it
has links to other fuses.
This way, if youre looking at an older .wir, there is no initial navigation
fuse, nothing gets placed at the top of each file, it still works. If
youre using an older wireframe app that doesnt support my navigation
feature but youre looking at a .wir file with the new navigation fuse,
theres one extra fuse that is never called called navigation so it still
works fine.
I'll appologize in advance if I've stepped on anybody's feet.
DRE
At 04:51 PM 2/16/2001 +1100, you wrote:
>Hi all,
>
>I've been doing a bit of work with Hal's very useful WireFrames utility.
>I've put up a working demo at http://bjork.net/wireframe/index.htm, so you
>can all see and comment. It's got a few new twists, but the main
difference
>is that there is no database required at the back-end.
>
>I look forward to your feedback,
>
>Thanks,
>Lee (Bjork) Borkman
>http://bjork.net ColdFusion Tags by Bjork
>
>
>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.
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
