Posted by editor
on September 14, 2007 at 6:54 AM PDT
Thumbing through Filthy Rich Clients with a smile... also:
Java Today: ME Application Developers project, JavaTools Community Newsletter #138, and JSR 277/291 interop strawman needed
Weblogs: ME community stars, JXTA's use of generics and enums, and Sun Tech Days Boston (Day 2)
java.net Poll: How many bugs or feature requests have you filed with java.net projects?
Forum Posts: Looking Glass on Windows, using JT Harness, and WSDL 2.0
Thumbing through Filthy Rich Clients with a smile
My copy of Filthy Rich Clients arrived yesterday, and it's fun to just pop around in the book to see what Chet and Romain cover. java.net projects are prominent throughout the book, particularly Aerith and the timing framework , which gets two whole chapters to itself. Both authors have a strong sense of humor, yet it doesn't get in the way of delivering the material -- Chet goofs on the Wikipedia definition of a convolution kernel in a footnote, but still delivers the goods on what the
ConvolveOp is, what it does, and why it's the one
BufferedImageOp from the
java.awt.image package that you should absolutely master.
Writers like Chet and Romain are pretty rare commodities, it seems: effective writers who write to be read, do so with an engaging and fun style, and have a wide-ranging set of interests. Anybody hoping to write articles and books would do well to pause a moment and think, "what is it about the stuff that I really like to read that makes it good?" It's usually not the topic, but rather the presentation. Good writers engage the reader's interest, develop their thoughts in a fashion that's easy to follow, occasionally remind the reader of where they're going with all this, and don't indulge in unneccessary sidetracks or details. We had one article the other week that was made dramatically better when the author simply moved the "how it works" section down to the bottom of the article -- it allowed the reader to start by learning about the topic in general and seeing what it did, and only then got into the details, even though the details are generally what's most interesting to the expert. It's the old novice-expert shift, and good writers help their readers make the move from one side of the scale to the other.
Over on TheServerSide , Joseph Ottinger recently posted some guidelines on submitting items to that site, starting with a set of tips , and then getting more deeply into the topic of the concepts of tech writing . Some of this guidance actually resembles items in the java.net writer's guide , like writing for readers who don't already know everything about your topic (since that's, you know, kind of the point...). I Skype'd with Joseph yesterday, and we traded notes about how to help writers better reach their potential readership. He's got some great points in his two guideline articles, and would-be writers should check them out.
And then go read Filthy Rich Clients, because Chet and Romain are clearly enjoying what they're doing with the graphics APIs, and write in a way that shows they want you to come along for the ride.
In Java Today ,
the ME Application Developers project is becoming a treasure-trove of content
for application developers. They report, "over the last couple of weeks and months we've added
the Mobile Ajax sub-project, the phoneME UI Labs project, and the brand-new
MobileAerith demo. The wiki has been updated with more good information and
links to several JavaOne sessions on relevant topics have been added. The
ME Application Developers project front page also has been updated to highlight
the new content."
The latest edition, issue 138 , of the JavaTools Community Newsletter is out, with tool-related news from around the web, announcements of new projects in the community and a graduation from the incubator (AppTale ), and a Tool Tip on using keyword expansion with Subversion.
InfoQ reports on modularity concerns in JSR 277 and JSR 291 Interoperability threatened by lack of a prototype . "The latest salvo in the discussion of JSR 277 , JSR 291 , and OSGi appeared last week in the form of a post by Glyn Normington , spec lead for JSR 291 and Expert Group member for JSR 277. He is concerned that the Expert Group has not been presented with a strawman yet and that the Expert Group will end up merely rubber stamping the strawman rather than discussing it in detail and making changes."
Today's Weblogs , starts with shout-outs from Terrence