Well, I think you should do what you feel is best for you right now. If you need a timeout from coding then write a book. If you feel a book will take too much of your time then code again. I'm still hoping my publisher will translate my book. So maybe there will be an english book even if you decide not to write one. I asked the published several times but didn't get any feedback yet. I suppose they are not ready to make a decision right now.
However, if you need some co-authors I'm ready. Not sure I'm allowed to but I can check it. I remember some clause in my contract about writing competing books. Don't get me wrong but a 5.2.0.0 release without any single commit of Howard would be something awful. :) It would be a historical event and the final prove that Tapestry is no longer a one men show. We have 29 fixed issues in current 5.2 trunk. The both most popular issues will be fixed in the next days. I'm on the verge of committing fix for http://issues.apache.org/jira/browse/TAP5-138 . Robert was going to provide a fix for https://issues.apache.org/jira/browse/TAP5-815 this weekend. JSR 303 support is almost there. On Sat, Nov 7, 2009 at 7:11 PM, Howard <hls...@gmail.com> wrote: > I've been consciously letting Tapestry 5.1 sit and stabilize for a > while ... a time that's stretched a few months longer than I initially > intended. > This is due to a number of factors: my return to independent > consulting, my desire to write a definitive Tapestry 5 book, and > preparations for many trips and speaking engagements. > All of these factors have worked on each other: I've been improving and > extending my Tapestry Workshop training materials which can be quite > time consuming. I've also (over the last several months) been on the > road several times, talking about Tapestry or doing Tapestry training. > I do want to write a book on Tapestry but if I start writing 5.2 code, > I know I'll be sucked right in ... lots of code (that darn Spring Web > Flow integration for sure this time) and bug fixes. > In addition, I've had an embarassment of riches: two main clients, one > regular part time, and the other requesting (but not always getting) > all my remaining time. I also have additional clients and training > engagements waiting in the wings. I simply have a lot of draws on my > time. > As usual, working on real-world projects lets me experience the "rough > edges" of Tapestry and fills me with ideas on how to address those in > the next release ... often by splitting up Tapestry services into > smaller, more easily overridden chunks and carefully moving internal > services out into the public APIs. > Finally, I've been very pleased by the fact that as I've stepped back > temporarily from my normal stream of commits, the other Tapestry > developers have stepped in and filled the gap. There's been quite a bit > of activity especially from Igor that I've barely had a chance to keep > up on. > So the question is: do I wait and see if time opens up in Q1 to > actually start on a T5 book ... or do I jump into 5.2 coding and leave > books to others? It's much, much easier to write code than to write a > book ... a book is a large amount of concentrated effort. It's very > hard to accomplish anything on a book using an hour here or an evening > there ... whereas Tapestry's code base lends itself to that kind of > effort quite nicely. > > -- > Posted By Howard to Tapestry Central at 11/07/2009 10:11:00 AM -- Best regards, Igor Drobiazko
