Re: [lmi] InputSequence questions

[Vaclav Slavik]

On Thu, 2010-03-25 at 02:11 +0000, Greg Chicares wrote:
> Well, I was making a tacit assumption that the popup editor
> would edit an InputSequence object's internal representation,

That was my assumption too -- I'm not particularly looking forward to
duplicating the parser. Let's revisit this if I/we find out that it's
impossible to work with (normalized into our preferred form)
InputSequence.

It's probably clear to everybody, but let me explicitly mention it
anyway: it won't be possible to preserve original form of the sequence
after editing it this editor. We'll have to either use
mathematical_representation() to produce string representation or --
preferably -- have some nice_representation() that makes it a bit more
readable. At the very least, it should omit implicit content: "0" is
better for humans than "0 [0, retirement)".

> I'm trying to simulate this in my mind, and now I wonder whether
> an "Add" button is truly needed. If I start with a single row:
>   [  ?  ]     until maturity
> and then fill it in this way:
>   [ 1000]     until retirement
> then as soon as the "until retirement" control loses focus, it's
> evident that a new row must be added.

If even last row's "until maturity" is editable, then you are right.
This is the auto-adding improvement over my first design suggested by
Vadim. So I think we all agree on this version...

Vaclav