Great... that sounds solid to me. You can use structure to accomplish the same thing. You can create a data structure out of the wddx file stored on disk and treat it just like a data store. If you would like help on this, just email me at [EMAIL PROTECTED]
Keep Up the good work. John >>> [EMAIL PROTECTED] 03/27/02 03:23PM >>> Gotcha. That's what my new editing interface does. It separates each element into its own form field. There are a few things that are making this a challenge, mainly since the data storage uses a text file/WDDX file. I was really contemplating putting all of this into an access db. It would simplify a lot of the issues that I have been facing as of late. What would be the con's to moving all of this data back into an access db? With a data export function, you could export the entire wireframe in a WDDX file so it could be easily imported into another wireframetool. An importer could be written to import current .wir files into the new version. Just thinking about it, I think we could add a ton of new functionality using a db as the storage solution. Any thoughts?? ==^================================================================ 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 ==^================================================================
