I think documentation and small/focused cookbook-type examples (thank goodness for JumpStart) are the biggest hurdle to people learning and using T5 currently. (At least that is my experience.) The user community and framework are robust, but figuring out how to do something can be challenging at times (even when searching the mailing list).
I'm not exactly sure what the motivation for writing a book would be. Maybe you want to make some money off of it or use it as a marketing tool (developers can tell their PHBs there is a Tapestry book)? My personal preference would be to have good documentation at tapestry.apache.org -- something that can be updated (paper dates itself quickly, especially when Tapestry 5.2.0.24 comes out) and is searchable (Google is my brain these days). Maybe even have it as a downloadable PDF that people can put on digital readers. My hope for you (and us) would be that with good documentation (including examples/tutorials) and marketing, more developers would come, and a larger developer base could increase your consulting business. As for a 5.2 release, it is important, but not as important as good documentation at this point. At least that's my opinion. You could even do a few bug-fix releases (5.1.0.x) before 5.2 while working on the documentation/book. Thanks! mrg PS. I also think having fragmented documentation (the web site, the wiki, etc) makes things harder to find, too. On Sat, Nov 7, 2009 at 1:11 PM, Howard <hls...@gmail.com> wrote: > [lots of things about books and coding] --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
