My tuppence worth: > required is from the component perspective, not from the developer perspective
Therein lies the confusion, for the documentation is read by developers looking to see what is 'required' from them! (I've yet to catch my T5 components reading JavaDocs or Googling for answers!) As the documentation is meant for developers it should focus on their needs - i.e. what they 'need' to provide to make the component work. As a developer I'm not looking at components in isolation, but rather, I'm looking at T5 as a framework. So if the framework provdes defaults and I don't need to, fantastic! Moreover, I don't need to know that attribute was ever required, for that's now unimportant information. Steve. On 23 August 2011 10:18, Robert Zeigler <robert.zeig...@roxanemy.com> wrote: > > On Aug 22, 2011, at 8/229:06 PM , Bob Harner wrote: >> >> "In many cases, a ValueEncoder can be generated automatically from the > > And this is the crux: in /many/ cases... /can/ be generated. When it can't > be, you'll still get the exception that it's not bound and must be. > Ergo: required. :) > > Robert > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
