Tapestry gives you a bunch of options here and elsewhere. Perhaps thats a failing, but it means you can adopt the practices that make sense to you, in terms of naming and organization.
On Fri, Jul 8, 2011 at 7:51 AM, Thiago H. de Paula Figueiredo <thiag...@gmail.com> wrote: > On Fri, 08 Jul 2011 11:06:42 -0300, Nicolas Barrera <nbarr...@gmail.com> > wrote: > >> Hi, > > Hi! > >> As it's not mandatory to have a @Component variable in Index.java I >> started to think that including comp1 just as a tag in the tml may result in >> a more difficult way of finding which pages >> depend/include comp1. > > Good point. :) > >> Is there any recommendation you would give a tapestry newbie on how to >> depend or include his own components into pages? > > Use the option you think it's the better one. I don't think there's any > recommendation about it. > > You haven't asked, but I prefer to use <div t:type="If"> than <t:if>. :) > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and > instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
