Hi Douglas, All of the scripting has been done using MindManager's VB API. ColdFusion is not involved yet ;-)
There are all kinds of use for the Map, for the XML, and for a way of translating from one to the other. As ever with XML, though, it's just a way of formally structuring data - it's up to all those tool-developers out there to think of more ways to *use* the data. What can you do with the map? * Do 80% of the architecting in a rapid GUI environment, with drag-and-drop, with arrows to reference single-source chucks of specification, etc. Show your friends - collapse it, expand it, drill down. Export it as a PowerPoint presentation so you can walk your tean through it; export it as a Word doc so you can attach it to your corporate documents. What can you do with the XML? * Keep it by your side. Open it in IE and you have a collapsible, precise, view of the entire application's architecture. Feed it into a Fusebox-generator and spit out a complete set of directories, core files, fuses, already substantially Fusedoc-ed. Do what you always do with XML - "repurpose it", transform it. You are correct that I am not turning out complete Fusedocs, but have faith - I am heading for a system where I can generate the *complete* Responsibilities and IO block. A more generic Fusebox-generator can add all of the other Fusedoc elements, although some of these will probably always require real-time manual entry. Sorry to foam at the mouth, LeeBB -----Original Message----- From: Douglas Smith [mailto:[EMAIL PROTECTED]] Sent: Thursday, 4 April 2002 2:22 AM Hi Bjork, Looks interesting. I guess you have some CF code that takes some MindManager (MMP) output and generates the XML file? Also, I don't understand the advantage of having an XML file that represents the application architecture in this XML format. What do you do with it? It's not a fusedoc, after all. Maybe I missed the earlier conversation about "MindMap ->XML Fusebox Spec" ... I will read up... At 12:11 AM 4/4/02 +1000, you wrote: > >But, if I use a mapping tool to specify my inputs and outputs, then I >don't need to duplicate the specification for the "job" recordset; I >simply draw an arrow pointing to the existing definition. I just need to >make sure that the XML-generation script handles it transparently. > >Anyways, to cut a long story short, I have that working now. The result >is that the generated XML has all of these references reconciled, but the >MindMap (ie the source) uses arrows instead of duplicating information. 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. ==^================================================================ 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 ==^================================================================
