To clarify the object oriented CSS point, I was referring to the style of
writing CSS as described at oocss.org. It outlines a convention for
writing your CSS in an "object oriented" way. Here's a nice presentation
describing it:
http://www.slideshare.net/stubbornella/object-oriented-css
I used
Hi,
We have 4 teams of 6-8 people each working on a pretty large Tapestry
project. We've encountered quite a few of these problems along the way ;)
I have to agree with Peter, well separated, testable code will make your
life immeasurably easier - get this bit right and everything else should
flo
Hi John,
There is no single formula, it just depends on the way you like to work..
Tapestry does make things easy though because by nature its very modular, and
IoC by nature encourages better interoperability. We currently have about 7
Tapestry applications sharing resources, so here are some
What i've done for our company where we work with 3 people on one site is to
divide the site into smaller component libraries, each library is a
standalone JAR which on deployment get released in the WEB-INF\lib folder
allowing the 'main' site to find this module and make use of it.
see:
http://
