Forum OpenACS Q&A: Re: How do I kill a WYSIWIG?

3: Re: How do I kill a WYSIWIG? (response to 1)

Posted by Dave Bauer on 04/21/05 05:40 PM

Carl,

HTMLarea has been removed from OpenACS, but replaced with RTE which just works better, so in OpenACS 5.2 we have a better option.

There is no way to turn off the rich text editor per user. I think you are asking for a way for the user to choose what editing interface they want.

In fact, OpenACS has a huge shortcoming in that there is no centralized way to store user preferences at all.

AFAIK HTMLarea or RTE should just disappear if your browser does not support it. Which browser are you using? I am suspecting Safari which incorrectly claims to support the rich text editing features. RTE (coming on OpenACS 5.2) correctly detects Safari and does not appear.

4: Re: Re: How do I kill a WYSIWIG? (response to 3)

Posted by Carl Robert Blesius on 04/22/05 01:04 AM

I am using Safari and it kind of works, but not really.

One of the use cases for the assessment package was a generalized way to store user data so this should not be to hard to add (considering this is how custom site wide registration data can be collected as it stands in head if assessment is installed).

BTW the WYSIWIG is throwing these annoying little javascript pop-ups that say something like: "I see you are using Mozilla < 1.3, this might not work but I will try it anyway" I keep looking for some way to tell he/she/it that they are very annoying.

Where do I kill the WYSIWIG site wide. I am going to remove them from sites I am involved with.