tag and its contents. Determining the proper location for the %BODY% tag (the most important O4W tag) may take some trial and error; in general, it should be centrally located to the page, and be able to dynamically shrink and grow (and have the other elements of the web page shrink and grow around it). The %MENU% tag (or its variants) may go in a different section of the html, or directly before the %BODY%. The %FOOTER% tag can be placed directly after the %BODY%, or in another html section as well. Note that O4W will generate its own html "form" tags, so no O4W tags should be located within an html "form". However, the %BODY% and %FOOTER% (and any %MENU% tags) _should_ be located within an existing html "body" tag. === O4W Template Settings === Once the html document has been modified to include the O4W tags, it must be placed in the appropriate location for O4W use. When using the O4W APIs, the template document can be located in any operating system folder by specifying the full path to the document; the template can also be placed in any OpenInsight table, by specifying the template name as "<tablename> <templateID>" (for example, "SYSLISTS THISTEMPLATE"). When using the O4W wizard tools, the template should be placed in the "template directory" location defined in the O4W Configuration table. The O4W Configuration record defines not only the location itself, but also the type of template location (either operating system folder or OpenInsight table). By default, the template directory is the folder named "templates" under the O4W directory, located in the OpenInsight folder (and the type of template location is "operating system folder"). By placing your template in the correct directory, it will be available to select during the O4W wizard definition processes. During the O4W wizard definition processes, it is also possible to select the "default" template. The specification of which template should be used as the default is also done via an O4W Configuration record. === Additional Templates === If O4W determines that a request is coming from a mobile browser, it will search for a "mobile-ready" version of the previously specified template. This mobile-ready version may use fewer images, have smaller borders, etc. For O4W to find this template automatically, it needs to be named "m_<templatename>" in the same location as the regular template (for example, if a template named "abc_co.html" is located in the O4W\templates directory, the mobile version should be named "m_abc_co.html" in the same directory). During the O4W Report definition process, you are able to define an additional template to use if the specified report is invoked as a "popup". Since an on-screen popup has less available screen space, and is not truly designed as a 'stand-alone' web page, you may wish to define a template with fewer (or no) images, etc., in this case. Note that a template named "blank", containing no formatting and only the minimal O4W tags, is available for these (or other) situations. === Example === Any web page can be used as the "source" for a template. In this case, we will use the html that generates the Revelation web page: ---------- <code> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <title>Revelation Software: Home

Home

Looking for the easiest way to navigate the site? Here is the