Hi everyone
Am 05.05.2009 um 14:01 schrieb Andreas Hartmann:
Hi Rainer,
Rainer Schöpf schrieb:
[…]
Improve the TinyMCE integration by making tiny_valid_elements.js
and the RelaxNG schema compatible (if possible).
I guess this would affect the BXE integration, wouldn't it?
Does it make sense to consider abandoning BXE?
Yes, I think BXE can and should be abandoned for the firedocs-
integration release. Uniklinik Freiburg and Uni Geneva both use bxe
and firedocs (don't know if that is in the same publications...) so
they most probably are on their way to replace BXE.
There are at least two organizations still using it [1]. Since it is
Firefox-only, I consider Firedocs a valid replacement, but I
wouldn't like to remove BXE before the Firedocs integration is
production-ready. We should probably even do at least one release
with both editors to provide a transition phase. I guess BXE 2 is
more advanced, but I have the feeling that the development has
significantly diminished.
This might break some features of TinyMCE, but would avoid the
extremely annoying and difficult to understand error messages you
sometimes get when you click on TinyMCE's Save button.
Of course, I'm most interested in TinyMCE since I recommended it to
my users. I can prepare a stripped down copy of
tiny_valid_elements.js; I have already started doing it on a case
by case basis.
Do you think we can provide a production-ready TinyMCE integration
in the 2.0.3 release, let's say in maybe two weeks?
Beside the BXE-Schema not beeing kompatible with Tiny (and FCKEditor)
there is a important bug still open for TinyMCE:
https://issues.apache.org/bugzilla/show_bug.cgi?id=43990
(TinyMCE editor doesn't convert images to lenya-document:{uuid} syntax )
I tried to upgrade TinyMCE to the latest (3.x)-version (a tinymce
lenya plugin upgrade is necessary for that matter) and fix the 43990-
bug - but that was obviously too ambitious for me (that was about a
year ago).
Jürgen
null-oder-eins GmbH Zürich
web & graphic design
www.null-oder-eins.ch
[email protected]
Skype: callto://ragaller
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
