Jürgen Ragaller wrote:
Hi there!
We are planning to use TinyMCE as Editor for a project. If read the
dev-list correctly, TinyMCE and Bitflux share a common validation of
(x)html - so it's either Tiny or Bitflux. Did I get this correct?
the validation is part of the XHTML doctype module.
it contains an rng schema that currently includes only a subset of XHTML
elements.
if i change it to allow the entire XHTML spec, BXE falls apart.
if i leave it as it is, the server-side validation complains about the
code that tiny produces (tiny does not know about the subset of allowed
elements).
so afaik there is no way to make them both work.
Currently I cannot manage to insert a table from within TinyMCE - I get
a validation error complaining, that tbody is not allowed (and other
stuff).
Can the validation Part be configured/adjusted on a per publication
level so we can use TinyMCE before a better Editor-Integration?
yes. in your publication, you can create
/lenya/modules/xhtml/resources/schemas
then you copy $lenya-trunk/src/modules/xhtml/resources/schemas/xhtml.rng
into this directory (only that one file), and modify it to include the
complete XHTML set. the magic of fallback means you only have to have
this one modification, and the rest stays in the trunk.
Are there other known issues with TinyMCE that need to be adressed
before using this editor? I like TinyMCE - it produces decent code.
there are some rough edges (for instance, some layouts look very ugly in
WYSIWYG, particularly floating sidebars), but it should be usable.
i'm deploying it with two customers atm, so you can be reasonably sure
i'll keep an eye on it for the next few months, applying patches, fixing
bugs (and perhaps adding features as time permits).
your observations and suggestions will be welcome.
--
Jörn Nettingsmeier
Kurt is up in heaven now.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
