I am certainly not the best reference to be quoted regarding this topic and I would be glad if somebody seeing any incorrectness could point that out so I can amend these details for further reference.

Whereas I did had in mind that the way in which ViewParts are going to be added had been changing from Sametime 7.5 to version 7.5.1, I did not consider the same when I installed the new version yesterday night. When I opened my Eclipse development environment this afternoon I got welcomed with two information in the source code. (more…)

While I have seen quite interesting presentations about Lotus Notes and Domino 8 including the new possibilities to create composite applications I thought it might be worth to bring my Eclipse Java development environment up to the latest release. While about 140 bugs has been fixed with this new maintenance release the main intention behind the installation in my case had been the test whether or not extension elements for org.eclipse.ui are now properly displayed rather than referred to ‘Default’ as described in my previous comment. (more…)

I am currently trying to get my head around the new development possibilities of the Rich Client Platform provided with Sametime 7.5 following the instructions from the IBM Redbook® “Extending Sametime 7.5 – Building Plug-ins for Sametime“.
Unfortunately I already struggled on page 73 of the instructions where a new extension point to display a new action in the tools menu is going to be created. My Eclipse client did not show up the option to create a new actionSet extension element as shown in Figure 4-13 of the manual. Instead of it I could select to create a new Default element only. Same on page 74 where Default has been the only option to show up as well instead of a new menu or action item.
After some research in the Sametime Forum I discovered, that there might be some differences in the Plug-ins of Eclipse version 3.2 and more recent versions (I used version 3.2.1).
After downloading Eclipse version 3.2 and linking the 3.2 versions of the Eclipse plug-ins as described on page 52 of the manual everything worked as described even while working with Eclipse version 3.2.1.