A well established Tapestry style in Tap3 + Tap4 was: <if jwcid="@Conditional" condition="whatever"> ... </if>
I really liked that style, especially for teaching Tapestry and wanted to allow something that immediately understandable but even more concise. On Wed, Mar 4, 2009 at 10:33 AM, Thiago H. de Paula Figueiredo <thiag...@gmail.com> wrote: > Em Wed, 04 Mar 2009 13:18:46 -0300, Ivano Luberti <lube...@archicoop.it> > escreveu: > >> pheeew ! >> Thanks for the quick answer to all of you. > > You're welcome! > >> I was afraid I had made one of the biggest mistake in my life. > > Maybe you just made one of the best decisions in your life.. :) > >> But can you tell me why the choice to abandon the old syntax has been >> taken: to me from the web designer point of view it is still the most >> clean way to implement the call to tapestry. > > Tapestry 5 haven't really abondened the old syntax, besides $content$ and > $remove$, but they're easily replaced with simple components. > I guess Howard (Tapestry creator and main developer) just wanted to create > another syntax, one that is friendlier with XML editors (namespaces). I > never use the <t:componentName> syntax in pages and almost never in > components and I'm quite happy with it. :) > > -- > Thiago H. de Paula Figueiredo > Independent Java consultant, developer, and instructor > http://www.arsmachina.com.br/thiago > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
