Integrate a web based WYSIWYM editor : a good idea ?

Hmm...this might be relevant then:

http://docs.jquery.com/Using_jQuery_with_Other_Libraries

Indeed that looks like exactly the trick needed.

Even better, it looks like the developer has already taken namespace conflicts into account and has posted a integration example that looks like it should be pretty simple.

http://trac.wymeditor.org/trac/wiki/0.3/Integration

OKAY, I was for XStandard before I knew from WYSIWYM.
Now I’m converted to the "WYM-Editor"!

WYM-Editor now supports: MSIE 6.0+, Gecko-based browsers (e.g. Firefox 1.5+) and Opera 9.0+.
ADDING EVEN IE5.01 support is no problem in my eyes. Thanks to Dean Edwards BASE2 and legacy file (http://dean.edwards.name/weblog/2007/03/yet-another/)

The MSIE6.0+ limitation is due to jQuery which is based on the base library version 1. Thanks to version 2 and some Javascript developers we can achieve realy crossbrowser support.
However the most important is that it gets integrated into modx as alternative or main editor.

*I’ve tested it and it works like a charm*

Please integrate it in the next built.

Pleas inform us about news regarding the BUILT-IN Editor in MODx

If WYM doesn’t support or at least have a fall-back working mode for Safari, it won’t be a replacement.

Plus, with WYM-Editor, JQuery is a requirement. I don’t know if this will work in conjunction with MooTools or not. We’re gonna be using alot of MooTools and Ext within the manager and that may or may not cause issues with something like WYM-Editor. However, if we decide to substitute MooTools with JQuery then this would indeed be doable. But for the time being...well...don’t know if it’s feasible right now.

there is no problem working with mootools and jquery - just put them in there own namespace’s.

jQuery and MooTools can indeed be made to play well together after all, thanks to the folks at jQuery building in a very flexible compatibility routine (mostly just to use $j or something else instead of the $ shortcut). Which is great news for us jQuery fans. However for core code I still think it makes sense to concentrate on just one library and use scripts that work with it, rather than loading two or more just to be able to pick and choose scripts that work with each.

no matter which core code you use, base library from dean edwards is used in both..the news is that there is a new version of base library base2.