QIF Importer
Charles Day
cedayiv at gmail.com
Mon Jan 28 21:30:45 EST 2008
On Jan 28, 2008 6:10 PM, Ian Lewis <ianmlewis at gmail.com> wrote:
> Charles,
>
> I've mostly been playing with the generic importer and seeing how that
> could be applied to the QIF importer. Nothing practical really. At least at
> this point. While the generic importer would allow the reuse of dialogs, the
> QIF importer requires a relatively high amount of user interaction. The
> generic importer isn't a druid so this would mean showing lots of popups.
> I'm currently at kind of at a loss for how it would best be done so that it
> wouldn't be a worse user experience than what we currently have and without
> introducing too many bugs. I probably need to have a conversation with you
> and/or Derek about it. I wouldn't wait for me necessarily.
>
> I didn't see this bugs before so if you are averse to looking at the C
> side of things I could take a look at them. I'm familiar enough at this
> point with how the druid works to be able to fix something like these but
> you're probably even more famaliar with C than I am. Are they holding you up
> from making other changes?
>
The C bugs aren't holding me up. I am just stepping away from the Scheme
side for the moment because the next Scheme patches will need to be built on
top of some of those seven patches awaiting review. I think I posted an
eighth patch to the list (rather than Bugzilla) and I don't think that one's
been committed either.
In the meantime, I'm happy to work on druid-qif-import.c if you haven't made
wholesale changes to it already. If you've only made small changes to it
then my changes will probably merge OK with yours. Either one of us could
work on those bugs. I think I've just fixed bug 509089 but I still have to
test it. I'll work on bug 512208 next. If you have time, it would be great
if you could try fixing 512173.
-Charles
Ian
>
> 2008/1/29, Charles Day <cedayiv at gmail.com>:
>
> > On Jan 3, 2008 6:03 PM, Ian Lewis <ianmlewis at gmail.com> wrote:
> >
> > > Charles,
> > >
> > > You mentioned in some other e-mails that you were working on fixing
> > > some problems with the QIF importer. What exactly are you working on? I'm
> > > looking at trying to improve the importer myself and would like to
> > > coordinate any changes in an effective way. That said, I'm new to coding
> > > Gnucash haven't really thought much about the scheme part yet and was more
> > > looking at fixing bugs in the import druid first, but eventually turn to the
> > > import itself with the eventual (and lofty) goal of rewriting the QIF import
> > > to use the generic import code that the OFX and other imports are using.
> > >
> > > Ian
> > >
> >
> >
> > Ian, can I get an update on what you are working on? I've made a whole
> > bunch of changes to the QIF importer .scm files recently. A bunch of the
> > patches have been committed, but there are seven more patches waiting to be
> > reviewed and I think I'll need to wait for them before diving in again. In
> > the meantime there are a few bugs in the druid (509089, 512173, 512208) that
> > should be fairly easy to fix, so I could work on the C code to fix those.
> > Are you actively working on druid-qif-import.c? If so, does your
> > version differ from the latest SVN version much?
> >
> > -Charles
>
>
>
More information about the gnucash-devel
mailing list