On Thu, 20 Jan 2011 21:31:47 -0200, Josh Canfield <[email protected]>
wrote:
To the extreme, I'd go so far as to say that I'd like to separate out
* tapestry-ioc - IOC container
* tapestry-servlets - Servlet request processing
* tapestry-templates - Component/page rendering code (t:block,
t:container, t:body, etc... i.e. non-component based template
elements)
* tapestry-components - Core components (t:if, t:unless, t:loop, t:any,
t:zone)
* tapestry-forms - Form components (t:form, t:textfield, etc.)
* tapestry-beaneditor - BeanEditor components
* tapestry-gridview - Grid components
* tapestry-usermessages - User message tracking components
* etc.
I think this is too extreme. I guess it would be very confusing for new
users to figure out what does he/she needs. In addition, each new module
has some overhead from the Tapestry team side. In addition, I don't
consider the current core JAR too large or bloated.
I can't see why the components library itself would be separated in
another project. It's almost impossible to have an useful Tapestry
application without them. In the above example, as Howard said about
dissecting the core jar, both BeanEditor and Grid have the same base:
BeanModel.
My suggestion: keep the core as is and discuss the placement of new
components and services and the creation of another modules case by case.
--
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: [email protected]
For additional commands, e-mail: [email protected]
