Right, it might have slightly different semantics.
As food for thought, we also discussed the addition of another ModelType.TEXT.
It could support:
- the distinction of the input type (text, text area)- multi-lines
- different character sets when stored as CDATA
IMO this would be more reasonable then simply adding "layout" hints as additional attribute meta data. But I am not sure about other implications, i.e. compatibility guidelines of the wire format.
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.)