On Thu, 20 Jan 2011 18:52:29 -0200, Howard Lewis Ship <[email protected]>
wrote:
So what are the advantages/disadvantages of having another module at
apache, say, tapestry-stdlib vs. just moving such a component into
tapestry-core?
To me, a separate module would be the place for functionality that is
important to have ready to use but, at the same time, not used in most
project. I hope I'm not contradicting myself here. :) One exemple: suppose
there's no licensing issues to have some cool components using the Google
Maps API inside the Tapestry project. As Igor said, this would be an
appealing feature, but not used in most projects, so it should be in a
tapestry-extras module.
To me, the idea of saying "if you want to present confirmation to a
user, just use the AlertsManager and Alerts component" is more
satisifying in a tutorial than saying "create a flash-scoped message
field, etc., etc.,". However, if the AlertsManager is in a optional
library, I might not feel as good about referencing it in a tutorial
compared to if it was in tapestry-core.
Not as good, but not much as long as it's explained it's part of the
Tapestry project and how to include it in a project (Maven, Gradle, Ivy,
etc).
And if we end up effectively
mandating the user of tapestry-stdllib, how valuable is it separate
from tapestry-core.
Agreed.
Alternately, if we have a stdlib, do we move some of our existing
components and mixins out of core?
I don't think so, hence my suggestion of a tapestry-extras module.
--
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]
