>From: <[EMAIL PROTECTED]> 
>Hi
>The magic is a missing attribute: allowBody
>  <form>
>   <textarea jsfid="textAreaTest" allowBody="false" >This 
>     is a mockup.</textarea>
>  </form>
>
>
>You can also use another Clay functionality
>
 
Or, you can put this attribute in the XML config.
 
<component jsfid="textAreaTest" extends="inputTextarea" id="textAreaTest" 
allowBody="false">
    <attributes>
       <set name="value" value="Test was successful." />
    </attributes>
</component>
 
This was David Geary's idea originally.  I guess Tapestry has a similar 
concept.  
In the future, I'd like to provide a annotation replacement for this XML stuff.
 
After all, we need to keep up with Tapestry 5.
 
 
>
><form>
>   <textarea jsfid="textAreaTest">
>    <!-- ### clay:remove ### -->
>    This is a mockup.
>    <!-- ### /clay:remove ### -->
>   </textarea>
>  </form>
>
>Hermod

 
<snippet/>
 
>From: Richard Eggert [mailto:[EMAIL PROTECTED]
>Sent: Monday, February 12, 2007 3:55 AM
>To: [email protected]
>Subject: Strange Behavior with inputTextarea component
>
>
>I've been trying to teach myself how to use Clay (despite the atrocious lack 
>of 
>available documentation).  
 

 
Well, I've been lobbying for some time for David to do some more writing on 
Clay.  The top half of the Clay site documentation was written by David.  I 
guess he's busy making money or something?
 
Anyway, *hopefully* the new Shale in Action book will have some material on 
Clay.
 
>In the process of doing this, I put together a very 
>simple "hello world" style application.  However, the behavior is not as 
>expected, and I'm not sure whether I'm doing something wrong or there's an 
>actual bug in Clay.
 

BTW, Hermod, thanks for all your help!
 
Gary

 

Reply via email to