overview applications limitations structure diagram files details
The following sample application has been created to provide basic examples of catalogue and contact template usage. The following actions are demonstrated:
Each of the actions above (with the exception of linking) is supported by a separate pattern page as shown in the diagram below.
This example application is applicable to all sites utilising the functionality provided by the catalogue and contact templates.
There are no limitations of note.
| Application |
|---|
|
|
|
Application |
|
|---|---|
| 1. index.html | HTML page that comprises of 2 HTML frames, sidebar.rhtm and welcome.html. |
| 2. welcome.html | This is the main right-hand-side target frame for the index.html introduction page. This simply displays a default welcome message until an item is selected from the left-hand menu. |
| 3. sidebar.rhtm | This is the menu for the sample application. |
| 4. editcategories.rhtm | This pattern page manages category information. |
| 5. edititems.rhtm | This pattern page manages item information. |
| 6. editcontainers.rhtm | This pattern page manages container information. |
| 7. editcommunities.rhtm | This pattern page manages community information. |
| 8. editou.rhtm | This pattern page manages OU information. |
| 9. editindividual.rhtm | This pattern page manages individuals' information. |
| 10. common.inc | This file is included by the most of the pattern pages which then make use of global parameters. |
| 11. clientside.js | This is a client-side javascript include file. This is used to pre-load images to speed-up mouse-over events. |
Each area of functionality supplied by this sample application is initiated from a menu structure on the left-hand side of the starting index page. This menu remains constant throughout the application.
The key to understanding how these examples work is to know that each pattern page will re-call itself as required with different parameters. These different parameters will trigger a different action/output by the pattern page. This therefore neatly provides associated functionality all from the same web page. To support this dynamic build requirement, each pattern page holds the entire set of functions required to fulfil the full range of actions it supplies. The appropriate functions are then brought into action by a list of 'if' statements working from the parameters supplied by the page call.
