Em Wed, 21 Jan 2009 21:46:20 -0300, manuel aldana <ald...@gmx.de> escreveu:
OK, but why does the layout component need to know what the main content is?
If it is a layout, yes. Otherwise, it would be an ordinary page.
As in other mail mentioned the only (but major) cons I can see is that making the Layout as the main-entry page is not very flexible and breaks somehow the tapestry page concept.
When people here talk about a Layout component, we are talking about something described by the Tapestry documentation as "A Layout component exists to provide common content across all pages in your application.". A Layout is a component, not a page, at least in the vocabulary used in this mailing list. :)
It does not mean that you cannot have more than one Layout (but they should be two different components, each page would use zero or one of them) or parameterized Layout or Layouts. ;)
-- 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: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
