Eclipse Series updated. Make your suggestions

Eclipse Series updated. Make your suggestions

Today we formalized some changes in the Eclipse Series of books. Some time ago Lee Nackman left IBM and his various roles related to Eclipse. Many of you may not know Lee but he was instrumental in the early days of Eclipse and IBM’s ongoing contribution and commitment to Eclipse. Lee, Erich Gamma and John Weigand envisioned and created the Eclipse Series of more then 20 books that today conveys so much vital information to the Eclipse community.

I’m pleased to report that I am taking over Lee’s place on the Eclipse Series editorial board. One of my first tasks has been to help in the redesign of the series look. The result of that effort can be seen in the OSGi and Equinox book going to press this week.

The original series had a sequence of Eclipse photos. This was fitting and attractive. Unfortunately, many of the photos looked similar and as a result is was hard to distinguish one book from another. For the new look we have standardized on a new color scheme and layout. Different books will have distinct images largely at the discretion of the authors but the overall look will be consistent.

We have also introduced a subtle branding differentiation through the use of the Eclipse or EclipseRT logos (see the top left corner) depending on their focus (tooling vs. runtime).

In this new role I will be looking for new ways to drive the content that the community needs. Writing a book is a huge investment and while many teams have made very significant technical contributions, they are not big enough or well-funded enough to write books. There are a few ideas kicking around for how to lower the barrier and what topics are in most need of coverage. While we have  great wealth of new projects at Eclipse, the book pipeline is surprisingly sparse.

As with everything at Eclipse, the community can help. Your suggestions for formats, topics and indeed, content are more than welcome. Feel free to contact me directly or post comments on this blog.

3 Comments
  • Ian Bull
    Posted at 11:08 pm, January 14, 2010

    One thing to consider is composing a book as a sequence of distinct (but related) technologies. In this case different authors would submit 1 or more chapters, which would form the basis of the book. The obvious example that comes to mind is an Eclipse book that covers the basis of Eclipse as an IDE. In a book like this I would expect a few chapters on project management, JDT, XML (and other J2EE tooling), Mylyn, Team/CVS, etc…

    Of course it would be much harder (if not impossible) to create a consistent example that flowed from chapter to chapter, but that may not matter in a book like this.

  • Wendell Beckwith
    Posted at 1:42 am, January 19, 2010

    Ian, you beat me to it as I was just about to suggest the same thing. Writing an entire book is hard (I know I tried and “real life” got in the way), however writing a well defined chapter or 2 or 3 is much, much easier and doable. As a prime example, I think ECF could use several chapters (intro, example, complex example, advanced topics). Actually this might be a great format for all the sub-booklets in the real book.

  • Posted at 7:09 pm, February 21, 2010

    This new looks great. Definitely a nice update from the original look.