Java Agents in Lotus Notes 8.5.1 Designer

I installed the updated Lotus 8.5.1 Client (Basic, Designer and Admin) a couple of weeks ago, and I really like it.  Designer loads quicker and also loads applications quicker - two time-intensive items in prior releases.

The thing I really love about this release is that it defaulted to the Eclipse perspective in Designer.  It felt like coming home again! 

One major impact when creating a Java agent is that the classes are actually listed in different files (which is really as it should be).  Previously, all the classes would be listed in a continuous view with separations between them. 

Here are a few of the features that I really like while coding Java in Lotus Notes:

• Context-sensitive auto-complete - this is great for a quick and sloppy typist like me.  With the case-sensitive nature of Java, this is so helpful.  Just start typing, and it will catch up with you and give you a list of choices.
• Self-Formatting - When you have typed some code, just press [ctrl][shift]-F and the braces and indents are all done perfectly.  To change the formatting rules, go to File | Preferences | Java | Code Style | Formatting.  All sorts of options are here for you to work with.
• Organizing Imports - Many best practices approaches suggest including only the imports you need.  For instance, you should not use "import java.util.*;" but "import java.util.TreeSet; import java.util.Iterator;" which indicates all the classes from other packages you are using.  Just press [ctrl][shift]-O, and presto! - the imports are all correct.
• Refactoring - Imagine that you want to change the name of a class or variable.  Just double-click on an occurrence of that name, right-click and select Refactor | Rename.  All of the references to this type or field name are changed throughout the code - amazing time-saver.  There are a lot of other refactoring options here too.
• Surround With - this is a tool with terrific time-saving potential.  Select some code, then Source | Surround With, and you have options to put the code in an if statement, a try-catch block and many other options.

One thing to remember if you are trying to modify the trigger or target of the agent - once the list of classes in the agent is open, focus on one of the classes, and the properties box at the bottom has all the options you could ever want.

For those who are used to the Domino Designer perspective, I encourage you to take the plunge and try the Eclipse perspective.  It will grow on you and you will wonder how you ever survived with the Designer perspective.  It's kind of like the R4.5 workspace - time to say goodbye so you can be ready for bigger and better things!