[daisy] [JIRA] Commented: (DSY-455) allow to define 'available document-types' in the siteconf

[Marc Portier (JIRA)]

    [ http://issues.cocoondev.org//browse/DSY-455?page=comments#action_13213 ] 

Marc Portier commented on DSY-455:
----------------------------------

Spent some time to see how this could be done / which files are affected.

affected files
--------------------
./applications/daisywiki/xmlschema-bindings/src/siteconf.xsd
    - needs to specify the new xml elements to hold this new config

./applications/daisywiki/frontend/src/java/org/outerj/daisy/frontend/components/siteconf/SiteConfImpl.java
    - needs to hold the filtering config, and probably also an active method that uses
      that data to 'vote/veto' on  the acceptance of a certain document-type in the list
      (and thus need to change the SiteConf interface)

./applications/daisywiki/frontend/src/java/org/outerj/daisy/frontend/components/siteconf/SitesManagerImpl.java
    - needs to parse the new config and pass that correctly into initalization of the SiteConfImpl class 

./applications/daisywiki/frontend/src/java/org/outerj/daisy/frontend/DocumentTypeSelectionApple.java
    - will need to change its 'getFilteredDocumentTypes()' to allow the SiteConf object to accept/reject 
      the actual document-types it is yielding today

and also involved, but probably no changes here: 
  ./applications/daisywiki/frontend/src/cocoon/webapp/daisy/resources/skins/default/xslt/select_doctype.xsl
  ./applications/daisywiki/frontend/src/cocoon/webapp/daisy/resources/xml/doctypes_list.xml


still needed
------------------
closure on the actual syntax and some suggestion on how this inclusion/exclusion patterns should be working
(anyone knowing some reusable wildcard-pattern implementation?)

> allow to define 'available document-types' in the siteconf
> ----------------------------------------------------------
>
>          Key: DSY-455
>          URL: http://issues.cocoondev.org//browse/DSY-455
>      Project: Daisy
>         Type: New Feature
>     Reporter: Marc Portier
>     Priority: Minor
>      Fix For: 2.1

>
> Currently the siteconf.xml [1] allows to specify the default document-type:
>     <defaultDocumentType>SimpleDocument</defaultDocumentType>
> this puts the most-likely to be created document for that site on top of the list.
> In more general terms however the repository might contain a whole lot of document-types that really should be totally hidden from the list of available document-types within the context of a certain site.
> For this filtering to occur, I would suggest to define the complete list of available document-types in the siteconf.xml file.
> Something like
>   <availableDocumentTypes>
>     <documentType>OneType</documentType>
>     <documentType>AnotherType</documentType>
>     <documentType>AFinalType</documentType>
>   </availableDocumentTypes>
> This should define the ordered list as is, to be presented when users take the menu option 'new document'
> [1] http://cocoondev.org/daisydocs-2_0/374-cd/23-cd.html

-- 
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