Memengo™ Community and Support

That's a good topic.

We've spent some time trying to figure out how should the CSV look like, given that each card has different set of fileds. There does not seem to be a good way to do this. the best I could come up with is this ("sparse mapping"):

Or this ("tagged mapping"):

Neither one looks good to me. How about you? Would you be happy with either one of these, do you have better ideas?

I don't think many of our users will know how to write scripts… this is what you suggest, right?

I'm nt sure I understand your second idea (About user renaming things). Can you provide an example?

How many people would know what to do with an Access database? We trying to make features appealing to most of our users, and so far the best we could come up with was the "Print" button.

Or design philosophy is that you should have three copies of data:

1. iPhone copy for everyday access when you're out and about.
2. Web Site access for convenient editing, and also for when the iPhone is not with you. Imagine gong on vacation and your iPhone being stolen? Web Site to the rescue!
3. A printed copy in the fire safe or a deposit box.

The first two should cover you in all of life's everyday situations. The last one is there in case of an unlikely event such our software getting irreparably broken, our compnay going out of business or your house burning down with the iPhone inside.

I can't imagine a situation that is not covered by these three copies of data.

The only thing that is missing here is ability to casually migrate to another software - you can still do it by re-typing things from the printed copy, but it's not convenient. Alas, for us to do something here would mean to export in a format that another program can import from - otherwise it's back to retyping. There is no single universal export/import format. A CSV file or an Access database are useless unless other programs can read from it.

Well, if you are willign to edit the result by hand, why not copy-paste the data from the "Print" page?

The only people who can take advantage of the structured nature of XML are people who can write their own programs to parse and transform the XML. In all other uses Print format is just as good, no?