I would suggest that you get a way from the linear, single path flow of writing book.
I have stopped reading most technical books because they assume that I am a beginner and am going to read the book in a strictly serial manner. I would suggest that rather than be chapter focused that you be concept focused (1-2 pages) and provide different paths through the text. So someone who is on the "beginner" path will be lead through the book differently than someone who is an intermediate. -pat On Wed, Sep 3, 2008 at 11:55 AM, Thiago H. de Paula Figueiredo < [EMAIL PROTECTED]> wrote: > Em Wed, 03 Sep 2008 15:31:05 -0300, ProAdmin Dariusz Dwornikowski < > [EMAIL PROTECTED]> escreveu: > > Tapestry alone is no use if you do not have DB. >> > > As a instructor of Java, Hibernate, Spring and other frameworks, my > experience says that people learn way better when they're learning just one > thing, one concept, one feature at a time. Therefore, I think the book must > focus in Tapestry and abstract away the persistence layer. In a later > chapter, the book would show how to integrate Tapestry and Hibernate. In > another chapter, the book would show a complete example of Tapestry + > Hibernate + Spring. > > > Thiago > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
