<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 1/23/2013 3:23 AM, Heiko Braun wrote:
<blockquote
cite="mid:46DDF9E1-93E8-411C-883E-791E37AADE58@redhat.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div><br>
</div>
<div><br>
</div>
<div>Right, it might have slightly different semantics. </div>
<div><br>
</div>
<div>As food for thought, we also discussed the addition of
another ModelType.TEXT.</div>
</blockquote>
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. <br>
<br>
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:<br>
1) What are all the types we need?<br>
2) Is just using ModelType enough or would we need a layout hint
attribute anyway?<br>
<br>
<br>
<blockquote
cite="mid:46DDF9E1-93E8-411C-883E-791E37AADE58@redhat.com"
type="cite">
<div>It could support:</div>
<div><br>
</div>
- the distinction of the input type (text, text area)
<div>- multi-lines</div>
<div>- different character sets when stored as CDATA</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
<div>
<div>On Jan 22, 2013, at 5:25 PM, Jeff Mesnil <<a
moz-do-not-send="true" href="mailto:jmesnil@redhat.com">jmesnil@redhat.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite"><span style="font-family: Helvetica;
font-size: medium; font-style: normal; font-variant:
normal; font-weight: normal; letter-spacing: normal;
line-height: normal; orphans: 2; text-align: -webkit-auto;
text-indent: 0px; text-transform: none; white-space:
normal; widows: 2; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width:
0px; display: inline !important; float: none; ">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…</span><br
style="font-family: Helvetica; font-size: medium;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: 2; text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; ">
<br style="font-family: Helvetica; font-size: medium;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: 2; text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; ">
<span style="font-family: Helvetica; font-size: medium;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: 2; text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; display: inline
!important; float: none; ">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.</span><br style="font-family: Helvetica; font-size:
medium; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height:
normal; orphans: 2; text-align: -webkit-auto; text-indent:
0px; text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; ">
<br style="font-family: Helvetica; font-size: medium;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: 2; text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; ">
<span style="font-family: Helvetica; font-size: medium;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: 2; text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; display: inline
!important; float: none; ">Heiko, wont' we have the same
question with other types of input (e.g. time input to
represent timeout, etc.)</span></blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
jboss-as7-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jboss-as7-dev@lists.jboss.org">jboss-as7-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jboss-as7-dev">https://lists.jboss.org/mailman/listinfo/jboss-as7-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>