[daisy] [JIRA] Updated: (DSY-477) Daisy Wiki configuration system

[Bruno Dumon (JIRA)]

     [ http://issues.cocoondev.org//browse/DSY-477?page=all ]

Bruno Dumon updated DSY-477:
----------------------------

    Fix Version: 2.3
                     (was: 2.2)

> Daisy Wiki configuration system
> -------------------------------
>
>          Key: DSY-477
>          URL: http://issues.cocoondev.org//browse/DSY-477
>      Project: Daisy
>         Type: Improvement
>   Components: Frontend - platform
>     Reporter: Bruno Dumon
>     Priority: Minor
>      Fix For: 2.3

>
> This issue serves as a place to collect ideas about requirements and implementation for a future configuration system for the Daisy Wiki.
> Background
> =========
> Currently the wiki has the following configuration mechanisms:
>  - Avalon component configuration (daisy.xconf/cocoon.xconf)
>  - the skinconf.xml for skins (XSLT).
> Often, things that fall outside these categories also need configuration information, some examples:
>  - extensions that want/need to make things configurable
>     (also think of deploying the same extension multiple times with different configurations)
>  - Wiki functionality which isn't necessarily a component, such as:
>        - config parameters for the document basket
>        - the default locale to be used by the Wiki
>        - the skin to use for the admin pages
>        - ...
> In some cases custom configuration mechanisms have been implemented:
>  - the external-include-rules.xml
>  - (not in wikidata) admin_locales.txt and locales.txt
> Requirements
> ===========
> Configuration parameters should be definiable:
>  - for the wiki as a whole
>  - specific for a site
>  - defaults specified on the level of the wiki, and overridable on the site level
> The skin configuration mechanism is currently an opaque blurb of XML made available to the XSLs. This is probably good enough and will not be changed. OTOH: it might make sense to have these things available to the templates as well? Or maybe skinconf should be a template that pulls things out of site/wiki config to make them available to the XSLs.
> Some things to consider when working out the design for this:
>  - reloading of config and config change notification
>  - structure of the configuration: flat property list of hierarchical, with attributes or not
>     => I'm very much in favour of an XML-like structure (even including mixed content)
>  - storage structure of config: one file or multiple files etc.
>  - performance considerations

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira