Changes between Version 1 and Version 2 of adeiInternals
- Timestamp:
- 07/16/09 18:02:32 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
adeiInternals
v1 v2 7 7 * Anything else... 8 8 9 This section describes how the additional data could be provided using ADEI Web Interface. The simplest approach is to provide a service generating an XML data, and XSLT stylesheet which would convert it to convert it into the HTML. Of course it is possible to generate directly XHTML, but using XML+XSLT approach it is easier to alter presentation form and establish some automation (the XML service could be used by 3rd party client applications). After the service is ready, the new ADEI module (an extra page in the upper menu) should be created and registered in configuration. 10 9 This section describes how the additional data could be provided using ADEI Web Interface. The simplest approach is to provide a service generating an XML data, and XSLT stylesheet which would convert it to HTML. Of course it is possible to generate directly XHTML, but with XML+XSLT approach it is easier to alter presentation form and establish some automation (the XML service could be used by 3rd party client applications). After the service is ready, the new ADEI module (an extra page in the upper menu) should be created and registered in configuration. 11 10 12 11 So, the following steps should be taken to setup 13 * Create a service, see description [wiki:adeiNewService here] 14 * Create a module, see description [wiki:adeiNewModule here] 12 * Create a service and put it in the ''services/'' subdirectory (see description [wiki:adeiNewService here]) 13 * Create a module and put it in the 'modules/'' directory (see description [wiki:adeiNewModule here]) 14 * Create a XSLT stylesheet which accepts produced XML and generates HTML to be displayed and put it in the ''xslt/'' sub folder. 15 * Optionally, if additional parameters, like ''target'' for multi-task services, should be passed to the service, special update service should be created in ''services/update/''directory ([wiki:adeiNewModule see details]) 16 * The module should be registered in ''$MODULES'' variable in the configuration file ''config.php''. Be careful, some of the global configuration options specified in the config.php located in the root folder of ADEI installation may be overriden in setups by setup-specific configuration file.
