Forum OpenACS Improvement Proposals (TIPs): Re: TIP #134: Change default value for RichTextEditor param in acs-templating

Collapse
22: Re: TIP #134: Change default value for RichTextEditor param in acs-templating (response to 18)
Posted by Rocael Hernández Rizzardini on 06/06/09 09:27 PM
We use special widgets for the content tool, and for assessment as well, more will come.
Based on arguments exposed here, I do not approve the change, until the remaining issues are cleared, and I would prefer to ask first the community about whether they use xinha, or they want to change to something else, and listen the pros / cons of changing to a new editor, which is a very important part of any system that produce content like OpenACS/.LRN.
Collapse
23: Re: TIP #134: Change default value for RichTextEditor param in acs-templating (response to 22)
Posted by Don Baccus on 06/06/09 09:37 PM
Based on arguments exposed here, I do not approve the change, until the remaining issues are cleared, and I would prefer to ask first the community about whether they use xinha, or they want to change to something else, and listen the pros / cons of changing to a new editor, which is a very important part of any system that produce content like OpenACS/.LRN.
You (and to some extent Gustaf) are arguing against a strawman, in other words rather than arguing against the TIP, you are arguing against something else of your own invention which is not the TIP.

The TIP is NOT to "switch to a new editor" or "to change to something else".

OpenACS/.LRN has supported *both* TinyMCE and xinha for some time, this TIP does not change that.

This TIP is only to change the *default* editor selected if you change from the default configuration which is NO WYSIWIG AT ALL.

Adoption of this TIP in no way prevents you or Gustaf or others from using xinha.

So please stop arguing that it does. It pisses me off.

The argument for changing the *default*, because out-of-the-box it gives you more accessible and valid HTML without the use of external apps like "tidy", and we claim to support that (I realize that traditionally neither you nor Gustaf consider accessibility to be particularly important, but honchos and the board have decided otherwise).

So we are simply suggesting that we provide a cleaner editor *by default*, not that you stop using xinha.

Collapse
30: Re: TIP #134: Change default value for RichTextEditor param in acs-templating (response to 22)
Posted by Dave Bauer on 06/08/09 02:25 AM
Roceal,

I think the existing of local custom plugins does not affect what editor is available in the core as a default. Of course if something is actually broken, we should fix it. It is not difficult to make plugins for TinyMCE or Xinha either.

I personally don't have a preference for TinyMCE or Xinha as the default. I have not evaluated which one is better for a certain purpose. I did the original work for MGH and added the newer TinyMCE because it supports translations of the TinyMCE interface.

Collapse
31: Re: TIP #134: Change default value for RichTextEditor param in acs-templating (response to 30)
Posted by Dave Bauer on 06/08/09 04:56 PM
Ok I added per widget config options. You can override any of the tinymce config elements using the same syntax.

Setting {options {editor xinha}} will override the default editor for tinymce or xinha, this already worked as it was built into the richtext widget origianlly when we still supported RTE.

I'll see if I have time to get the OacsFS plugin to work on TinyMCE.

It probably will take 2-3 hours. One good thing of these editors is the plugin architecture. Both editors are very easy to add new plugins.

Collapse
32: Re: TIP #134: Change default value for RichTextEditor param in acs-templating (response to 31)
Posted by Emmanuelle Raffenne on 06/08/09 05:07 PM
Thanks Dave. I'll fix the version numbers.
Collapse
33: Re: TIP #134: Change default value for RichTextEditor param in acs-templating (response to 30)
Posted by Rocael Hernández Rizzardini on 06/08/09 06:17 PM
Yes, the default won't affect local install preference (you can change it at any time), this boils down that the online editor it's a matter of preference. The major problem we still face with online editor is the copy/paste from word :p
Collapse
35: Re: TIP #134: Change default value for RichTextEditor param in acs-templating (response to 31)
Posted by Emmanuelle Raffenne on 06/09/09 07:06 PM

Hi all,

I've updated the release notes in acs-core-docs including the right version number. (thks Dave for the upgrade)

I've added the missing message in tinymce (oacslink.desc etc.).

I've updated the doc of template::widget::richtext for tinymce. It was a bit out-of-date. It says that oacsfs scripts live at xowiki, is that still true?

Caveat: the three adp-files needed for the OpenACS file selector (insert-image, insert-ilink and file-selector) are currently part of the xowiki package, since acs-templating is per default not mounted. This is hopefully only a temporal situation and we find a better place.

I don't know if it has been moved to acs-templating but in any case, it means that to use it with xinha it needs xowiki installed or acs-templating mounted.