> The only issue for me was cost of a nice XML editor and requiring
> the use of ONE more program to get your job done. It is a hassle
> to separate the generation of fusedocs and their subsequent
> maintenance. In that if you generate all your fuse stubs based on
> your xml fusedocs, updating the xml version becomes an issue if
> you want them to reflect the same information, you would need
> another process to synchronize them.
Don't forget that you can SCRIPT Studio's VTOM. So it should be possible
to create a wizard for editing XML FuseDocs right within CFStudio - much
like my FuseDoc attributes appending wizard. Currently my wizard parses
the FuseDoc after Hal's FuseDoc EBNF definition, but parsing XML FuseDocs
is also possible using VBScript and MSXML Parser (which comes with IE and
is already installed on almost every system anyway). It should be also
possible to create a conversion wizard that converts from current FuseDoc
format to XML format and vice-versa.
So what do you people think? What are the big benefits of using XML based
FuseDocs and are they worth it to start building such a wizard?
> I can send you the schema I created if you'd like.
Please send it to [EMAIL PROTECTED] or even better, post it to FuseWiki.
-erki
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
