We've recently seen a flurry of news surrounding newly released revisions of various editors for the XOOPS environment (Xoops Editor Package - V1.01 and Tinyeditor - V1.0 RC1). Personally, I've used the Koivi editor on my sites. What I would like, however, is a discussion amongst the XOOPS community here comparing these various editors.

Which one(s) do you like best? What do you like about them? What don't you like about them?

For HTML I too would choose Koivi - because AFAIK it's the only one that lets users add images from the XOOPS image manager. On the down side (unless this is now fixed) it cleans up your raw code. This would be fine if admin could turn the feature off, but on the version I tried I had problems pasting a JavaScript into the text editor, even in code view.

One thing I found frustrating with all of the editors I tried was that none of them followed typographic conventions - i.e. created a para break (P) on 'Enter' and a line break (BR) on 'Shift+Enter'.

With double BR tags everywhere it makes it hard to do anything stylish with text using CSS. The editor that ships with WordPress is the only one I know of that does it properly.

On my wish list - 'proper' typography and pre-defined CSS classes in a drop-down menu.

... and a DHTML editor like the one in DokuWiki.

Quote:

No, I wrote a plugin for tinyeditor.

P on Enter? tiny will do
BR on Shift-Enter? tiny will do

CSS classes in a drop-down? tiny will do

So the battle for me has ended!

Thx for that frankblack. Now I'm getting a 'tiny' bit excited (typographically speaking).

Is the image manager plugin included with the download?
Does it work in Firefox and IE?
Does it work on a Mac?

Yes the XOOPS image manager is included in the basic package. And if your browsers are able to understand html and do not block popups - then and only then - it is working.

its a long time that we expect for a totally BBCODE editor that just have WYSIWYG view.

To do it, it needs 2 converters.

(1) BBCode -> HTML in editing page
(2) HTML -> BBCode in viewing page

IMHO this wysiwyg editor wins the battle

Tiny wins for me too. I just love its versatility. Easy to set up too.

Quote:
This I don't get. You would have the content put into HTML, converted into BBcode, which is converted into HTML by the textsanitser all over again? Now that's adding more useless work to the rendering engine for sure...

No, IMHO Tiny should have a limited default editor (like Wordpress has, uses TinyMCE too), thus prevening misuse. The content is stored as semantic xhtml in the db, and the system doesnt need to revert it back to html from bbcode, slowing it down.

Herko

Quote:

tiny forsees such a possibility right now! I guess it is a feature that I forgot to announce or explain more clearly.

I found a way to mimic the standard dhtml-editor. Maybe you can test yourself if you implement this at a place where no further WYSIWYG is needed. Just one parameter has to be set to reduce tinyeditor to this mimic-mode.

Here is the example taken from news 1.44:


Important is the xEditor-array. 1 or missing parameter means tinyeditor uses the full functionality, whereas 'xEditor'=>'0' means that tinyeditor takes the reduced instruction set for the mimic-mode.

I see, writing more clear and easy docs are needed... sigh!

P.S.: The above code is just a snippet. It needs more to be working...

Herko it seems you misunderstood me

I talk about a totally BBcode WYSIWYG editor that don't need "HTML enable" to work.
because its not safe to use html editors in many websites like xoops.org

there's an editor samuel works a long time ago:
https://xoops.org/modules/news/article.php?storyid=2917

and i think phppp works on a same thing.

Quote:
No, I didn't misunderstand you at all.

You want this:
WYSIWYG editor that writes pure BB-code. So the content is stored in the DB as BB-coded content.

What BB-code does however is change the content back to publishable HTML when the content needs to be displayed.

So: you propose wysiwyg -> bb code -> html
I propose: wysiwyg -> html

BB code was meant to *replace* (or preceed is more accurate) the complex and expensive WYSIWYG editors at the time (there are no good open source wysiwyg editors back then). You could make it easy to manage what is used and what isn't, and still allow people to add some special markup to their content.
Now, however, there are plenty of mature and manageable open source wysiwyg editors. Now you can do what you with them what you did with bbcode, but now you can do it even better.

SO, why add it on top of bbcode? You can santize the output even better then you can with bbcode (less coding necessary for that), you can manage rights, you can extend it easier.. Youhave the security of bb code, but you have so many advantages over bb code.

bb code isn't an end unto itself, it is a means to acieve something alse. If you focus on what you want to achieve, it's a logical step to *replace* bb code with a good editor like tinyeditor.

@frankblack: I know that I can confige tinyeditor to use a limited editor as default one. I love it

Herko