All of the program code and information presented in the OpenNTF.org Code Bin are provided "as-is", and should be used at your own risk. OpenNTF.org make no express or implied warranty about anything in the Code Bin, and OpenNTF.org will not be responsible or liable for any damage caused by the use or misuse of anything from this site. OpenNTF.org makes no guarantees about anything. Please thoroughly test all of the knowledge and code you find here before you attempt to use them in your production environment.

Domino Ajax Engine

Version 0.0.2

Gavin Luscombe (gavin_luscombe@hotmail.com)

This code is licensed under the Lesser GNU (LGPL) open source license version 2.1.

This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.

http://www.gnu.org/licenses/lgpl.html

An example of extending the Ext framework (http://extjs.com) to render Domino views/outlines.

What's New ?:
0.0.2 - Implemented workaround for issue with DXL export for action bar
0.0.1 - First Release

Credits
• Credit to Jack Ratcliff and Rich Waters for the inspiration and some of the code used within. Also credit to authors of any code I may have borrowed from forums such as notes.net and openntf.org - this is an opportunity from me to give a little back.
• Thanks to Jerry Carter for a workaround to the DXL export truncation for the action bars

About
+ Implemented
• Views - flat & categorised
• Column Sorting on flat views - works on categorised views, but there are some know issues
• Column alignment - Ext currently does not separate header alignment from column alignment, so DAE uses the column alignment for rendering
• Preview pane - very basic implementation at present
• Opening of documents in new tabs - very basic implementation at present
• Outlines
• Icons
• Outline Hierarchy

- Not Implemented
• Action Bars - a lot of work needs to take place to make these functional
• Forms - documents currently render with their default forms, and titles do not appear on the tabs as documents are opened
• Column view switching
• Calendar views
• Categorised views with totals columns have known issues
• Custom Themes/Icons are not supported in this version - you can ignore them when setting up your application configuration documents
• Everything else

Prerequisites

• Domino 6.5 server or greater. (6.5 now required for Action Bars)
• Session-based authentication (Using Basic Authentication may lead to issues, or unwanted login prompts).
• Template signing ID that can run restricted operations.
• Browser supported by the Ext framework (Tested on IE 7 and Firefox 2.0.0.4 - may work on others).
• Ext library database deployed to server with read access for anonymous users.

Deployment

• Sign both the Ext Library template and DAE template with your own signing ID capable of running restricted operations.
• Create databases from the template and deploy to your server - I suggest placing both in the same directory.
• Set the ACL's of both databases appropriately:
• Ext Library
+---- Default - No Access
+---- Anonymous - Reader
• DAE
+---- Default - No Access
+---- Anonymous - No Access
• Important: Ensure that you select the [Admin] role in the ACL for the ID you want to configure the database with.
• Open the DAE database, and set up the configuration document to point to the Ext Library.
• Create Application documents to point to your databases - you can use "Copy database as link" and then use the paste icon to fill in some of the required information.
• Populate the name of the database's main outline and default view.
• Please Note: Databases must reside on the same server as the Ext library and DAE. (e.g. Each server needs its own instance of the Ext Library and DAE)
• Select an application from the view, and press the open button.
• If all is well, your web browser should launch and the application should appear using the Ext framework to render the user interface.

Disclaimer
• This framework has only been tested with a small number of application designs. It may or may not work for your applications. The full source code is being made available for you to extend and enhance as you see fit.