Sirs,
I am unclear as to why you have not officially 'fixed' errors in code in your book 'Java Swing'. Let me initially state that I am not writing to 'bash' you, I am simply expressing my disappointment and surprise.
Case in point.....
pg.35 'Sim......Frame'.... Excuse me, but there are three authors of this book, correct? Doesn't it bother any of you that since 1998 (first printing?) no repair has been done to the code here? Make this code work as is.... go ahead.. guess what.... you can't!!!!! (How about internalFrame.setVisible(true);)??????
I'm a beginner at this, it's true, but so are many other people who spend their money on a book the three of you wrote. I'm not declaring myself an expert by any means, but I don't understand why things like this aren't addressed and fixed.
The next example..... 'Web Site Manager'
It is described as 'a bit of fun' and 'robust error checking gets in the way of having fun, and that's all we're really trying to accomplish with this application.' Fun for who??? Didn't you put yourselves in the shoes of your readers?? This example is a monolith. Yes, I'm impressed that there are methods and classes flying all over the place, but how does it help me if I can't get it to run??
This book cost me $44.95 at Barnes and Noble. I'm not writing to get my money back, I'm trying to let you see this book from the perspective of a non-expert.
(And why write with experts as your target audience? I'm willing to bet you that the majority of people buying this book are anywhere from 6 to 12 months into Java.)
I've purchased other Java books, in Horton the code is bare for the sake of teaching, and the code runs. In Deitel and Deitel the code and concepts progress through many levels, but the code runs. In Java Black Book the code runs. In Core Java2 the code runs. Why do I assume that as I continue through your book I'll be visiting this web page for errata in each chapter???
Ken Gorman
|
