Forum OpenACS Development: Re: Supporting tinymce in xowiki

Collapse
9: Re: Supporting tinymce in xowiki (response to 8)
Posted by Dave Bauer on 01/25/08 09:56 PM
Hey everyone,

I got Tinymce 2.1.3 working on HEAD (can merge into 5.4 if people want).

BUT

Because tinymce requires a little different style of configuration, I really want to put the entire config object in a parameter, instead of just the plugins.

I can reuse the XinhaDefaultPlugins parameter and just stick the config into that.

Alternatively I cna adda new paremter

RichtextConfig or someting along those lines.

For now we have a reasonable deafault setup that seems to work ok.

I am checking in the code to HEAD using XinhaDefaultPlugins as the parameter for now.

Collapse
10: Re: Supporting tinymce in xowiki (response to 9)
Posted by Gustaf Neumann on 01/26/08 01:28 AM
If people want to switch between Xinha and tinymce, it looks as a bad idea to use the same parameter with different content for Xinha and TinyMCE. How about introducing a parameter TinyMCE_Config?
Collapse
11: Re: Supporting tinymce in xowiki (response to 10)
Posted by Don Baccus on 01/26/08 12:41 PM
I agree with Gustaf.
Collapse
12: Re: Supporting tinymce in xowiki (response to 9)
Posted by Emmanuelle Raffenne on 08/26/08 12:12 PM
Hi Dave,

I had a look at TinyMCE and I liked it a lot, nice work!. I had to tweak it a bit to make the "openacs" theme work on HEAD (committed) but couldn't make the oacsimage and oacslink plugins work. It will need some HTML strict cleanup too.

Tinymce on HEAD is version 2.1.3, the last one available is 3.1.1. I think we should upgrade, I can help with that. Right now, only english is available but if we upgrade, we'll be able to provide all the available languages (http://services.moxiecode.com/i18n/). The downside is that the API has changed in version 3.x so we'd have to adapt the oacs plugins and openacs theme, but it won't require too much effort I guess.

I agree that new parameter(s) should be created to hold the tinymce configuration. It may be worth to separate the different section of the configuration into different parameters (see http://wiki.moxiecode.com/index.php/TinyMCE:Configuration for reference): one parameter for the theme configuration, one for plugins, and one for general stuff. One might want to use the openacs theme but not the oacs plugins, in this case, the default would be kept for the theme parameters and the user would have to edit the plugins one only.