Sorting out QSF import and export

[Josh Sled]

David Goodenough <david.goodenough at linkchoose.co.uk> writes:
> So the question is, which way to go.  Should I simply work on the old QSF
> code and get it to work, and then add selection to it and matching, or should
> I look at the new framework and rewrite the QSF code to work there?

QSF is a bad idea.  Please don't propagate it.

Domain-specific import/export formats and import/export logic are going
to be far easier to implement, debug and use.

Hopefully, you can find something to leverage in the existing (generic,
not QIF-specific) importer/exporter, but for things like Customers and
Vendors where there's not an src/engine/Account to match against, I'm
not sure if the existing code will be trivially adaptable; those Vendors
and Customers are different data-sources for matching purposes.

Note that I'm speaking at a high-level, I'd be happy if you found the
code was more sophisticated than I'm thinking.

-- 
...jsled
http://asynchronous.org/ - a=jsled; b=asynchronous.org; echo ${a}@${b}
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.gnucash.org/pipermail/gnucash-devel/attachments/20090609/1dbf58b5/attachment.bin>