This is a much welcomed improvement. It's definitely a step in the right direction.
It'd be nice if the components themselves were further categorized, much like for T4. Forms, links, etc. I'm a big fan of the examples, as well, and look forward to seeing more of them. As a guy coming from T4, I would have killed to see an example of using an "else" with an "if". I think I spent a solid afternoon on that because it was so different from the way it'd been done in previous Tapestry versions. Another thing that I think would be nice is a cross-ref from the binding type to a little blurb about it. E.g., I was looking at TextField and saw the new "nulls" property. I had no clue what the "nullfieldstrategy" binding was and had to fumble around the site a bit until I found its description. Hope some of that was helpful. -- Kevin On 1/31/08 1:58 PM, in article [EMAIL PROTECTED], "Howard Lewis Ship" <[EMAIL PROTECTED]> wrote: > I've been very busy this week improving the Tapestry Component Reference. > > The Component Reference is now generated as multiple pages: an master > index, and one page per component (or mixin, page, base class) that is > documented. > > Documentation partly comes from the JavaDoc for the component, and > partly from an extra hand-tooled documentation file. The hand-tooled > documentation gives extra examples and notes. > > You can view the current documentation set here: > > http://tapestry.formos.com/nightly/tapestry5/tapestry-core/ref/index.html > > Feedback is most welcome! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
