RE: [Pythoncard-users] CSV for PythonCard

[Kevin A. <al...@se...>]

> > This issue came up because of the addresses and dbBrowser samples. A CSV
> > module would allow simple import/export for any PythonCard app. It isn't
> > critical right now, so anyone that wants to can pursue it and
> just add the
> > module to cvs when it is ready and notify the list. I'm not actively
> > pursuing it myself except via email.
>
> Why not use XML? It's much more powerful, and there's _lots_ of support
> for it in the standard libraries... You can even use the xmlrpclib for
> simple serialisation:

The whole point of CSV is to deal with other programs that don't support
some better format. I think the initial idea was to import Outlook Express
or Netscape contacts, which meant CSV. XML doesn't help you there.

Tab separated or some other formats are okay as are fixed field formats as
long as you don't have multiline data (typically the Notes field), it just
depends on what is on the other end. Obviously, if you have some newer
program on the other end that can talk XML that is probably the way to go.

I don't even mind switching to XML for the resource format for PythonCard,
but only after I know I'll never have to hand edit the files and that
whatever generating them always outputs valid XML, so we won't have
validation problems. If you ever have to look at XML, then something is
wrong with your solution :)

ka