Tuesday 13 September 2005 2:47:26 am

Personally, I like TinyMCE and especially Xinha. Xinha has by far the most features of them all (even server side spellchecking etc for the so inclined).

I'm however still not 100% convinced if ezxml can be made sane enough to interface easily with it.

For one thing, it throw errors after me in the past when I tried to do nest lists (why, I can only speculate, I THINK it's to ease the PDF people's job). If ezxml can be modified to support a SANE subset of XHTML, it shouldn't be that hard. But until that happens, good luck on hoping that the XHTML you sent will be accepted ;).

At the very least, it would have to have support for:

<br/>
<p></p>
<ul></ul> (and obviously li)
<ol></ol>
<table></table> (and its children, i.e. th, tr, td)
<div></div>
<span></span>
<pre></pre>
<img/>
<a></a>

and the special ezpublish tags, all nested in whatever way allowed by the XHTML spec. formatting can be done with span and divs, so I'm not that worried about those tags (in fact, phasing out font and strong and its relatives is about time).

If it can be avoided, I really rather would NOT deal with

 <custom tags="name">

as with the above mentioned selection, it should be possible to allow most every halfway sane layout.

As for dealing with embedded images coming from the CMS (as opposed to external ones), I think I'd simply add the proper embed ezxml tag and use a AJAX call to have the CMS supply me proper HTML for that. OTOH, it shouldn't prove very hard to convert from a suitably named img to embed and back.

To avoid possibly infinite trouble, I'm set against supporting embed for anything ASIDE of images.

Visit http://triligon.org

Wednesday 14 September 2005 2:49:02 am

Great!
although I don't have much experience with ezpublish extesion development I'm going to change that. alternative for OE and partly obsolete (for 3.6, 3.7 ezpublish) XMLarea is a must and I'd be happy to help.

Wednesday 14 September 2005 4:37:47 am

xavier - xmlarea does work exactly how you suggest it should work. it doesn't send ezxml to the client (other than when you choose to edit in ezxml or javascript isn't available).

it shouldn't be too difficult to integrate a different xhtml editor. it's just not a job i relish as it will involve messing around with javascript again.

i think only a few small changes need to be made in the input/output handlers to ensure compatability with 3.6. i will have to get around to doing this soon as i think i'm going to have to upgrade to 3.6.

sorry i haven't replied to your mail yet.

Wednesday 14 September 2005 8:32:48 am

i hacked the javascript quite a bit. the plugin architecture just wasn't powerful enough to do what it needed to.

the handling of nested lists is a bit of a hack cos htmlarea spits out some rather odd xhtml at times.

Thursday 15 September 2005 4:59:11 am

If I'm gonna do it, I'll be using Xinha. After some tests, it's by far the most flexible editor and also still being actively developed daily.

As for the image stuff on mosce, I can't get it to work. I have my ideas what to do with images, but it's not gonna be too easy and first I'd want to get a sane input handler up and running. After that, GUI work can be done.

Visit http://triligon.org

Thursday 15 September 2005 7:11:07 am

Hi,

In my mind, what is important is to have a proper fundation. I want something easier to extend and able to cope with the changes on the xml schema defined by ez. I want something able to cope with the way content is stored, should it changed (eg, links are stored differently between 3.5 and 3.6).

On the server side, it means usign the regular classes as far as possible, inherit from the ez classes if you need new features or methods and generaly avoid reinventing the wheel (and while I'm at it, no copy paste from existing methods).

I don't care much right now about specific features like attaching images or links. I want something that is extensible enough to be able to add that and other wonderful plugins if needed.

In fact, the system should be able to switch from one wysiwyg editor to another without too much pain. I'm afraid when stevo said he had to change a lot of js on htmlarea, that's something I'd rather avoid.

This being said, If I can't start from Stevo+'s work, I'd rather start with the best one ;)

How's the community around TinyMCE ? is it reactive ?

I need to find some time to test them more seriously and have a look at the code.

X+

P.S. I've been able to find a few people offering their help on the net, but could the other drop me a mail at sydesy[at]gmail[dot]com ?

http://www.sydesy.com

Tuesday 04 October 2005 11:05:30 pm

Hi,

Although I welcome a new WYSIWYG extension using an editor that is actively developed, STEVOs xmlarea has worked great for me on several 3.5.x projects, and I was hoping to see it compatible for 3.6 so that I can keep using it in the near future.

STEVO: Are there any news on 3.6 compatibility?

Thanks in advance !

Sincerely,

Eirik Alfstad Johansen
http://www.netmaking.no/

Friday 13 January 2006 11:48:28 am

KUDOS!
I am really encouraged by the progress made here. I installed it and I can get Xinha to load (Firefox, but not IE).

But then I run into the bugs... I may find some time to help

version ezpublish 3.7.2