Any your beta will be ready next week........ I have been playing with ADALON a lot recently. It is nice in helping to gather requirements and present a bare-bones project program flow diagram with a basic generated directory and CFM forms creation. However ADALON does not go far enough. You have to spend too much time buried in a lot of small data collection forms entering obscure links. It should be more visual.
Keep me informed about your progress. Wally Randall ----- Original Message ----- From: "Jason Paul McCartan" <[EMAIL PROTECTED]> To: "Fusebox" <[EMAIL PROTECTED]> Sent: Friday, March 29, 2002 4:11 PM Subject: RE: Fusebox-list V1 #44 > Andrew > > > I don't know if you have been on this list for a while, but > > over at topica there was a list created sometime last year related > > to visualfusebox. I never did hear again from the person who was posting > > but I tested the app he was building (for some reason I think his name was > > Dov Katz, maybe I am totally off). Anyway, I would like to help out, just > > not sure where to start. I may be able to dig up the archives that had a > > list of some requirements. > > I've lurked for a while but only now just had the time to actually start > being more involved. I teach IT as a freelance instructor and I'm starting > to teach Fusebox as well as develop commercial courseware for it. This tool > is a natural extension of both of those and as something that will make my > own and hopefully other developers' lives much easier. > > The first place to start is what I call the "Wouldn't it be cool ...?" > stage. Simply think of all the things you'd love a tool to be able to do to > allow you to build Fusebox applications quickly and efficiently. Something > that is visual and allows you to design the structure and architecture of > the application and that will generate the build of the interaction code and > files for you. You can then add in the content that gets displayed. What > else would you like to see? > > Some things that I am considering adding include: > > * visual sql builder that's part of the QueryFuse that operates during > design > * some testing features to check that fuses operate as they should > * export modules so that it can be extended to include Perl, Python, JSP and > any other language in the future > * an internal scripting language (eventually) that allows you to write > simple code that is translated to CF, ASP or PHP at export. > * Projects stored in CVS or a database system to allow for networked > interaction amongst developers > * Content and asset management tool that integrates with the desktop > developer version of the tool > * Sandbox security on a per-application or per-module basis > * Versioning and auditing tools so that complete "editions" of a site can be > stored as a snapshot and exported as required. > * In-built FTP/file functions so that once your code is exported it can be > moved onto the correct server. > > I'm probably going to set up a development mailing list for the tool once > I've got the requirements and features fully worked out. > > ______________________________________________________________________ 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
