Hello All,

While I have been only utilizing / learning concrete5 for about a month now, I must say that I have been loving the package structure / coding method set forth by the core. It is great, and it makes creating new blocks and being able to override / expand existing blocks easy to do.

My one "eh?!" moment however is seeing how ingrained the tinyMCE is in to the core. I've been starting to work on an Editor selector (or switcher if you want to call it that) so that the admin can select whether to use tinyMCE or CK Editor from the Editor option in the System Settings. Once selected, that editor would be available to the user within the standard content and the composer. I have been able to get CK Editor to do so in both instances, however one thing as a programmer that I see is a bit... disturbing, and I'm hoping I'm only missing something here. When I have the option for the CK Editor, the tinyMCE JavaScript file include is still there, and I cannot remove it as it seems to be so ingrained in to the core.

Another problem that's really making this project hesitant is that while I can expand the standard content block and the composer to utilize the CK Editor, add-ons that create / call their own editor instance will automatically call tinyMCE.

Perhaps there might be a way to make the editor more of a pluggable object and not so ingrained. Maybe there could be a config setting that is initially always set to 0 for the Editor to use, but can be useful for add-ons to see if there is other Editor's installed and if so then be able to call / look up what that editor is and use it instead?