Presentation from Norwegian Lotus User Group (2 hour edition)

1. LSBG Vårseminar, maj 2011 Larvik, Norge Plug yourself in and your applications will never be the same! (An introduction to plugin development for Lotus Notes, Domino and Sametime)

3. Design Partner for Domino NEXT and Lotus Connections 3.0

4. Active blogger: lekkimworld.com

5. Speaker at Lotusphere

6. Articles for THE VIEW

7. E-mail: mh@intravision.dk

8. .com/lekkim

10. It's about extending the UI in Notes, Sametime and Symphony

11. It's about delivering a UI capable of doing stuff you cannot do in ”traditional” Notes

12. It's about developing custom components for the XPages Extensibility Library

13. It's about DOTS (previously JAVADDIN) and OSGi on the Lotus Domino Server

16. Well Adopted

17. Multi-platform

19. Web Applications

20. Database Integrations

21. etc....

22. What's possible with plugins Torsdag, sal 1, 11:20-12:00 - Ta samarbeid og planlegging til neste nivå

24. ...or use the bit.ly link >> http://bit.ly/pluginredwiki

27. One button reads contacts from names.nsf

29. Create document

30. Set subject

32. Create an update site with the feature

33. Create a widget for the feature from the update site

35. Installing Lotus Expeditor Toolkit

36. Plugin Development Basics

37. Building UI's with SWT and JFace

38. Jobs, Jobs, Jobs

39. Logging

40. APIs

41. Debugging

42. Deployment

43. Resources / Q&A

44. Eclipse architecture Workbench JFace SWT Core Extension Point Framework Service Framework Rich Client Platform Plug-in Plug-in Extension Pt. Plug-in Extension Point Extension Point Extension Point A software component in Eclipse Extension Point declares contract to extend plug-in functionality Extension code extends this functionality RCP allows you to build GUI apps on multiple OS SWT provides uniform UI API across multiple OS that calls OS UI API for native look and feel JFace provides components to make it easier to write a GUI e.g. wizards, preference pages, actions, dialogs Workbench is desktop UI and customizable Service Framework supports registration and lifecycle management of plug-ins

45. IBM Lotus Clients – built on Eclipse Sametime Expeditor Apps and Plug-ins (ISV + Customer) Notes Symphony Industry knowledge and experience ecosystem of partners open and extensible collaborative services Integrated applications Portal Browser Desktop Mobile Multiplatform support Scalability Security

46. Eclipse workbench

47. Notes workbench s

49. FREE! No charge to use the Expeditor toolkit

55. Browse to unziped update site

56. Select OK

58. Click Install...

60. Install all features

61. Restart

65. Run -> Run Configuration

66. Double Click Client Services

67. Give The Configuration A Name

68. Select Run

72. Run -> Run Configuration

73. Double Click Client Services

74. Give The Configuration A Name

75. Select Run

77. By themselves plugins may not do anything, but when you start combining plugins you can build very powerful applications

78. Examples: Eclipse, Notes, Sametime, Symphony Application Plugin

82. Files used for translation

83. Images

84. etc....

86. Select Plug-in Project

92. The arcane art of building UI's

96. Protection from OS Level Changes

97. Very responsive

98. Resulting UI looks like native platform applications

101. Image / Font Registries

102. Wizards

103. Viewers

104. Meet WindowBuilder! http://eclipse.org/windowbuilder/

106. Create view part class

107. Add com.ibm.rcp.ui.shelfView extension point

108. Use WindowBuilder to create UI

109. Try It Out!

111. Java and Eclipse contains a rich set of API's that you can use when developing plugins for Lotus clients

112. Knowing the API's available to you is crucial

114. Logging

115. Notes backend

116. Notes frontend

119. To tell the caller we're done we use callbacks or listeners

120. Harder to grasp

121. Used in AJAX – you request data in the background and once the data has been fetched you are told

123. Allows for easy background processing

124. Very simple to use

125. Allows scheduling of jobs (“run this code in 2 minutes”)

126. Allows weaving of jobs

127. Allows for listening to job status etc.

131. It's – surprise, surprise – called the “UI thread”

133. Attempts to access the UI (i.e. set the text of a label) outside the UI thread will fail with an exception

135. Using Job in code public void fireOnTheEmpire(int initDelay, final String jediName) { // create recurring job to poll web service new Job("Poll the Force!") { protected IStatus run(IProgressMonitor monitor) { // invoke endpoint using input String srvc = “http://moon5.tatooine.com/JediFinder”; WSFacade facade = new WSFacade(srvc); String result = facade.fire(jediName); // do something with the result ... // reschedule this job (in 5 mintues) this.schedule(5 * 60 * 1000); // return return Status.OK_STATUS; } }.schedule(initialDelay * 60 * 1000); } final

136. Using UIJob in code final List lstJedis = new List(parent, SWT.NONE); ... public void psssst(final String[] jedis) { // since we're called in a background process // use that UIJob we learned about to update the UI new UIJob("Load Jedis") { public IStatus runInUIThread(IProgressMonitor monitor) { // update UI for (String jedi : jedis) { lstJedis.add(jedi); } // return status return Status.OK_STATUS; } }.schedule(); }

137. Avoid Spinning Wheel of Death public void createPartControl(Composite parent) { final Label txt = new Label(parent, SWT.NONE); new UIJob("Indicate job starting") { public IStatus runInUIThread(IProgressMonitor monitor) { txt.setText("Turning star cruiser (" + new Date() + ")..."); // do long running task == BAD!! try { Thread.sleep(5000); } catch (Exception e) {} txt.setText("Done turning star cruiser (" + new Date() + ")..."); // reschedule and return this.schedule(5000); return Status.OK_STATUS; } }.schedule(5000); }

140. You perform some background operation (e.g. load data from a web service or similar)

142. We do it by nesting Job instances

143. Do it right! public void widgetSelected(SelectionEvent event) { list.add("Starting to run code (" + new Date() + ")...", 0); new Job("Long running job") { protected IStatus run(IProgressMonitor monitor) { downloadEntireGoogleSearchIndex(); // call back into UI to tell user we're done new UIJob("Update UI") { public IStatus runInUIThread(IProgressMonitor monitor) { list.add("Done running code (" + new Date() + ")...", 0); return Status.OK_STATUS; } }.schedule(); return Status.OK_STATUS; } }.schedule(); }

145. Add selection listener

146. Load data from the web

147. Once call is done update the UI

150. Logging – Example package com.example.demo1; public class MainViewPart extends ViewPart { private static final Logger logger = Logger.getLogger(MainViewPart.class .getPackage().getName()); public MainViewPart() { try { logger.info("Main view part instantiated"); String senateCount = this.countSenators(); if (logger.isLoggable(Level.FINEST)) { logger.finest("Found “ + senateCount + “ senators (" + this + “)”); } } catch (Throwable t) { logger.severe(“There was a disturbance in the Force!”, t); } } }

154. Log the current sunrise and sunset

155. Enable logging

157. Basic usage is almost the same as you know and love

160. DO use the Job API and the supplied NotesSessionJob

161. Notes backend API in code new NotesSessionJob("Access Notes data") { public IStatus runInNotesThread(Session session, IProgressMonitor monitor) throws NotesException { // print username System.out.println(session.getDatabase(null, “names.nsf”).getTitle()); // return return Status.OK_STATUS; } }.schedule();

163. Bridges a MAJOR gap in the Notes product as it gives us access to the Notes UI from Java

165. Supported from Notes 8.5.1

167. Example project available from OpenNTF.org (“Java UI API Exerciser”)

170. Listen for selection events and view entries

172. Access to backend document

173. Edit / Field / Modify listeners

176. Place the email addresses of the user's contacts in the list box

177. Use the composeDocument API to compose an email to selected contact with data

182. Set breakpoints

183. Inspecting variables

184. The console, logging levels

186. Creating an update site to hold the feature

187. Installing the feature into the clients either manually or using a widget descriptor Feature Plug-in Plug-in . . . Feature Plug-in Plug-in . . . Update Site . . .

189. Create an update site

190. Create an update site NSF

191. Add our feature to the update site NSF

192. Create a widget for our feature

193. Add it to a widget catalog

194. Watch a video at: http://bit.ly/h4pjMb

195. DOTS (used to be JAVADDIN)

196. XPages Extensibility Library ” A new project has been created which contains a simple sample for how to to develop a 'native' XPages control via the Java extensibility API. This control can be deployed globally as an OSGi bundle/plugin to Lotus Domino and Lotus Notes/Domino Designer and then used in all NSFs without having to put the code in all NSFs redundantely. The new control shows up in the palette in Designer as other out of the box controls.”

198. HIGHLY recommended article on the Job API >> http://www.eclipse.org/articles/Article-Concurrency/jobs-api.html

199. Eclipse articles >> http://www.eclipse.org/articles

200. Eclipse WindowBuilder >> http://www.eclipse.org/windowbuilder

202. How do I?

203. Doesn't that mean?

204. Give it to me! :-)