Thanks for pointing that out. But what I'm more concerned with is the fact you're downloading TinyMCE, PLUS jQuery, PLUS the plugin so it's lot of stuff being downloaded, and much of the code you actually have downloaded is just duplicated effort. Both jQuery and MCE implement DOM selectors, iterators and manipulators, both implement an XHR wrapper, both implement event models, etc. What I was wondering has anybody taken the MCE code, cut its DOM, XHR, etc out and wired the jQuery ones in in their place? That'd eliminate duplication of effort between the two, and result in a smaller download size.
On Feb 20, 5:27 pm, tlphipps <[EMAIL PROTECTED]> wrote: > Regarding using jquery to 'attach' the editor, there is a plugin that > I believe does just > that:http://groups.google.com/group/jquery-en/browse_thread/thread/d33630d... > > On Feb 20, 10:33 am, Gordon <[EMAIL PROTECTED]> wrote: > > > I've been using TinyMCE to build a CMS that's also being built around > > jQuery for other functionality, and I got to thinking, a lot of the > > TinyMCE code is simply replicating functionality that's already in > > jQuery (DOM selectors. XHR, etc), so has anybody tried to remove this > > stuff from the MCE codebase and use the jQuery implementations > > instead? > > > Additionally, how about using jQuery functionality to attach editors > > to controls? For example $('textarea').tinyMCE () to attach editors > > to all elements, or $('#myEditor').tinyMCE to replace just a specific > > instance. You could use any CSS rule you wanted to determine where an > > editor should be created in theory. > > > And how about using jQuery UI to implement MCE's inline popup > > windows? > > > I do know there's WYM, which is built on jQuery, but that's very early > > on in its development and also appears to have stalled.
