On Wed, 29 Aug 2012 17:28:06 -0300, Muhammad Gelbana <m.gelb...@gmail.com>
wrote:
Yes that's true.
Is including pages in a component library not common ?
Including pages in a component library is common. And don't forget that in
Tapestry pages and components are 95% the same. A page is a component with
URL and activation context, but without parameters and that can't be
declared inside other components or pages.
Calling it a "component library" makes it sound like it's only for
components.
It's just the shorter name possible. A component library can have pages,
components, mixins, resources, etc.
Was modules supported mainly as component libraries ?
Absolutely no. Modules are a Tapestry-IoC feature, and Tapestry-IoC
doesn't know about web apps, not even Tapestry(-core) itself.
Pages *are* components. And pages in component libraries is common.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
