Download CartoWeb Documentation

Structure
•
o
exportCsv: Csv export plugin, see Section 11.3, “CSV Export”
o
exportHtml: HTML export plugin, see Section 11.2, “HTML Export”
o
exportPdf: PDF export plugin, see Chapter 12, PDF Export
o
hello: test plugin
o
hilight: hilight plugin, see Section 9.3.2, “Hilight Configuration”
o
outline: redlining and annotations, see Chapter 10, Annotation and Redlining
po: PO templates files, used for gettext translation system, see Section 15.1.2,
“PO Templates”
•
projects: CartoWeb user projects dir, see Section 2.4, “Projects”
•
scripts: maintenance and administration scripts
•
server: CartoWeb server code files
•
server_conf: Cartoweb server-side configuration files, see Section 4.3, “Server
Configuration Files”
•
templates: CartoWeb Smarty templates files, see Chapter 16, Templating
•
templates_c: smarty templates cached files
•
tests: CartoWeb unit tests suite, mainly used for development and debug
purposes
•
www-data: writable and web accessible directories for generated files
o
icons: Generated icons
o
images: Mapserver images
o
mapinfo_cache: Client-side server configuration cache, see Section 5.6,
“Caches Configuration”
o
mapresult_cache: Client requests and associated server results cache, see
Section 5.6, “Caches Configuration”
o
pdf: Pdf generated cache files
o
soapxml_cache: Client SOAP XML requests and associated server results
cache, see Section 5.6, “Caches Configuration”
o
wsdl_cache: Client-side WSDL cache, see Section 5.6, “Caches
Configuration”
2.3. Plugins
Modularity is a key feature of CartoWeb. Its functionalities are packaged in logical
sets called plugins, that aim to be independent from each other, although some
dependencies cannot be totally avoided. Some plugins (core plugins) cannot be
disabled, while the other ones must be explicitly loaded in the server and/or client
configuration files.
32