<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><DIV>On 06 Jun 2007, at 17:50 , Ken Treis wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><DIV><DIV>On Jun 6, 2007, at 1:21 AM, Lukas Renggli wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><FONT face="Monaco" size="2" style="font: 10.0px Monaco">So yes, you to manually generate the option tags and use #attributeAt:put:</FONT></DIV> </BLOCKQUOTE></DIV><DIV><BR class="khtml-block-placeholder"></DIV>OK, I can do this.<DIV><BR class="khtml-block-placeholder"></DIV></BLOCKQUOTE><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Why aren't you using #callback: instead and let Seaside do the low level html stuff?</DIV><DIV><BR class="khtml-block-placeholder"></DIV><BR><BLOCKQUOTE type="cite"><DIV><DIV>Can we add the trivial helpers for WASelectTag>>name: and WAOptionTag>>value: ? The other form input tags have them. I have added them as extensions in my VisualWorks package, but it seems that they belong in the base. It'd be more consistent with the other form input tags.</DIV><DIV><BR></DIV></DIV></BLOCKQUOTE><DIV><BR class="khtml-block-placeholder"></DIV><BR></DIV><BR></BODY></HTML>