On Thu, 2002-11-21 at 17:58, Chris Lyttle wrote:
> What I think might work is a dialog sort of like this; 
> 
> Status Date      Description    Amount  Dest Account
> Clear 02/21/2002 ATM Withdrawal $200 
> 
> o This matches the following transaction;
>       02/21/2002 Cash           $200    Expenses:Cash Withdrawal
> o This is a new transaction
> o Postpone this transaction
> o Replace this transaction
> 
> And have the above for each transaction being imported. The right pane
> could still list other possible matches (Though I would make it somewhat
> smaller). The user is then certain what match has been picked, the top
> line could be directly edited to create a new transaction (if This is a
> new transaction is selected). It also gives a visual indication to the
> user with the radio button selection of what exactly will happen to the
> transaction. The Status can be used for the clear/reconcile decision.
> 
>

Derek pointed out it was difficult to understand what I meant above. So
I went ahead and used glade to implement something I feel might be
useful along the lines I was talking about above. A few things I
couldn't find widgets for so had to improvise.

The way I see this dialog working is like this;

1) User imports file, chooses account the file is for in Benoit's
Account picker
2) This dialog pops up with the list of downloaded transactions in the
left pane. Each transaction is red.
3) User selects a transaction, the list of matches appears on the right
pane, with the top pick automatically filled into the 'This Matches The
Following Transaction:' register field. This is read only.
4) If the user accepts this he just has to select a different
transaction. The previous one will turn blue in the Download list to
indicate it was processed. (This could also require the Apply button to
be pressed, but personally I'd find it annoying to have to confirm my
choice).
5) If the user doesn't like the match he just has to choose another one
from the potential matches list or...
6) Select 'This Is A New Transaction:'. This time the fields are not
only editable, they are actually the register (sort of like josh has in
the SX Editor). The user can create a whole new transaction from the
downloaded data, with splits, etc as wanted.
7) Again once he moves to the next transaction, the edited one updates
with his changes and turns blue to indicate its been accepted.
8) The last two choices are also available if needed.

This may be to hard/over the top for where we are now in the release
process, but I feel it could give us what we need. Having thought a bit
about how the druid process operates I'm not to sure now if it gives the
user the best experience. Hopefully this will help the discussion.

Chris
-- 
RedHat Certified Engineer #807302549405490.
--------------------------------------------
        |^|
        | |   |^|
        | |^| | |  Life out here is raw 
        | | |^| |  But we will never stop
        | |_|_| |  We will never quit 
        | / __> |  cause we are Metallica
        |/ /    |
        \       /
         |     |
--------------------------------------------

Attachment: transaction-matcher_glade_DEFANGED-10.DEFANGED-49
Description: application/defanged-49

This message has been 'sanitized'.  This means that potentially
dangerous content has been rewritten or removed.  The following
log describes which actions were taken.

Sanitizer (start="1037958582"):
  Part (pos="1032"):
    SanitizeFile (filename="unnamed.txt", mimetype="text/plain"):
      Match (rule="2"):
        Enforced policy: accept

  Part (pos="4185"):
    SanitizeFile (filename="transaction-matcher.glade", mimetype="application/x-glade"):
      Match (rule="default"):
        Enforced policy: defang

      Replaced mime type with: application/DEFANGED-10
      Replaced file name with: transaction-matcher_glade.DEFANGED-10

  Total modifications so far: 1


Anomy 0.0.0 : Sanitizer.pm
$Id: Sanitizer.pm,v 1.54 2002/02/15 16:59:07 bre Exp $
This message has been 'sanitized'.  This means that potentially
dangerous content has been rewritten or removed.  The following
log describes which actions were taken.

Sanitizer (start="1037958610"):
  Part (pos="2412"):
    SanitizeFile (filename="unnamed.txt", mimetype="text/plain"):
      Match (rule="2"):
        Enforced policy: accept

  Part (pos="5565"):
    SanitizeFile (filename="transaction-matcher_glade.DEFANGED-10", mimetype="application/DEFANGED-10"):
      Match (rule="default"):
        Enforced policy: defang

      Replaced mime type with: application/DEFANGED-49
      Replaced file name with: transaction-matcher_glade_DEFANGED-10.DEFANGED-49

  Part (pos="34169"):
    SanitizeFile (filename="sanitizer.log", mimetype="text/sanitizer-log"):
      Match (rule="2"):
        Enforced policy: accept

  Total modifications so far: 1


Anomy 0.0.0 : Sanitizer.pm
$Id: Sanitizer.pm,v 1.54 2002/02/15 16:59:07 bre Exp $

Reply via email to