TextField Document model

[Jonathan Giles]

On 23/10/2012 6:22 a.m., Mark Claassen wrote:
> Even though I was pushing for the mutable content, I am leaning toward the
> ContentFilter approach now.  If the passing of the control as a parameter
> is acceptable, then I think it makes a nice encapsulation; where an
> implementer can, in one class, deal with the data model and cursor position
> without needing to subclass anything.  Hopefully this does not conflict
> with the Control / Behavior / Skin concepts.
No, this approach wouldn't impact on the Control / Skin / Behavior 
concept - it seems totally reasonable. Everything you're discussing 
would be API on the Control.

I'm not entirely clear on your ContentFilter specification, but I figure 
we can cross that bridge when we get nearer to it, rather than try to 
design API from afar.

-- Jonathan