The IBM developerWorks newsletter was effectively retired on Friday which really bums me out. I’ve using the newsletter as an easy weekly way of following along with what happened on developerWorks and I’m going to miss the ease with which I could do that. The “new way” (for me at least) is to use the social media outlets (Twitter, Facebook) or the feeds available. I’m going for the latter and just added a series of feeds using the feeds page to my Google Reader. RIP developerWorks newsletter…
Well I just did a quick search on developerWorks and it gave me a lot of info. Among others were the below articles that I think look very interesting. Especially those two first ones look like something that would be of interest to a lot of people venturing into this area.
- Eclipse’s Rich Client Platform, Part 1: Getting started
- Eclipse’s Rich Client Platform, Part 2: Extending the generic workbench
- Create an Eclipse game plug-in, Part 1: Getting started
- Create an Eclipse game plug-in, Part 2: Building and firing a BB gun
- Create an Eclipse game plug-in, Part 3: Gaming the system
- Create an Eclipse game plug-in, Part 4: Packaging, testing, and putting final touches
- Building Eclipse plug-ins using templates
- Eclipse Test & Performance Tools Platform, Part 1: Test, profile, and monitor applications
- An introduction to the Eclipse Web Tools Platform V1.0
A lot of people ask me how to get started with Java programming so when I saw the below entry in the developerWorks newsletter I thought it should be communicated as far and wide as possible.
“developerWorks Java contributor Steve Perry took on the Herculean task of updating the “Introduction to Java programming” tutorials. This two-part series introduces the structure, syntax, and programming paradigm of the Java language and platform.”
Are you ready to get going on development of plug-ins for the Notes 8 client (Eclipse)? If you are then look no further than this series of articles on developerWorks: Plug-in development 101. It’s a bit sad that it isn’t Notes 8 specific but hey it’s in the Open Source zone but even though you get the basics of the necessary steps for creating plug-ins.
“This article introduces some helper classes so you can quickly build and deploy feature-rich, reusable, Eclipse-based components for IBM Lotus Notes. You also learn how to create a foundation upon which other components can be created quickly and easily.”
Designing composite applications: Writing an Eclipse component for IBM Lotus Notes by Craig Wolpert and Jo Grant from IBM @ IBM developerWorks.
Sounds like a series coming up that you might want to check out if you’re new to Eclipse development.
developerWorks: Plug-in development 101, Part 1: The fundamentals
After reading the last installment in an article series on Notes 8 development on developerWorks I have to wonder how many articles they (developerWorks) need to publish on creating simple plug-ins, building features and publishing them using an update site. This is already extensively covered as part of the Eclipse development articles both on developerWorks and on eclipse.org/articles.
In my mind a good example of bringing something new to the table is the article on leveraging the current context in Notes 8 (Leveraging user context in the IBM Lotus Notes V8 sidebar and toolbar). That’s new. That’s something I wanna do. It still uses the first third configuring and setting up stuff but still it’s new.
Why not try some more concrete examples that actually cover some of the things that IBM bring to the table in Notes 8 / Sametime 7.5 / Expeditor or some of the areas that is going to cause problems? Suggestions could be:
- Using the components of Expeditor e.g. the message broker and the web services engine
- Building Notes UI’s using SWT components
- Making your SWT components look the ones supplied by IBM
- Communicating with the Notes application from your features/plug-ins
The above suggestions aren’t great but I’m dying to read articles on Notes 8/Sametime 7.5 that doesn’t spend the better half explaining the same ol’ concepts as have been explained so many times before…