By default "iterating" a set will use a setseq which may still uniquify
information if it finds duplicates (but it may not as it's lazy &
al). #flatten conserves the seq type, so if there are two equal
operation items amongst all selected operations they may get
deduplicated, with the end result of operations disappearing in the
final formatted result.
Hiding of 0-values was only for accounts which hadn't been operated
on (for balance, or operations which had not happened for
debit/credit). Balanced account balances should not be hidden.
* interaction is terrible, select is ugly but radio buttons take way too
much vertical space, no matter whether they're on the left or the
right
* may be possible to unify operations lists between chart of accounts
and entries? Not currently selected set, just the list of possible ops
Only do so if the last user action was enabling said operation,
otherwise things get confusing.
=> keep a separate 'active' value which is unset when an operation is
disabled
* move chart of accounts higher in document
* rewrite text a bit
* split controls to left-hand column
* remove dependencies between operations
* highlight result of last-applied operation (not very good looking atm)
After discussion with fp this probably isn't the direction (ish), but
want to checkpoint this in order to work on other stuff earlier in the
document, but not commit a single gigantic blob of stuff.
