The forum operates in read-only mode.
Please head to StackOverflow for support.
Just throwing this up to get a discussion going, but I'm not sure about the usefulness myself.FCKeditor as en engine so that any custom GUI can use the functionality of it...See ticket.
Any kind of skin would be possible this way. Think of office2007, but any crazy idea would be possible.Also think about small apps that use just part of FCKeditor's functionality. For example imagine a link list where you can enter a link in an input field and a description in a textarea. The input field could be accompanied with a button that gets you browsing on the server with also upload functionality; and the textarea could have a toolbar for markup. This would be easy when being able to use the functionality of the FCKEditor. The input field button could use the 'Insert/Edit image' dialog and a small toolbar could be assembled with buttons you like.Small apps like this will benefit huge from a modular editor.
The idea we talked about at IRC expands your idea, where we would have: engine, frontend and template, as named by abraxas:
Where Template depends on Frontend, which depends on Engine. We provide 1 engine, 1 frontend (that can be replaced) and a few templates for that frontend (the so called Skins).
CKEditor Project Lead and CKSource Owner
Follow us on: Twitter | Facebook | Google+ | LinkedIn
The final results of these thoughts have been defined in the Basic Structure section of the V3 documentation.