[Ralph]

I wasn't sure exactly where I was going to post this topic and decided that here was the best place, for now at least...

I have managed to integrate WYMeditor into Etomite 0614/5 - almost... It just depends on which browser you are using... After spending some 10 - 12 hours working on the integration, almost non-stop, I managed to get it integrated and working as expected using Firefox... I even managed to modify it to include DIV tag containers, to an extent...

When I attempted to test the integration in IE7 I was shocked to find that there is a major bug... First, I had to add code to the editor style sheet to suppress list-style-image from inserting those cute yellow boxes that the manager uses for list items... Then I was even more surprised to find that with every keystroke in the editor panel the entire document disappears until you mouse around the editor, changing focus... My gut feeling is that there might be a javascript routine monitoring the events and that is where the problem lies... I haven't had a chance to look that far yet...

I guess my main reason for posting this information here is to let the Etomite community know how much time we developers put into making things work... What may seem like a Plug-N-Play integration can takes hours, days or, worse yet, even weeks... Sure, the demo's work great as stand-alone code, but will they perform as flawlessly in a working environment and play nice with the rest of the code that shares the same page...??? Only time tells that tale... Suffice it to say, I was a bit discouraged to see the editor fail when using IE7... That's actually an understatement... Downright pissed is a more accurate assessment of how I felt, and I'm not much happier even as I write this...

So, what's the big deal...??? Why is this happening...??? Easy questions to answer... The existing code base has become, or always was, too unwieldy to keep stable in its present form... The mutate_content_dynamic.action.php file should have been broken down into smaller pieces from the very start... Additional features have only made things worse... That's why we need a complete rewrite... And knowing that even an Alpha release of Cocoon is in the distant future, we need to make some decisions... Do we break this module down into more manageable pieces or do we just say enough is enough and lock the code base down completely... I'm not thrilled with the idea of locking down the code base, although it would be the easiest answer...

Ideas...??? Suggestions...??? I'll probably be looking into splitting up the mutate_content.dynamic.action.php file today so if anyone has any input, or would like to help, don't waste time in responding... Oh, and this will definitely delay the 0615 bug fix release, as well as delaying work on Cocoon... However, some of this work will need to be done for Cocoon anyway...

[cathode]

I for one an excited about the progress you've made, even if it shows that Etomite in it's current state cannot use wymeditor - at least I know it'll be possible in Cocoon.

In case anyone is curious, WYMeditor is a replacement for Xinha, RTE, etc. It's a standards-based editor that displays the content in it's semantic-markup form while editing it- making it simple for a user to see how their content is formatted.

I encourage everyone to go and check out the WYMEditor demo. It's a must-have for the next version of Etomite! :D