yep, just to say that the suggestion worked. Thx! [1] https://issues.apache.org/jira/browse/ISIS-1552
On Sat, 3 Dec 2016 at 13:32 Dan Haywood <d...@haywood-associates.co.uk> wrote: > Ok, thanks... I'll try it out and report back > > On Sat, 3 Dec 2016, 12:02 Martin Grigorov, <mgrigo...@apache.org> wrote: > > There is no need of new method to TextField (or other FormComponents). > We already > have org.apache.wicket.markup.html.form.FormComponent#onDisabled(), it sets > the "disabled" attribute at the moment. > > Sven's suggestion to use Behavior + IComponentInstantiationListener looks > the most flexible to me. > @Dan: this should solve the issue for Isis. > > Martin Grigorov > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Fri, Dec 2, 2016 at 6:03 PM, Martijn Dashorst < > martijn.dasho...@gmail.com > > wrote: > > > On Fri, Dec 2, 2016 at 12:21 PM, Pedro Santos <pedros...@gmail.com> > wrote: > > > After reading the thread on Isis's mailing list, I'm under the > impression > > > that the best solution is to offer an API enabling users to configure > how > > > the disabled text field will be shown. My suggestion is to add the > method > > > TextField.showDisabledAsReadOnly(boolean) and to keep the current > > > "disabled" attribute as the default presentation of a disabled text > > field. > > > > Of course we can change the behavior in a major version such as 8.0. > > > > That said, changing disabled to mean readonly doesn't sound like a > > good idea as a general rule, only if the names convey different > > meanings. > > > > > > OTOH, I doubt adding a `setReadOnly` option to TextField is a good > > option as well. > > > > Martijn > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > >
