<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><DIV>On 07 Feb 2007, at 9:39 AM, Dries Buytaert wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><P style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-height: 14.0px"><BR></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">So, if I understand correctly, you suggest that introducing more types (i.e. float, integer) and corresponding validation routines in core would be the first step.<SPAN class="Apple-converted-space"> </SPAN>This makes sense to me, and shouldn't be too hard.<SPAN class="Apple-converted-space"> </SPAN>Is anyone working on this -- or willing to work on this?</FONT></P> </BLOCKQUOTE></DIV><BR><DIV>I think perhaps we should look at more semantic data types than just float and integer.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>A good example of this would be a title type. Which defaults to textfield, and automatically does the plaintext validation and formatting on output.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>The same with 'markup' or similar, which automatically expands to a widget that has format selectors.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>'id' field type could also be useful. </DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Especially when integrated into a query builder, and even if only for constructing crud functions such as drupal_load('objecttype', 'id1', 'id2');</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Personally I'm more interested in working on the data model side of things, and how it ties into the CRUD functions. I've already made a good</DIV><DIV>start at that in the stuff i did for drupalcon.</DIV></BODY></HTML>