I think it's fair enough for a developer of the framework to write a book. This gives a more comprehensive insight in the framework. Buying a book is a choice to be exercised by us . No one forces us.
If it is well written and worth it why not buy it. As far as documentation goes, I do agree that with GWT that's a problem. Actually at time I think it's not the lack of documentation but the comprehensive coverage at some common location. Another problem with jet speed the framework is evolving. It's difficult to keep pace for the documentation (I am a developer and I know how hard it is) All said and done, I do not see a reason for why to get pissed off for a developer writing a book. And whenever we have some tutorial/example to share let's do it. On Oct 4, 10:06 pm, Paul Stockley <pstockl...@gmail.com> wrote: > 2.1 Isn't even released yet so why are you pissed off about there > being no documentation! > > On Oct 4, 11:36 am, Ashton Thomas <ash...@acrinta.com> wrote: > > > > > > > > > At the end of the day, the GWT community will benefit from the book. > > For whatever reasons Chris is writing the book I am certain they are > > justified and reasonable and I am sure he will be able to provide the > > GWT community some valuable insight outside of buying the book. > > > yes, books may be a little behind development especially at the rate > > GWT is coming along. So it is understandable that you would prefer to > > have some more agile and publicly available documentation going on. > > > So your argument is understandable but this is probably not the worst > > thing ever. A more appropriate response may be to continue to > > highlight the contributions of people and make specific requests to be > > addressed. > > > On Oct 4, 11:24 am, Isaac Truett <itru...@gmail.com> wrote: > > > > I think if this makes your list of things to get really pissed off about, > > > then life must be pretty good. > > > > Someone who works on GWT gets a writing credit on a book about GWT; that's > > > not something to get upset over. > > > > On Fri, Oct 1, 2010 at 1:38 PM, Tommy Lui <tlui1...@gmail.com> wrote: > > > > Hi, > > > > > Please help me understand why Chris Ramsdale (Google's Developer > > > > Relations team to develop and advocate GWT best practices.) is > > > > writting a book about GWT 2.1 when he works at Google on the GWT team > > > > and there's no official documentation, except for a few waves > > > > available to the developer community. > > > > > Is this some way for him to force developers to buy his book? > > > > >http://www.manning.com/bambury/ > > > > > The book is due to be release in 2011, so I'm sure it's GWT 2.1 not > > > > GWT 2.0 content. > > > > > I'm hoping that I'm not the only person really pissed off about this. > > > > > I'd really like other peoples opinions on this topic > > > > > -- > > > > You received this message because you are subscribed to the Google > > > > Groups > > > > "Google Web Toolkit" group. > > > > To post to this group, send email to > > > > google-web-tool...@googlegroups.com. > > > > To unsubscribe from this group, send email to > > > > google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2Bunsubs > > > > cr...@googlegroups.com> > > > > . > > > > For more options, visit this group at > > > >http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
