The Integration Story started in 1994, with the first ways to combine Lotus Notes and Lotus Ami Pro to create custom applications. In 2011, the Integration story is still going strong. This session will start with the basics and ramp up in skill and capabilities. We will show how to integrate Lotus Notes, Lotus Domino, XPages, and LotusLive applications with the tools on your user's machines: Microsoft Office, Microsoft .NET custom applications, OpenOffice.org , LibreOffice, Lotus Symphony, and more. We will look how the ODF and OOXML standards are changing the integration story and how they will impact you. You will walk out of the session with lots of sample code and extending your own integration story! MWLUG 2011: The Never Ending Integration Story View more presentations from John Head
Archive for LotusScript
MWLUG 2011: The Never Ending Integration Story: How to Integrate Your Lotus Notes, Domino, and LotusLive applications with Microsoft Office, .NET, and Lotus SymphonyAugust 26 2011
@IamLUG 2011 - The Never Ending Integration Story: How to Integrate Your Lotus Notes, Domino, and LotusLive applications with Microsoft Office, .NET, and Lotus SymphonyAugust 3 2011
This is the integration session I gave at IamLUG 2011 IamLUG 2011: The Never Ending Integration Story: How to Integrate Your Lotus Notes, Domino, and LotusLive applications with Microsoft Office, .NET, and Lotus SymphonyView more presentations from John Head. "The Integration Story started in 1994, with the first ways to combine Lotus Notes and Lotus Ami Pro to create custom applications. In 2011, the Integration story is still going strong. This session will start with the basics and ramp up in skill and capabilities. We will show how to integrate Lotus Notes, Lotus Domino, XPages, and LotusLive applications with the tools on your user’s machines: Microsoft Office, Microsoft .NET custom applications, OpenOffice.org, LibreOffice, Lotus Symphony, and more. We will look how the ODF and OOXML standards are changing the integration story and how they will impact you. You will walk out of the session with lots of sample code and extending your own integration story!"
JMP208 The Never Ending Integration Story: How to Integrate Your Lotus Notes, Domino, and LotusLive applications with Microsoft Office, .NET, and Lotus SymphonyJanuary 30 2011
JMP208 The Never Ending Integration Story: How to Integrate Your Lotus Notes, Domino, and LotusLive applications with Microsoft Office, .NET, and Lotus SymphonyView more presentations from John Head. Downloads coming shortly
I got an email from good friend Kenneth Haggman, one of the people behind the awesome Notes & Domino developers tool NotesHound. I have used it for years and written about it a couple times. Kenneth wrote me to tell me that individual developers can now download NotesHound for free! Look at all these tools: If you are doing any form of Notes & Domino development, you owe it to yourself to get a free copy of NotesHound right now. And if you love it as much as I do and can use it inside your organization - get yourself a corporate license.
So how does one tell if the APIs in Lotus Symphony 3 have been updated? Compare to the previous version: Lotus Symphony Presentations 220.127.116.11: Lotus Symphony Presentations 3.0.0 Much nicer :)
Here is a great tip for anyone working with mail merge in Lotus Symphony Documents 1.3 using the LotusScript API. One of the first things people want to do with automating mail merge is to automate just enough so the user can write a form letter without having to automate the whole process. Just get the selected documents, map the fields, and open the mail merge wizard/process. We do this pretty easily with Microsoft Word Mail Merge and the Mail Merge Wizard. Until now, this was not possible with Lotus Symphony Documents. The key is the ShowMailMergeSideBar function on the Mail Merge object. We (PSC) was using the document text as stated, and it was causing issues. The Sidebar would come up in strange ways and the completed merge would not have the field data. Totally strange. So before I reveal the solution, let's look at the documentation for the method: Method ShowMailMergeSideBar This method opens mail merge sidebar in Lotus Symphony. Be sure that the document is visible, othe
One of my favorite slides at Lotusphere 2010 was in "AD207 IBM Lotus Symphony Technical Overview" when they were comparing the code needed by both UNO and LotusScript to create a table. Let's look at this in detail: Here is a screenshot of the table to be created: The code required in UNO to create this table: Object desktop = factory.createInstance("com.sun.star.frame.Desktop"); XComponentLoader loader = ( XComponentLoader ) UnoRuntime.queryInterface(XComponentLoader.class, desktop); PropertyValue args = new PropertyValue; args = new PropertyValue(); args.Name = "Hidden"; args.Value = Boolean.FALSE; XComponent component = loader.loadComponentFromURL("private:factory/swriter", "_blank", 0, args); XTextDocument document = ( XTextDocument ) UnoRuntime.queryInterface(XTextDocument.class, component); XMultiServiceFactory docfactory = ( XMultiServiceFactory ) UnoRuntime.queryInterface(XMultiServiceFactory.class, document); Object ob
Tri State Lug 2009 - Integration And Coexistence SessionView more documents from John Head. Demo database available for download here
To get started with the Lotus Symphony LotusScript API, let's write our first code sample - the ever popular "Hello World" sample. To start, create a new button in a Rich Text field in a document. Change the code selection drop-down to "LotusScript" and enter the (Options) section. To begin, every time you want to use the Lotus Symphony LotusScript API, you need to call the LSX. You do that with the following code: %INCLUDE "symphonylsx.lss" This tells LotusScript to load the Symphony LSX. It also enables LotusScript to do cool things like provide type-ahead for the custom LSX - even in buttons or in actions on a form or view. Now let's write some code. Go into the Click section of the button and enter the following: Dim application As SymphonyApplication Set application = New SymphonyApplication To begin, we are creating an application variable and setting it to the SymphonyApplication class. We then set that variable to a new instance of that c
As you might have heard, Notes 8.5.1 includes a new API for Lotus Symphony - in native LotusScript. It works with all three of the Symphony applications, but the Lotus Symphony Presentations API is very bare in this release. I will cover more about each Symphony application in individual blog entries to follow, but I wanted to give an overview of the LotusScript API first. To begin working with the Lotus Symphony LotusScript API, you need to download the file lotus_symphony851_win_CZ5SZEN.exe. You can get this from both PartnerWorld or Passport Advantage. There is also a version of the file for Linux. Once you have downloaded and unzipped the Toolkit, you will see the following: Here is a description of each folder: docs - contains two pdf's: "IBM Lotus Symphony Developer's Guide.pdf" which is all about working with the Symphony API for modifying the menu, sidebar, and menu bar and is targeted at Expeditor developers and "Symphony Developer's Guide for Notes.pdf" which is for No
One of the features of Notes 8.5.1 that is getting buried under the local XPages and other killer features is the new API that allows Notes developers to write LotusScript and Java to automate Lotus Symphony. No longer does one need to learn the UNO hacks we have been using for the past couple years with OpenOffice.org and the past 18 months with Lotus Symphony. I am queuing up a bunch of articles on the new Lotus Symphony API for this week and next. Here is a quick rundown on them: 1. Introduction to the Lotus Symphony LotusScript API 2. Lotus Symphony Documents "Hello World" in LotusScript 3. Lotus Symphony Spreadsheets "Hello World" in LotusScript 4. Lotus Symphony Presentations "Hello World" in LotusScript (and why it doesn't work) 5. Lotus Symphony Documents and Mail Merge via LotusScript 6. Using the Symphony LotusScript API in a Document Action 7. Using the Symphony LotusScript API in a View Action 8. Building Cha
Here are the slides from my session at UKLUG 2009 in Edinburgh, Scotland, UK last week. Uklug 2009 Lotus SymphonyView more documents from John Head. Demo databases can be downloaded here
Ed Brill and Stuart McIntyre both covered this video earlier this week, which reveals the following new features in Lotus Symphony 1.3: Support for reading Office 2007 file formats Support for widgets and Live Text Support for network connection hyperlinks for URI protocols New clip art Enhanced animation effects in Symphony Presentations Improved DataPilot functionality in Symphony Spreadsheets The ability to create and print envelopes, and enhancements to outline-level numbering styles in Symphony Documents One of the things that will not be included with Lotus Symphony 1.3 is the new LSX Toolkit which will bring LotusScript and Java abstraction to the UNO API that Lotus Symphony (and of course OpenOffice.org) use. This will allow Notes developers to automate Symphony without having to go thru COM or OLE abstraction. The toolkit will be delivered with Notes 8.5.1 later this year, which will also include Symphony 1.3. Just a bit longer to wait for that feature. I have had a c
Symphony Thursday: Developer 101 1. Introduction to UNO Development and Documents/Writer "Hello World" 2. Spreadsheets"Hello World" 3. Presentations "Hello World" Last time, I covered the basics of UNO Development and walked you thru a "Hello World" application for OpenOffice.org Writer and Lotus Symphony Presentations. This blog entry will cover how any file type - documents, spreadsheets, or presentations, can be saved as a PDF. How Lotus Symphony Saves Lotus Symphony and OpenOffice.org have a built in command that save the current file. If we take the Lotus Symphony Presentations document we generated in the Presentations: "Hello World", we would do the following to save the file Call Presentation.storeToURL("file:///C:/symphonythursdaypresentation.odp", args) The storeToURL method has two parameters. The first is the complete path of where you want to save the presentation. Just as when we were creating the presentation, we have to use a URL format for t
Any other suggestions?
So IBM thinks it is important that all the LotusScript Developers transition to Java ... where is IBM Education?September 8 2008
So Bob Balaban did some blogging this weekend on the transition of LotusScript developers to Java and Nathan Freeman blogged about some nuggets around Java and the Notes UI and Front End classes. While the complete message of what is coming is not anything that those of us in the Design Partner can communicate (I just wish IBM would blog/discuss this publically). The path that will come to a head with the final release of 8.5 (that is a guess, it could be 8.5.1 or later) should not surprise anyone and is a long time coming. It should put the Java and LotusScript developers on equal footing. The problem here is that while IBM has gone out of it's way to preach why Java is so great AND that LotusScript is not going away, IBM has not giving us the tools to educate the typical LotusScript developer. Why has IBM Education not come out with courses and materials to help the LotusScript developer, who typically has no hard-core development background, move to Java? This has to come from IBM
(Sorry for the title only post before, was me setting blogs in the future for writing, and then didn't get to it ... all comments deleted) So this should be a fun topic. I would like to throw out this topic: Does Lotus Symphony really need LotusScript support? And by support I mean native classes. My answer right now is No. Here is why. First, Lotus Symphony already supports the UNO API. For example, you can use the following LotusScript to put text into Lotus Symphony Documents: Set SM=CreateObject("com.sun.star.ServiceManager") Set Desktop=SM.createInstance("com.sun.star.frame.Desktop") Set WriterApplication=Desktop.loadComponentFromURL("private:factory/swriter","_blank",0,args) Set WriterText=WriterApplication.getText() Set Cursor=WriterText.createTextCursor() Call WriterText.insertString(Cursor,"Hello World!",False) Those who have been to my integration presentations at a conference will notice that this is the same code to automate OpenOffice.org. The UNO API support is a car
BP218 IBM Lotus Notes 8 and IBM Lotus Expeditor Customization for LotusScript Developers Speakers: John Head, Alex Kassabov SW Pelican - Tuesday 10:00am - 11:00am So you are a LotusScript developer. You can make forms and agents sing. But with Lotus Notes 8, you want to extend your applications into Composite Applications, the sidebar, and the menus. You notice this is all done in Eclipse.org, IBM Lotus Expeditor, and Java. What is a LotusScript developer to do? You come to this session. You will learn how to get started with these new tools, see demos and take home samples on how to begin integrating today. We will talk about why Composite Applications should excite you. We will walk you thru building your first Sidebar application. And, we will show you how to interact with the Lotus Notes 8 menus. A few surprizes will give you the tools and knowledge on how to make your applications look like they belong in Lotus Notes 8! | View | Upload your own Download Updated Slides here