I'd strongly recommend against an Access file.  Wasn't that the point of
the new wireframes tool (Hal's tool used an Access db).  I like being
able to send someone a .wir file that they can drop in a be ready to go.
If you did want to use an Access database, I'd recommend a different
table for each wireframe.  This way, a user could export a single table
into an .mdb, and you could have an import facility in the wireframe
tool to avoid the problem that Steve mentioned.

---
Billy Cravens


-----Original Message-----
From: Russ Johnson [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, March 27, 2002 2:24 PM
To: [EMAIL PROTECTED]
Subject: RE: New WireFrame alpha with DevNotes integration

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
==^================================================================

Reply via email to