Dov,
Sorry, I just 'got' what is happening when I choose the add a fuse link! I
had misunderstood it completely.
My comment should be that the link should say "add a fuseaction and fuses".
It would still be good if there was a way to share fuses beween two
fuseactions. That is the most common way I save time. A query for example is
shared by several actions for list, edit, update (to check it exists), etc.
I can see great use for this application what are your plans for it ? Will
you sell it or give it away ?
I had already started working on somthing similar but this looks better than
mine.
Some of the plans I had which you might like to include are:
1/ A list of the fuses in each fuseaction. Click on a link to launch
CFStudio or XMLSpy to edit the FuseDoc.
2/ Ability to read an existing index.cfm and create a heirarchy. Useful if
you have an app like the one you plan to build but need to restructure it.
(eg new version).
I will try and extract the wireframe reading code later today.
Kevin
-----Original Message-----
From: Kevin Roche [mailto:[EMAIL PROTECTED]]
Sent: 01 August 2001 19:04
To: Fusebox
Subject: RE: Visual Fusebox 1.0
Dov,
1 & 3/ Yes I saw that, but mouseover text for the icon you mention says add
a fuse to an application. There should be a many to many relationship
between fuseaction and fuses.
A fuseaction can have several fuses.
5/ They have a strange file format but code to read it and make a structure
is open source. I will extract it and send it to you.
A new thought....
Fuses are often shared by several fuseactions. Is that possible ?
Kevin
-----Original Message-----
From: Dov Katz [mailto:[EMAIL PROTECTED]]
Sent: 31 July 2001 19:58
To: Fusebox
Subject: RE: Visual Fusebox 1.0
My comments (real quick, because I have to go to a meeting):
1/ when you mouseover all icons, you should see white text appear in a grey
bar at the top of the page, as well as the browser's status bar (make sure
you are using msie , as i suggested)
2/ i will implement this. thx for sugg.
3/ mouse over the icons, one of them (a white document with a mouse and a
star) is for adding fuseactions.... see /1 to be sure
4/ hierarchy is for the most part enforced, javascript alert boxes prevent
you from violating the hierarchy as I define it in the help file
5/never used wireframes. if you know their datafile's syntax and want to
write an import utility, id be happy to integrate it
all the best,
-Dov Katz
---------- Original Message ----------------------------------
From: "Kevin Roche" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Date: Tue, 31 Jul 2001 19:49:12 +0100
>Dov,
>
>Great! I like the idea. Here are some comments after I tried it.
>
>1/ I found the icons a bit confusing as the icon on the top bar is slightly
>different from the one in the created heirarchy.
>
>2/ I could not see a way to move fuses around (change the parent)
>
>3/ I could not see a way to add fuseactions
>
>4/ Can the Heirarchy be enforced ? ie:
>
> Application - Circuit - Fuseaction - Fuse
>
>5/ It would be nice if your tool was able to read files created by
>wireframes and allow me to add this stuff to the heirarchy for editing. I
>need to be able to move any element to below any other of the correct type.
>
>Kevin Roche
>OBJECTIVE INTERNET
>
>-----Original Message-----
>From: Dov Katz [mailto:[EMAIL PROTECTED]]
>Sent: 31 July 2001 15:27
>To: Fusebox
>Subject: Visual Fusebox 1.0
>
>
>I built an app during my spare time last week. I hope you fusebox designers
>find it useful, and newcomers to fusebox: I hope this helps ease the
>transition. Please send me feedback, because we, as a developer community
>can make this a great utility for reasons below (i wrote about it in the
>from the documentation (excerpt below) ,so I'm not going to repeat that
>effort...)...
>
>point your MSIE browser to http://www.msidg.com/visualfusebox and when
>there,click the "Start" button.
>
>Sorry if, you receive this multiple times. I just want to get as much
>feedback as possible, (hence 3 lists) about the app, and the concept. I
>obviously still a long way to go, but it is all functional (read
>documentation).
>
>EXCERPT :
>Introduction
>I created this program as a "quick start" to my own application development
>efforts. Every time I begun programming a new fusebox application, I found
>myself "copying-and-pasting" a bare bones file/directory structure from one
>of my other fusebox apps, instead of creating all of the files from
scratch.
>This program, as I hope you will also see, not only eliminates the
hand-made
>file creation process, but allows more clear planning by providing a visual
>structure throughout the process. It also makes documentation more
plentiful
>and uniform. It is by no means a finished project, and I plan on enhancing
>it as the need arises.
>
> -Dov Katz ( [EMAIL PROTECTED] )
>
>Visual Fusebox (for lack of a better name) is a tool designed to help
>coldfusion programmers plan out their applications. It may also be a great
>way to ease new fuseboxers into the coding styles associated with the
>Fusebox methodology. This utility allows you to design applications in an
>easy-to-use visual interface, and either save the "blueprints" or "compile"
>the blueprints into a file-structure skeleton, which can then be downloaded
>in a zip file. There are 2 advantages I see to this application.
>
>Developers can share "blueprints", improve them, and contribute to a
>centralized library of architectures
>As Fusebox is released for other languages, (ASP,PHP,etc.) the "compile"
>section can easily be augmented to allow compilation into any of the new
>languages, while allowing programmers of the various languages to maintain
a
>common platform for planning the applications, and can share plans
>pre-compilation.
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
