On 1/23/2013 3:23 AM, Heiko Braun wrote:

Right, it might have slightly different semantics.

As food for thought, we also discussed the addition of another ModelType.TEXT.

I kind of like that idea. If the rule is that a ModelType is all that is provided for layout hints then we should think long and hard about every UI type we will need. ModelType.DATE comes to mind.

Note that I'm not making a slippery-slope argument here. I think the number of these we really need is finite. I think we would need to answer two questions:
1) What are all the types we need?
2) Is just using ModelType enough or would we need a layout hint attribute anyway?

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.

On Jan 22, 2013, at 5:25 PM, Jeff Mesnil <jmesnil@redhat.com> wrote:

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.)
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev