Robert Graham Merkel <[EMAIL PROTECTED]> writes:
> OK, I tried one of the example apps included with pilot-link, and it
> managed to read the expenses from my Palm IIIx without difficulty.
Great.
> From here, I'll try to hack it into gnucash, using dlopen() and co.
> to make sure it is only enabled if pilot-link is installed.
Another option we could consider, though it may not be worth it, would
be to structure things with a small stand alone app that handles
pilot-link and communicates via it's stdin/stdout to gnucash.
Basically the app could be a small guile program that's linked to
pilot link and can send and receive scheme-form commands on it's
standard input/output. Then gnucash could fire it up whenever it
needed to talk to the pilot. Since you could just use the scheme
reader/writer on both sides for the communications, parsing would be
trivial.
The communications might look like this:
gnucash -> (connect-to-pilot "/dev/ttyS0")
helper <- (result 'ok)
gnucash -> (get-expenses-info)
helper <- (expenses-info ...)
etc.
This would have several advantages, including not having to muck with
dynamic libs right now, and keeping the pilot libs outside the main
app which *might* make things more stable. If the helper crashes, no
big deal. It would also make it easy for people to write up other
little guile scripts to hack around with their pilot's data.
Just a thought...
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
