Le 22 janv. 2013 à 16:56, Heiko Braun <hbraun(a)redhat.com> a écrit :
Some implications I would like to hear your thoughts about:
a) lowering the default max-length might break your subsystem and/or specific clients
b) keeping the current default and doing it case-by-case will result in text input
(opposed to text area) for all String attributes once we switch to a dynamic UI (usability
drawback).
That also means that depending on the max-length, the attributes would have to guard their
values against line breaks (that you can have in a text area and not in a text input)….
Not sure if that'd a real problem in practice…
what about c) add an additional metadata flag to the attribute definition that can be set
for the attributes that must be represented in a text area.
Heiko, wont' we have the same question with other types of input (e.g. time input to
represent timeout, etc.)
jeff
--
Jeff Mesnil
JBoss, a division of Red Hat
http://jmesnil.net/