Further investigation of gnome-pilot shows that it works, but
utilising it raises several problems.
gnome-pilot uses an applet, which, when clicked on, calls several
conduits for each type of data (to-do list, address book, expense
tracker etc.), synchronizing everything at once. This design is quite
elegant from a user's point of view. Their current expense conduit
simply reads data from the expense tracker and exports it as
comma-seperated text.
The simplest way to write an appropriate conduit would be to be able
to call gnucash engine functions directly from it, but as I understand
it that is not currently possible. Somebody on the list previously
suggested making the engine a library, and while I wasn't initially
keen on the idea, how difficult would such a task be? A CORBA
interface to the engine would also do the trick, but that's a
substantial job.
Alternatively, it might be possible to get gnucash to simply parse
the comma-seperated text files. This perhaps isn't quite as neat,
but would do the job.
The final approach would be to ignore gnome-pilot completely and
use pilot-link to talk to the Pilot directly. This means we could
do the parsing from within gnucash, but means that a seperate hotsync
operation has to be performed.
Opinions, anyone?
--
---------------------------------------------------------------------------
Robert Merkel [EMAIL PROTECTED]
What a strange game. The only winning move is not to play.
-- WOP, "War Games"
---------------------------------------------------------------------------
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
