• Eclipse-based editor for LotusScript - An Eclipse version of the LotusScript Editor is being released for LotusScript programmers. The LotusScript editor in Eclipse (LSEE) is an alternative to the classic Notes-based LotusScript editor. This editor takes advantage of the many editing features of Eclipse while retaining most of the classic features. Support for customizable code templates is supported along with information about template variables that you can use in code and comment templates, and a list of known issues. For all other information about this editor, see "Eclipse-based LotusScript editor" in the "Eclipse-based language interfaces" section of the Lotus Domino Designer Eclipse User Guide.
• Eclipse-based editor for Java - The Java interface for agents, libraries, and Web services now opens an Eclipse Java editor. This is the same editor that you open if you are in the Eclipse Java perspective and click File - New - Class or edit an existing Java file. Eclipse is a powerful Java tool and this improvement now provides a full-featured Java editor inside Domino Designer.
• Notes Client Java UI API - The Eclipse framework provides the ability to contribute to several locations of the Notes client. These locations include but are not limited to the global toolbar, sidebar panels, and menus on the top-level or right-click. The Notes Client Java UI API specifies the classes available for use when contributing to these areas of the client. For example, a plug-in could be written to contribute an item to the context menu of a Notes document. The custom code run when the user chooses the item would use the Notes Client Java UI API to know more about the document and change its properties. Generally, the APIs are similiar in scope and functionality to the front-end Lotuscript classes. The top-level classes implemented include:
  • NotesUIWorkspace - get a handle to the current document, prompt the user for input including the ability to select a database, open Notes elements in the user experience, and compose new documents.
  • NotesUIDocument - Information about document, ability to get and set fields, interact with document in a variety of ways
  • NotesUIView - Information about view
  In addition, access of the Notes back-end is available through the use of the lotus.domino classes (also available in notes.jar outside of this framework). The bridge between this package and the Eclipse-based framework is the NotesSessionJob class. Overriding NotesSessionJob allows code to be given a Session. Using this, the code can leverage the same back-end logic as it would have when using notes.jar directly or within a Java agent. Refer to the API Javadoc for more information.
• Domino Designer Extensibility APIs - This code drop makes available an extensibility API that lets your custom plugins know, whenever your selection changes, whether the new selection includes any Domino-based information and if so, what project (database) and what design elements are selected. With these APIs, you can follow the selection down to the design element level. For example, you can tell what form a user is editing (thought not what field is selected). In the newer, Eclipse-based editors, you may also be able to get more detailed information since these are derived from the standard UIs included with Eclipse. A lot of this Eclipse information is already public. The following is a list of the classes in the API:
  • DominoDesignerElement
  • DesignerDesignerElementSelection
  • Designer Exception
  • DesignerProject
  • DesignerResource
  Refer to the API Javadoc for more information.

LotusScript/COM/OLE classes

Lotus Domino Designer 8.5 adds the following:

• NotesRichTextDocLink.RemoveLinkage -- new method
• NotesDocument.GetRead method -- new method
• NotesDocumentCollection.StampAllMulti -- new method
• NotesView.ResortView method-- new method
• NotesViewEntry.GetRead method -- new method
• NotesViewEntryCollection.StampAllMulti -- new method

Lotus Domino Designer 8.5 adds the following:

• Document.getRead method -- new method
• DocumentCollection.clone -- new method
• DocumentCollection.contains -- new method
• DocumentCollection.intersect -- new method
• DocumentCollection.merge -- new method
• DocumentCollection.stampAllMulti -- new method
• DocumentCollection.subtract -- new method
• RichTextDocLink.removeLinkage -- new method
• Session.EffectiveUser -- new property
• Session.resetUserPassword -- new method
• View.resortView method -- new method
• ViewEntry.getRead method -- new method
• ViewEntryCollection.clone -- new method
• ViewEntryCollection.contains -- new method
• ViewEntryCollection.intersect -- new method
• ViewEntryCollection.markAllRead -- new method
• ViewEntryCollection.markAllUnread -- new method
• ViewEntryCollection.merge -- new method
• ViewEntryCollection.subtract -- new method
• ViewNavigator.markAllRead -- new method
• ViewNavigator.markAllUnread -- new method

Glossary