direct connect and libofx developement
BenoitGrégoire
bock at step.polymtl.ca
Sat Jun 28 14:33:18 CDT 2003
On June 28, 2003 01:07 pm, Josh Miller wrote:
> I don't know about the mac but if you want a list of servers on a windows
> system.. You can install the demo of MS money and dig throu the CAB files,
> they have a complete list of URLS and an application on the MS money
> Developer site that will break down all the specific settings in the config
> files.
You're kidding right? If so, the biggest hurdle to implementing direct
connect support has just been lifted.
BTW, I wan't to apologise to everyone for not being very active on
libofx-devel and in CVs these past few weeks. I'm extremely busy with real
work. However, I DO read everything, and if anyone wan't to jump to active
development, I'll be happy to spend the necessary time to get them up to
speed on the code base and future plans. Here is my updated personal roadmap
for LibOFX. It may not happen in that order, depending on who get's invoved
in active development.
0-Branch the current libofx since the API will change.
1-Proper callback function registration, scrap the current callback model for
data communication with the client, in favor of a query model. Clean up
function names, constant names and data structure to be less tied up to the
OFX data model.
2-Libofx export support and API. This will allow aplications supporting LibOFX
to export their data in a variety of formats, with a single interface. The
first format supported will be QIF, stealing code from ofx2qif. OFX and CSV
support is also planned.
3-Convert the gnucash ofx module to use the new interface and support export
functions (basic features: accounts, transactions and commodity). This will
allow testing of the export architecture.
4-QIF import support.
5-Direct connect suport (bi-directionnal communication with a bank's OFX
server). This will be a lot of work, and I will need help, since my bank does
not support direct connect, so I will not be able to test it easily.
1 and 2 are essential for LibOFX to move forward. Ideas for the new API
should be discussed as soon as possible. 3, 4, and 5 can happen
simultaneously.
As always, you can find me on #gnucash on irc.gnome.net
--
Benoit Grégoire
http://step.polymtl.ca/~bock/
More information about the gnucash-devel
mailing list