Michael Wechner schrieb:
Andreas Hartmann schrieb:

[…]

From what I heard, TinyMCE is very popular a cross-browser (X)HTML editor, allows customization (AFAIK the EPO uses an enhanced TinyMCE), and doesn't make as much trouble as Kupu. BTW, I have some code somewhere which allows to execute build files in modules. We could use that to download TinyCME when the tinymce module is installed. WDYT?

I also think TinyMCE is quite fine, but please aware of the lincense

Also one might want to consider Xinha

I also heard positive things about Xinha, but there have been some negative remarks on the markup it produces:

https://addons.mozilla.org/de/firefox/reviews/display/1449?show=20&page=2

"Looks Nice, Poor Markup: The text editor is rich with useful features and well laid-out. If it produced valid XHTML markup it would be of real value."

Supporting XHTML strict is apparently not on their roadmap:
http://xinha.webfactional.com/ticket/137

Would it make sense to consider introducing a non-validating HTML resource type and rendering these documents using the HTML generator (JTidy)? But I have to admit that all my hair stands on end at such a thought :)

OTOH, from my experience the browser plug-in approach (Yulup, Firedocs) allows to offer a very good user experience and rich feature set. Here the major question is about the communication interface. I'm not sure if it is realistic to expect the editor vendors to agree on a standard interface (like CMIS), though.

I wouldn't rely on CMIS for the moment, but I still very much believe that Lenya and all other CMS should support something like the Neutron/Atom/OrWhatever protocol and allow to easily use such editors as Yulup and Firedocs

BTW, here's the documentation about the protocol Firedocs uses (Atom + some extensions):
http://firedocs.org/development/docs/remote_editing

The server- and (IIUC) client-side implementation is almost completed. If nobody objects I could commit the Lenya module in the contribution area.

Another option would be a thighter cooperation between the editor vendors and the Lenya community. This was quite good when we started to integrate Kupu, but Guido Wesdorp hasn't been active on the list for quite some time. The same applies to BXE.

as you point out there is the risk of a "single point of failure"

Yes, from the POV of the Lenya community a standard interface would be extremely helpful to avoid the dependency on a particular editor. But AFAIK all past attempts to agree on such a standard have failed. Maybe it is just not realistic to hope for such an agreement?

-- Andreas


--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to