Common Steve - not everyone uses c:\inetpub\wwwroot - alotta places don't. Just query the IIS metabase (for IIS of course) to determine each web's true root. :-)
--- Billy Cravens -----Original Message----- From: Steve Nelson [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 03, 2002 12:45 PM To: [EMAIL PROTECTED] Subject: Re: Fusedoc Parsers I've got one that rocks the horse as Mr Cox would say. It's still ultra super duper buggy which is why i haven't released it yet. This tool I wrote takes the top level directory path i.e. c:\inetpub\wwwroot It then, reads through every directory and reads in each fbx_settings.cfm and the appropriate fbx_switch.cfm It extracts all included fuses and reads their fusedocs using cfdev's <cfx_xmlparser>. Next it compares all of the <out> variables with the <in> variables of the current fuse. In the end it gives you a report of all the fuses in your entire application that are expecting variables that were never passed out of another fuse. This is incredibly helpful in validating your fusedocs. It's no use if a fuse passes a test harness but does the wrong thing. Jeff Peters is working on another fusedoc tool. He is making an automatic test harness tool. That will read your fusedocs and create instant test cases. This is just the beginning, there will be many many tools that work from the xml fusedocs it's just going to take some time and a tremendous amount of creativity. You also have to remember the tools aren't the important part, the real power of fusedocs is the ability to break your application into tiny atomic pieces and write the code for each atomic piece without knowing the rest of the application. Steve Nelson "Gallant, Ron" wrote: > I think it is a valid question. If I where on the outside looking in I > would wonder why we bothered to have XML based DOCS if we had no tools to > take advantage of it. And I an sure in time there will be many great tools > that com out of it. > > Michael: I don't know if anyone has anything as of yet. I do hear that topic > come up here often. This group works fast, check back in a few weeks an > they may have something. FB if a working work in progress. > > -----Original Message----- > From: Shane Johnson [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, April 03, 2002 12:59 PM > To: [EMAIL PROTECTED] > Subject: RE: Fusedoc Parsers > > Well you could try writing it yourself, I don't remember seeing an > advertisement that said we had any such tool. > > -Shane :) > > -----Original Message----- > From: Michael Paris [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, April 03, 2002 9:48 AM > To: [EMAIL PROTECTED] > Subject: Fusedoc Parsers > > Hello all. > > I'm a software engineer working at a small .com - we are currently > redesigning the system using Fusebox 3.0; of course, we're new to > fusebox! > > My question is: Where are the fusedoc parsers/documentation generators? > > > For eg., javadoc takes all comments and creates HTML pages that index > and display the comments and API. > > The only thing close to this for fusedoc is at bjork.net. However, his > program only recognizes the old fusedoc version and not the latest XML > fusedoc (Fusedoc 2.0). > > So, where do I find a fusedoc parser that takes inline fusedoc XML tags > and generates pretty, formatted documentation in HTML? > > Thanks for your help. > > Regards, > > Michael > > > Blue Cross Blue Shield of Florida, Inc., and its subsidiary and > affiliate companies are not responsible for errors or omissions in this e-mail message. Any personal comments made in this e-mail do not reflect the views of Blue Cross Blue Shield of Florida, Inc. > ==^================================================================ This email was sent to: [email protected] 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 ==^================================================================
