.Domino Framework

The 0.6 Beta of the .Domino Framework was published on OpenNTF on the weekend.  One of the last minute additions in this release is the abillity to access the XSLT/Skins feature of the .Domino Framework from within the Inspector tool.   The significance of this is that this the Inspector tool can be invoked against ANY Notes database.  So this tool now allows developers to apply XSLT transformations to design elements without the need to include any additional code in the applications themselves.  All the code (and XSLT) is held in the .Domino Framework database.

e.g. I frequently take on development for existing Notes applications in which the fonts used in forms an/views are inconsistent.  Using Inspector I can apply an XSLT from the .Domino Framework to all view/forms that change all fonts to Default Sans Serif saving me hours of manual (and boring) coding.

Did you ever want to lose the list of Notes IDs that have modified a particular set of Notes documents?  It would seem it is not possible to edit the existing contents of the $UpdatedBy using either @commands or LotusScript.  I assume this is a data integrity issue to ensure the contents of the edit history for any document cannot be manipulated.  This field can be modified (or removed) for design documents (see SuperNTF project at OpenNTF).  Interestingly, it is possible to edit or remove the contents of this field using XSLT.   I am not 100% sure this is a good thing to have, but it is possible!

The following is the XSLT code necessary to apply against documents exported from a Notes database as DXL before reimporting.....

I started work on extending the functionality of the .Domino Framework to provide the ability to "skin" an application for a Notes client based upon a style sheet.  The first challenge has been to develop an approach to take.  I had previously developed a solution for views that used the NotesDOMPaser.  Viewnify also uses this approach.  The downside to this is the lack of a standard way to define the "style".  Importing from a CSS was a possible options but what names should be applied to the classes/ids...

I decided to try XSLT.  It is an industry standard and the transformations could be defined as data rather than code.  Notes provides a way to transform DXL using an NotesXSLTTransformer class.  Using the Domino.reflections namespace I have extended the existing DominoDocummentCollectionDesign class to provide a Transform method.  This new method acts upon the selected design elements, exports them to DXL, applies an XSLT before importing the modified design elements back into teh database.  I also developed a debug option that exports the DXL to a file so it can be inspected.