Power Programming: Examining and Manipulating IBM Lotus Domino Application Designs (AD 204)
Tags: Lotusphere2006
Just been to this - very good - session, presented by Andre Guirard and Mark Jourdain. As expected we were exposed to some code in this session together with some useful best practices and architectural slides and comments. And it was fun to listen to also.
I have used DXL to modify Domino design elements only rarely and always "manually" (so exporting, editing with notepad and re-importing). That's possible, but only necessary if you have to do some very ugly things (like changing names in a form with > 100 fields with similar names - which is normally no good design to begin with).
.
The beauty of the approaches presented is to use the Lotus Domino built-in functions - starting with the LotusScript classes to access design elements, but getting much more flexible when using the XML Tools like Exporters, DOM and SAX. Doing this the end users - without the Designer client and even without Designer access rights can change design elements on the fly by wizards built by the developer.
And the best thing is, that the demo database shown will be available in the sandbox on LDD (aka notes.net). The script libraries even contain some very cool utility functions, e.g. a subroutine to de-code BAS64 encoded elements (like image resources) to binary: it will create a MIME entity (which supports BASE64 encoding) and just call a method to get the decoded contents.
Very cool stuff, to be used in my next projects.
Just been to this - very good - session, presented by Andre Guirard and Mark Jourdain. As expected we were exposed to some code in this session together with some useful best practices and architectural slides and comments. And it was fun to listen to also.
I have used DXL to modify Domino design elements only rarely and always "manually" (so exporting, editing with notepad and re-importing). That's possible, but only necessary if you have to do some very ugly things (like changing names in a form with > 100 fields with similar names - which is normally no good design to begin with).
.
The beauty of the approaches presented is to use the Lotus Domino built-in functions - starting with the LotusScript classes to access design elements, but getting much more flexible when using the XML Tools like Exporters, DOM and SAX. Doing this the end users - without the Designer client and even without Designer access rights can change design elements on the fly by wizards built by the developer.
And the best thing is, that the demo database shown will be available in the sandbox on LDD (aka notes.net). The script libraries even contain some very cool utility functions, e.g. a subroutine to de-code BAS64 encoded elements (like image resources) to binary: it will create a MIME entity (which supports BASE64 encoding) and just call a method to get the decoded contents.
Very cool stuff, to be used in my next projects.
