On Mon, 13 Aug 2012 09:54:07 -0300, sommeralex <[email protected]> wrote:

Hi Thiago,

Hi!

Thank you for your help (again).

:)

I know how to use the radio/radiogroup
component in tapestry - I'm am lucky. But i would never know how to use it just with the api docu link provided. Using a radio/radiogroup element
should be done in few minutes. (and IS done in few minutes also with
tapestry if you know how to do it)

Writing documentation is hard and time-consuming. You can help by writing your own on the wiki or filing documentation JIRAs.

instead of providing an update with a minor performance gain, the
documentation should be simplified and extended with more examples. Hence, I am missing "modern/social" components like a simple working OAUTH plugin e.g integrated with tapestry for e.g facebook.

Have you seen http://tynamo.org/tynamo-federatedaccounts%20guide? ;)

Don't forget that the Tapestry team cannot focus on everything at the same time. We have finite time. Nobody, besides some Howard's gigs, is being paid for developing Tapestry, so please remember that. This is a voluntary effort, so often something is provided in Tapestry (or any other open source project) because someone needed it in one of their projects. The old URL rewriter API (which will have an independent comeback) is one example of that. I needed it, I wrote it, added to Tapestry itself, everybody can (now could) use that.

In addition, instead of having a large number of features in Tapestry itself, we prefer to focus on having a solid foundation upon which other can build, so other projects like Tapestry-jQuery, ChenilleKit, etc should be considered part of the Tapestry ecossystem, not just what is inside tapestry.apache.org.

Maybe i should start a blog for tapestry beginners :-)

Please do it! I'd love to see that. :) I should have started blogging long ago . . . but I decided I wanted to blog about Tapestry in a blogging system written in Tapestry and I haven't had the time to write it yet . . .

--
Thiago H. de Paula Figueiredo

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to