Altough I already have written about it here I would like to emphasize the importance regarding the possibility to integrate CKEditor in popular js frameworks that don't have a good html editor (yet).
jQuery doesn't really have a RTE. They have some half-baked, not ready for production solutions (WYMeditor, wysiswyg and others) which are buggy and not very feature rich. There are of course plugins to integrate FCK and tiny but these aren't tightly integrated, especially not with jQuery UI.
ExtJs has only it's own RTE which is limited and people are beginning to write extensions for (only a few). And there are also the integration plugins which IMHO the tinyMCE one currently wins.
YUI has IMHO a decent RTE which is expandable but isn't as feature rich as FCK. I don't know the Dojo editor that good...
The story seems always the same. It is very hard to create a good RTE! Because of lack of time, dedication, browser differences/bugs/annoyances, usability issues, etc... I don't know really. But it is obvious that in almost every js framework project there is a need for a RTE and if there isn't one (which there isn't) people start to try to integrate one of the existing solutions or they try to build their own but that almost never succeeds. How many of these have survived?
WYMeditor is (almost) dead. Nicedit hasn't seen any development since March, there is no writable public repository and the developer is absent from the forum since more than 2 months.
So... Why do I think the integration of CKEditor into JS frameworks like Ext or jQuery or dojo is so important? Because:
- There is no editor that can do it today. There are a few editors out there that can be integrated but there isn't one that can do it right. There's no competition here (yet). Be the first, get the fame.
- Attract professional JS developers. A lot of people are using current RTE editors, from the hobbyist to the professional. JS frameworks attract especially professionals. Getting them involved in the project or gaining them as new users means not only having a broader user base but also more quality bug reports and maybe one or two or twenty future plugin or core developers.
- The users want it too. Users are always complaining about the missing of a RTE. And I'm sure there are more than a few developers out there, that are willing to help on this.
- Framework lead devs want it too. Having a new shiny feature in your library without having to maintain it, great! But there might be licensing issues (jQuery is licensed MIT/BSD)...
I saw that there are scripts for server side integration. Why not create integration scripts for the JS frameworks? Doesn't this make more sense? Because then you're attracting people with skills that this project can use.
Summary: Tight integration with JS frameworks leads to a lot of fame, new users and professional js developers which are able to give back. Which leads to a better project after all I think it's a win-win and now is the best time to lay the groundwork.
(i hope this made sense... it's 2am now...)