The main point for moving it away from access is for working in a team, and simply moving the devnotes around. By keeping this in a wddx file, all you have to do to move it from one cf dev server to another is zip up devnotes app and paste it in the new location. Everything remains in tact. If it is in a database, you lose this portability.
On the current project I'm working on, my prototype and devnotes gets moved between two servers. 1) my dev server which is constantly on the net 2) my laptop server which allows me to demonstrate the app to my client when connecting to the net is not possible. The real problem i found with the database is I would often needed to still copy between laptop and dev server, but I would occasionally get the two databases out of sync when working on multiple applications. i.e. application 1 would have the latest data on the dev server, whereas application 2 would have the latest version on the laptop. So to properly get them sync'd back up, i needed to actually go into the database and move specific records from one to the other. With a wddx datafile, each application essentially has it's own datasource, so this problem doesn't occur. All of this said, i'd suggest playing more with the wddx file. What problems are you running into with the wddx file that you can't figure out? Steve Nelson Russ Johnson wrote: > 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?? > > -----Original Message----- > From: John Farrar [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, March 27, 2002 1:57 PM > To: [EMAIL PROTECTED] > Subject: RE: New WireFrame alpha with DevNotes integration > > Russ, > > Separation refers to it requires extra effort to manage xfa's, menu's, > description, and titles all in one text box. I thought we could use more > than one box to manage these. It only makes sense to increase integrity and > simplify entry. > > John > > >>> [EMAIL PROTECTED] 02/24/02 12:17PM >>> > John, > > Funny you should mention some of these things! I have been working on a > WDDX storage solution for wireframes for about the last 4 days. This of > course is going hand in hand with a new editing interface. > > Also, versioning of your prototypes should be added by the end of the > weekend. Currently if you regenerate a prototype, it just overwrites the > existing one. I have the versioning functionality coded, I just need to > integrate it into the application. > > I ask for clarification on your third point. When you mention to > separate these things, are you referring to the interface itself? > > BTW, please go to the project page on sourceforge > (http://sourceforge.net/projects/wireframetool) and add any feature > requests you may have into the Feature Requests Tracker. This will give > us a good source to work from. > > Thanks, > Russ > > John Farrar wrote: > > The prototype concept is way cool! I was thinking... it would be cool if > > we could have a full fusebox 3 application skeleton that we installed on > > a server. We did the wireframe right where we were building the test > > site/application and gave the client instant access. (With some of Hal's > > security to control what the client could do.) This could interface with > > cool tools like SQLGen by Aloha-WebDesign and be the start of a new > > level of cool for creation of applications. > > > > Version 5 wish list... > > * XML or WDDX wireframe storage format. > > * Flash MX edit interface... could create more dynamic edits > > .. * separate xfa's, menus, title and description > > * Import engine for current wireframe format conversion. > > > > If I took the time to build this direction... would anyone else be > > interested in beta testing this type of wireframe manager. (Following > > the wireframe is not for look and feel ideals, before anyone get's > > confused.) > > > > John > > > > > > > ==^================================================================ 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 ==^================================================================
