I'm not sure I'm ready to endorse in writing and in public :) I would be interested in hearing your thoughts on the "incomplete feeling" it gave you... I actually got just the opposite impression, that it touched on a great many relevant things. Perhaps because it was admittedly shallow detail-wise in spots? The language issues I tend to gloss over because even store-bought books these days tend to have far more grammatical/careless errors than they should... how many errata does a typical tech book these days have?!?
I think for the target audience I forwarded it to here at work, it's very good... they just need to be made aware of a great many things and have a clue about them, not become instant experts in them. For those of us with more experience, we aren't likely to get much, if anything, out of it... although I have to say, I've seen a great many piss-poor attempts of explaining Tiles, but the brief few paragraphs in this about it was very clear, concise and understandable. -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com AIM: fzammetti Yahoo: fzammetti MSN: [EMAIL PROTECTED] On Tue, November 15, 2005 1:13 pm, [EMAIL PROTECTED] said: > It might be worthwhile to add your review (below) to the wiki page > http://wiki.apache.org/struts/StrutsBook I, for one, was put off by the > language errors and general incomplete feeling of the document, but your > comments would lead me to give it a closer look. > >> -----Original Message----- >> From: Frank W. Zammetti [mailto:[EMAIL PROTECTED] >> Sent: Tuesday, November 15, 2005 1:08 PM >> To: Struts Developers List >> Cc: Struts Developers List >> Subject: Re: Re: [Struts Wiki] Update of "StrutsBook" by >> GeorgeDinwiddie >> >> >> On Tue, November 15, 2005 12:53 pm, Martin Cooper said: >> > Very strange. The title says Struts Ti, but that is the >> only place in >> > the entire book that Ti is mentioned. >> >> I thought that was odd too :) >> >> I have to say, I spent about 10 minutes looking over this >> thing, and overall I thought it was quite good. Sure, there >> are some debatable points in there, some things that some >> might argue aren't "best practices", and there are some >> mistakes like you've pointed out (no more than most books >> that get published today I'd bet), but it looks to do a good >> job of covering a lot of topics in a decent way. I've >> actually passed a copy along to some colleagues that are just >> getting into the J2EE web development world now... I think if >> they read and understand even half of this it will serve them >> down the road. >> >> > My >> > favourite, though, is page 3, where is says "This book >> should be used >> > by". (That's the entire sentence.) >> >> Hey, that's flexibility man! :) >> >> Frank >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
