Expose internal IceChangeEditor instance in TinyMCE plugin
Added a command to TinyMCE (via existing ice plugin) to expose the internal IceChangeEditor to allow plugins and external code access to the ice API.
Thanks, @primatology. I would like to keep the ice instance encapsulated in the editor plugin and then expose its api through tinymce's command interface.
Instead, can you put together a pull request adding any functions you need using the tinymce command interface?
@delambo, fair enough. In my current implementation, I need access to pluginsManager.usePlugins(...). How do you feel about a new editor command, 'ice_useplugins', that simply wraps the method?
Or do you envision a different method of injecting methods into the TinyMCE ice instance? I haven't looked at the codebase in two months, so forgive me if there've been updates.
Ah, I see what you're trying to do now. I think a second option might be to allow a plugins configuration in the tinymce ice config that would take a set of plugins and would mix it in with the set of plugins that are initialized in the initializeice command.
Configuration might be a better approach so that you can avoid having to use callbacks; although, I can see both approaches as being practical since a user may want to add a plugin set sometime after init. Feel free to take on whatever suits your needs or both options. Thanks.
Hey @benesch : Is this still beign worked on or have you given up?