I'm working on creating a different namespace URI that includes the t:comment element, for compatibility.
I'm also thinking that <t:comment> could consume elements rather than throw an exception if one is found. That would make it much like $remove$. In fact, perhaps it should be called t:remove? On Thu, Mar 5, 2009 at 1:00 PM, Thiago H. de Paula Figueiredo <[email protected]> wrote: > Em Thu, 05 Mar 2009 17:49:06 -0300, Fernando Padilla <[email protected]> > escreveu: > >> isn't there already a "$remove$" feature or something like that? > > This was a Tapestry 4 feature. I've made a simple component, Remove, that > does almost the same thing. It's very simple: boolean setupRender() { return > null. }. <div t:type="Remove">blah</div> :) > >> >> Thiago H. de Paula Figueiredo wrote: >>> >>> Em Thu, 05 Mar 2009 17:40:56 -0300, Fernando Padilla <[email protected]> >>> escreveu: >>> >>>> did you just create a new "reserved word", comment?? >>>> so no one can create a component named "comment"? >>>> that seems like it could turn out to be a big regression.. >>> >>> I guess you can still use <div t:type="comment">. Anyway, I agree with >>> Fernando. A name less likely to be used in real comments would be a better >>> choice. <t:tapestrycomment>? >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > > -- > Thiago H. de Paula Figueiredo > Independent Java consultant, developer, and instructor > Consultor, desenvolvedor e instrutor em Java > http://www.arsmachina.com.br/thiago > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
