tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Harish Krishnaswamy <hkrishnasw...@comcast.net>
Subject Component naming
Date Sat, 31 Jul 2004 17:53:34 GMT
What are the perils of relaxing the component naming strategy?

Currently the component naming is undefined. This leads to complexities 
with javascript, CSS and such. Why not define a component naming 
strategy? This will certainly simplify things quite a bit, right?


To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org

View raw message