Hi
Am 15.05.2007 um 16:22 schrieb Jörn Nettingsmeier:
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.
very nice - I added a comment to xhtml-basic and removed the comment
from xhtml-strict.
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.
At the moment we are using a <div class="box">...</div> floating to
the right (see also www.ethz.ch, they do it basically the same way).
And we are trying to write a tinymce plugin named box that generates
the html for such a box. The idea behind this is to avoid having two
editable areas but still have a 3 column layout (sort of).
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).
music in my ears...
your observations and suggestions will be welcome.
One rough edge is the procedure when a validation error occurs (I'd
say Users should get a chance to fix their code in one editor
session...)
:
1) Edit with tiny mce and (unluckily) produce invalid code
2) submit > the validation complains and says why (editor remains open)
3) fix the code
4) submit again
5) bang:
No transition found for event [checkExecutionConditions] in state
[executed]!
org.apache.cocoon.ProcessingException: Sitemap: error calling
continuation at <map:call> - file:/Users/ragaller/lenya/lenya14x/
build/lenya/webapp/lenya/modules/usecase/usecase.xmap:92:39 at
<map:mount> - file:/Users/ragaller/lenya/lenya14x/build/lenya/webapp/
lenya/usecase.xmap:57:131 at <map:mount> - file:/Users/ragaller/lenya/
lenya14x/build/lenya/webapp/global-sitemap.xmap:306:105 at
<map:mount> - file:/Users/ragaller/lenya/lenya14x/build/lenya/webapp/
sitemap.xmap:729:106
Thanks, Jörn - for the help!
Jürgen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
