TextField Document model

[Mark Claassen]

Looking at the source for TextInputControl, I see I need to refine my API
ideas a bit.  The cursor control is, of course, also manipulated from other
methods (like replaceSelection) in the controls.  I need to reconcile these
regardless of which API we choose.

On Mon, Oct 22, 2012 at 2:52 PM, Jonathan Giles
<jonathan.giles at oracle.com>wrote:

> 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
>