I think two books are in order: First, S2 Basics / introduction : one single app development example. Later, S2 Advanced: advanced topics, deep customization, Internals, Spring integration, Javascript such as JQuery, etc.
I suggest - moving Spring integration to the S2 Advanced book. - adding IDE (Eclipse, ...) configuration to chapter 3. Therefore https://github.com/lukaszlenart/struts-mini-book becomes: 1_introduction.txt 2_generate-project-with-maven.txt 3_basic-configuration.txt (with IDE (Eclipse, ...)) 4_internal-di.txt 5_integration-with-tiles.txt 6_login-and-authenticate.txt 7_final-word.txt On Thu, Oct 25, 2018 at 2:59 AM Lukasz Lenart <lukaszlen...@apache.org> wrote: > pt., 19 paź 2018 o 14:06 Dave Newton <davelnew...@gmail.com> napisał(a): > > > > No recommendations; I'm forced to use Word right now for a Kindle book > I'm > > working on and I hate it (same when I did the S2 book) so don't do > > that--makes code stuff needlessly complicated. > > > > There are many plain-ish-text systems out there--my personal preference > > would be one of those, in a repo, and convert to final format. This also > > allows you to write in code snippets you can pull from the same or > > different repos, which is very convenient. I haven't found a great way to > > do code fallouts though, like PragProg or Manning, in a trivial way. > > Thanks a lot Dave! Yeah, plain text is my favourite format :D > > I made a first step and the basic book setup is ready, you can preview > it here [1] and the source code is available here [2] > > [1] https://leanpub.com/struts-mini-book > [2] https://github.com/lukaszlenart/struts-mini-book > > > Regards > -- > Łukasz > + 48 606 323 122 http://www.lenart.org.pl/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@struts.apache.org > For additional commands, e-mail: user-h...@struts.apache.org > >
