Hi all, my organization recently released a large project using Tapestry 5. We 
are in the process of starting another large project and are hoping to leverage 
some of the existing Tapestry work and components that have already been 
implemented. We plan to form a second team and would like that team to work in 
parallel with the existing team. I am new to Tapestry and I'm concerned about a 
number of things:

 1.  Seems like the best unit of sharing would be at the component level. Am I 
missing anything else?
 2.  How to best manage the shared components and dependencies between teams?
 3.  What CSS and HTML conventions would be needed for this to work? 
(object-oriented CSS?)
 4.  Are there any tools to help ensure best practices are being followed?
 5.  How does having a large number of components affect performance? (should 
we have lots of small components, or less number of larger components…does it 
make a difference?)

I appreciate any feedback.

Thanks,
John York


Reply via email to