Just to give a small example why it takes some time, knowledge and so on:
Right now we have two "WB only" modules in FCKEditor, the droplets and the link selector.
Both are the same, just with another icon / table / HTML output, but in core the very same.
Somebody thought it's a good idea to insert them into TinyMCE - where they don't work, but display (just like in the yet CKEditor), so in fact my "buggy" CKEditor is as finished as TinyMCE - because anybody can use e.g. CKFinder http://ckfinder.com/
. So it's as good working as such modules.
But - nobody thought, that the code of this Plugins is not really making sense.
Have a look - they make use of the plugin.js as any other. To initalize it, and make it appear in CKEditor. So far, so good.
But then everything "collapses" - because the plugins use their very own way of coding.
So if we really want to make use of the modules as they are, we need to put that much time into throwing everything out what is just useless, we can programm that module from core as it should be.
Then we can also make use of nice CKEditor things - like defining how WBlink should be opened, and so on. We don't need, but we can.
The only good CKEditor plugin I have seen so far is the Drupal - Joomla is crap, and modx is... Well, I don't want to speak of that. But the drupal one is quite huge, and quite different from codings I have seen before...
So, there is need of recoding, or better: New coding. Not because "new is always better and old is always crap", but because it just won't work.
But that would take time. Dietmar has waited now more than half a year for help, so one or two months more or less won't hurt anybody.