TextField Document model

[Mark Claassen]

> Adding a new constructor to set it once would likely work for most cases.
> I suspect making it dynamic is a lot more work.
Maybe it is a bit more for the API designer, but, the way I understand it,
this would preclude the use of the SceneBuilder to create the components,
without a lot of subclassing.  (See the rest of this thread.)
If this is not the case, I would be very interested to know how to
accomplish this.

On Thu, Oct 18, 2012 at 5:09 PM, Scott Palmer <swpalmer at gmail.com> wrote:

> On 2012-10-18, at 3:28 PM, Richard Bair <richard.bair at oracle.com> wrote:
>
> > I don't have any philosophical reason for not having content be mutable.
> My only concern here is that having it mutable introduces some additional
> complexity in the class / skin -- or at least it might.
> >
> > BTW, if you find that changing it dynamically works perfect, I'd be
> happy to do the code review (including Jonathan).
>
> Adding a new constructor to set it once would likely work for most cases.
> I suspect making it dynamic is a lot more work.
>
> Scott