Re: [lmi] tasks 2007: bug 104481: fund selection

[Evgeniy Tarassov]

On 2/21/07, Greg Chicares <address@hidden> wrote:
>
[...]

Thank you for such an exhaustive explanation!

> The user needs to specify the percentage that goes in each account.
> So we've got a vector of percentages p0, p1, ... p39 constrained by
>   0 <= px <= 100
> and
>   100 <= sum of all px

Oh, i guess here you mean 100 >= sum of all px.

> Because the cardinality of the problem is sizable--perhaps forty--you
> might first think of using a grid. But the typical cardinality is much

Oh, I think a grid would be confusing because the data is only one
dimensional. The only advantage over a list (IMHO) is that it will
automatically align account names and partition values. Another
'feature' could be the fact that grid allows editing in place, but
this could bite in the back someday, the moment an additional
information is needed to be shown while editing an entry (such as
allowed value range, or a resulting absolute value (not percentage,
but total * px)).

What if the list of accounts (taken from the legacy application
interface) contains only non-null entries. While the complete list of
acounts being accessible through another (maybe a drop down) list, and
when a user selects an item in the list it is added to the main list
(if needed) and selected, so that a value could be added right away.

Another idea is to replace the text control field (for entering px
value) by a pair of field -- a ruler with a text field next to it. The
ruler may also contain a non-draggable indicator to show the maximum
allowed value (0 <= pk <= 100 - (sum of all px) + current value of
pk).

Just a notice -- i would slightly rearrange controls from the Funds
section of the legacy application to make the relation between widgets
data more explicit. For example:
from left to right:
group1) checkbox (or a radio radiobutton) the px uniformly equal
group2) list of accounts
group3) the group of widgets for editing selected account px value

Or maybe to position them like (below)?
group1 - top
group2 - left_bottom
group3 - right_bottom