Re: let's drop model support

From: Magnus Lie Hetland <[email protected]>
> On the other hand, I'm reluctant to closing the door on MVC
> completely. Even if (big if!) we decide to drop MVC at the moment, it
> would be good to have the option of reintroducing it later without a
> complete redefinition of attribute semantics etc.
>

For clearly immutable value (booleans, tuples and numbers):

comp.prop should behave value in, value out .

The real questions are about: comp.items and comp.text

and there all our problems are not only related to supporting MVC, but to the
fact that we wanted a minimal interface between front-end and back-end and this
has influenced the componenent interface too, that apart from add (?) is just
reduced to getting/setting attributes but e.g.

*) a Tk listbox has insert and delete too, to manipulate the list items
*) a swing JList let you access a model to do the same things
...
[same for text widgets]

that's why we have come to need in-place modification etc which interacts
poorly with the idea of optional model support.

OTOH comp.items and comp.text with just copy semantics is probaly too minimal.

So it's a trade-off this kind of issues and having e.g. Listbox offer a richer
interface (with the problem of how manage then the back-end/front-end
interaction).

regards.








-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf