[daisy] [JIRA] Updated: (DSY-158) Allow customisation of the DaisyHTML editor

[Bruno Dumon (JIRA)]

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

Bruno Dumon updated DSY-158:
----------------------------

      Component: Frontend - doc editing - HTML
                 Repository - schema
    Description: 
Som discussion about customising the DaisyWiki editor have been had on the mailing list:

>>For the turning off: there's no special provisions for that, other then
>>> > hacking the code. The idea has been floating around to have
>>> > per-part-type configuration of the HTML editor, with different sets of
>>> > functionality enabled.
>
>> 
>> Can you point me at the right part of the code to hack?


Sure, there are two parts to it:

1. Altering the configuration of the HTML cleaner to change what HTML is
allowed

See the file htmlcleaner.xml (in the binary dist somewhere in the
webapp, in the source tree at
applications/daisywiki/frontend/src/cocoon/webapp/daisy/resources/conf/htmlcleaner.xml)

As also noted in there, some element declarations cannot be removed or
won't have influence if removed, it might be that strong and em are
among them (though I'd need to check the code).

2. Altering the HTML area configuration to match the HTML cleaner
configuration.

See the initEditor function in daisy_edit.js. Among other things, you'll
see it's very easy to remove certain buttons from the toolbar.



  was:
Som discussion about customising the DaisyWiki editor have been had on the mailing list:

>>For the turning off: there's no special provisions for that, other then
>>> > hacking the code. The idea has been floating around to have
>>> > per-part-type configuration of the HTML editor, with different sets of
>>> > functionality enabled.
>
>> 
>> Can you point me at the right part of the code to hack?


Sure, there are two parts to it:

1. Altering the configuration of the HTML cleaner to change what HTML is
allowed

See the file htmlcleaner.xml (in the binary dist somewhere in the
webapp, in the source tree at
applications/daisywiki/frontend/src/cocoon/webapp/daisy/resources/conf/htmlcleaner.xml)

As also noted in there, some element declarations cannot be removed or
won't have influence if removed, it might be that strong and em are
among them (though I'd need to check the code).

2. Altering the HTML area configuration to match the HTML cleaner
configuration.

See the initEditor function in daisy_edit.js. Among other things, you'll
see it's very easy to remove certain buttons from the toolbar.



    Environment: 

I'm assigning this to the component "repository schema" too since specifying the sort of HTML allowed in a part might be made configurable on that level. One reason to do so might be so that non-Daisy Wiki clients also know about this. As a contra, this makes the repository more related to the Daisy-HTML format.

> Allow customisation of the DaisyHTML editor
> -------------------------------------------
>
>          Key: DSY-158
>          URL: http://issues.cocoondev.org//browse/DSY-158
>      Project: Daisy
>         Type: New Feature
>   Components: Repository - schema, Frontend - doc editing - HTML
>     Reporter: Ross Gardler
>     Priority: Minor
>  Attachments: 1138.html
>
> Som discussion about customising the DaisyWiki editor have been had on the mailing list:
> >>For the turning off: there's no special provisions for that, other then
> >>> > hacking the code. The idea has been floating around to have
> >>> > per-part-type configuration of the HTML editor, with different sets of
> >>> > functionality enabled.
> >
> >> 
> >> Can you point me at the right part of the code to hack?
> Sure, there are two parts to it:
> 1. Altering the configuration of the HTML cleaner to change what HTML is
> allowed
> See the file htmlcleaner.xml (in the binary dist somewhere in the
> webapp, in the source tree at
> applications/daisywiki/frontend/src/cocoon/webapp/daisy/resources/conf/htmlcleaner.xml)
> As also noted in there, some element declarations cannot be removed or
> won't have influence if removed, it might be that strong and em are
> among them (though I'd need to check the code).
> 2. Altering the HTML area configuration to match the HTML cleaner
> configuration.
> See the initEditor function in daisy_edit.js. Among other things, you'll
> see it's very easy to remove certain buttons from the toolbar.

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