|
My apologies for those of you who now have this message
from both list.
I think this is probably safe for general consumption.
;-)
Thanks,
LeeBB
----- Original Message -----
From: Lee Borkman
Well, I think it's exciting anyway ;-)
Because I'm using a mapping tool that allows
relationships, I can avoid duplicating data definitions by using relationships
in their place.
For example, I have two fuses, qry_job and dsp_job.
Qry_job outputs a recordset called "job". Dsp_job takes a recordset called
"job" as input. Suprisingly enough, these recordsets (and therefore their
definitions/specifications/fusedocs) are identical in structure.
Now, usually, when creating the Fusedocs, I would
copy-and-paste the recordset definition around. But that's obviously a
case of code (or meta-code) duplication, and potentially dangerous, for reasons
we all understand.
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.
If anyone's interested, you can find the Map, the XML, and
an image here:
Thanks everyone,
Sorry for getting carried away,
LeeBB
==^================================================================ 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 ==^================================================================ |
