Here's the thing: I want to have ONE simple thing to describe and document.
These endless chains of options are a tax on users: they are harder to document, harder for users to determine what the "right" approach is, require more code and more tests. If you've read the book "The paradox of choice" you'll realize that giving users lots of options is a way of shirking responsibility for making a real decision. I regret some of my "you can have it your way" design choices in the past, though I don't think any of them are that crippling (though allowing page templates in the web context was a huge mistake). In any case, the question is where to put the files; I'm open to META-INF/assets/ or T5-RESOURCES/assets/ or META-INF/tapestry/assets/ or TAPESTRY/assets/ or something along those lines. -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
