Another topic of great impact would be 'design methodologies with tapestry': By just knowing the main features of the framework (Ioc, components, ...) and without considering its internals what one can say about best design practices? Are there any suggested workflows of design that exploit tapestry-provided features? Some de-facto standards?
Two critical points: - not limit yourself to Web apps, even if they are the great majority if t5 based software - it's important to explain WHY one design choice is better than another when using T5 Cheers -- Alessio On 8-ago-2013, at 20:54, Bogdan Ivascu <ivascu.bogdan...@gmail.com> wrote: > I would find a Tapestry book covering in depth Tap-Ioc very appealing. > Another area of great interest for me is the client side part of Tapestry > as I find myself writing more and more client side code these days. In > depth ajax coverage would be a great addition to existing material, in my > opinion. > Securing tapestry pages also comes to mind. > I read above Apache Camel, very interesting idea. > > > On Thu, Aug 8, 2013 at 5:50 AM, Geoff Callender < > geoff.callender.jumpst...@gmail.com> wrote: > >> I completely agree. If the aim is to help Tapestry then why not do as >> described below by Alessi? >> >> Equally useful, in my opinion, would be to contribute "advanced topic" >> pages to Tapestry's web documentation. You would reach a much bigger >> audience. You could reach them sooner, because the contributions can be >> incremental. You could be responsive and up-to-date, because it's a cinch >> to modify. >> >> Besides, you know there's no money in technical books these days, yeah? >> >> Nonetheless, Thiago, I applaud your enthusiasm and your massive ongoing >> contribution to Tapestry. >> >> Cheers, >> >> Geoff >> >> On 07/08/2013, at 4:35 PM, Alessio Gambi wrote: >> >>>> I am not sure that there is enough of an audience for two books. >>>> Perhaps you can cooperate with Igor to get your content into his book? >>>> There would be a lot of marketing synergy there at least. >>> Writing a book is a huge commitment and takes usually a lot of time; and >> if we consider the fast pace at which T5 is evolving lately I do not think >> that writing another one-man-book is the best strategy. >>> >>> Why don't we -as a community- collaborate towards a Web magazine/journal >> or any other form of periodic publication ? >>> >>> Main reasons that I see in favor of this more flexible (agile if you >> like): >>> >>> - papers are more focused and requires in general less effort than a >> book. They have a fixed number of pages so authors are 'forced' to just say >> what it is important... Extensive code and additional examples can be also >> published somewhere else. >>> >>> - articles are cheaper (free if the authors wish) to sell and easier to >> distribute (google scholar like) >>> >>> - several authors can contribute to a single article and several papers >> can be merged into a more concrete/solid publications (book chapters). >> Making collaboration a daily activity. >>> >>> - committers and other members of the community can contribute also by >> reviewing the various contributions. This will raise the quality of the >> publications and will give credibility to them. >>> Remember that peer review is MUST be done in a voluntary fashion for >> many reasons, >>> I >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >>> For additional commands, e-mail: users-h...@tapestry.apache.org >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
