|
openslice actually consists of two template databases - opensliceSource and openslice. Generally speaking, most developers will never need to use opensliceSource, but it is provided to allow complete and open access to the source code. Most of the LotusScript utilities are pre-compiled and included in openslice via the use of lss files. Why? In a word - performance. As there is a significant amount of code included in openslice (around 350 functions in 24 script libraries), using lss files helps Notes to carry this code without the extra overhead of compiling at run-time. This helps to provide these functions without a noticeable decline in performance.
Unfortunately, one of the limitations to implementing code via lss files is the inability to step the debugger through these functions. Usually, you wouldn't need to debug into the openslice functions, but just in case something really weird is happening, or a bug (surely not!?) is found, then the opensliceSource or opensliceHelp database can be used to see the function source code to help you work out what is happening.
Open Slice Source
The Open Slice Source template database is the home for all the Open Slice design elements - forms, views, and the Open Slice lss script libraries. This template will be updated by liquidtoast where changes are required to any $sys elements. It is also where the original version of any $app elements can be found.
Open Slice Source also contains samples of every standard document type, provided as examples of what each form might look like. The Source template also includes all the necessary documents required to provide a minimum working copy of Open Slice (keyword and configuration documents).
Open Slice
From the Open Slice Source library we create the actual Open Slice template from which most developers will create their own applications. The Open Slice template contains only the standard design elements (forms, view etc), as well as the three default script libraries. The Open Slice template also includes all the default keyword and configuration documents which must exist in an application for Open Slice to work correctly.
NOTE: Developers making use of Open Slice in applications, who want to be able to continue to receive updates and bug fixes should not make any changes to the Open Slice databases, as any of these changes will be lost whenever new versions of Open Slice are released. Corporate Templates (see below) should be used to customise Open Slice.
Open Slice Help
The Open Slice Help database is the third database provided by liquidtoast. The Help Database (which you are reading now) contains a full listing (including segments of source code) of all available classes/subs/functions provided in Open Slice, as well as instructional help on how to utilise the Open Slice components.
Corporate Templates
A corporate template can be used as an intermediary design between the Open Slice template and any corporate applications, and would mostly be used as a mechanism for distributing corporate wide user interfaces, or corporate specific code which needs to reside in each corporate application. For example, a corporate template would be based on (and directly inherit it's design from) the Open Slice template, and would be the template used to create/update corporate applications. Any standard corporate elements (prefixed with a "#" (eg #XXsubHeaderDefault) could be included in this template, along with any standard documents (eg a Database Link document to the internal corporate directory or Domino Directory). |