ofx and generic import: GUI, callbacks

[Christian Stimming]

-----BEGIN PGP SIGNED MESSAGE-----

On Donnerstag, 21. November 2002 23:42, Benoit Grégoire wrote:
> > As for the GUI for Destination Account matching/choosing, I absolutely
> > have a listview in mind. The listview would have one line per
> > transaction. Each line shows some details for the transaction (date,
> > amount, description, ...) *and* the destination account. 
> >
> > All our discussion about "automatic destination account matching" IMHO
> > is *only* about the suggested default. The user should *always* have the
> > choice to choose some other destination account (and, BTW, this is the
> > only way to learn the automatic matches in the first place).
>
> Ok, that would technically work.  But the user would be presented with the
> exact same list of transactions twice.  This just duplicates work for the
> user.  He would have to first select or double check the auto-selection of
> the destination account (possibly by finding his sales receipt for several
> of the transactions) for every transaction.  Then once done he would have
> to start again (again possibly refering again to paper receipts) to see if
> the transactions have to clear an existing transaction or be added.

This is the order in which these steps currently appear in the QIF importer. 
But I would propose to switch around the order of these two steps. First,  
the user chooses the transactions that are actually new (existing GUI parts). 
Secondly, the user chooses/confirms the destination account for the new 
transactions (new GUI part).

Surely those two different actions can be perfomed inside the same dialog 
window, but it doesn't change the fact that these still are two different 
actions. I would prefer to have these two different actions in different 
windows / druid pages.

Christian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iQCVAwUBPd1moWXAi+BfhivFAQGRawP+NBdimXNyLcPB4u6Q+mY9xgwiVnj4+Nlk
qUSoaTSNm5ub2k4dn0gInY0hW4V+CZfk8JE1gSQpv2OkYJPvnTKbV/uOD/w5CuKL
RHxKksv7gLBpXOFUXBdT6qKK7jBgFaJFoXOocBOvmeHmMQ71YAN/hN/wClt8VxZH
R70Lkgg8sn0=
=0iSf
-----END PGP SIGNATURE-----