events

thatvetguy wrote:render: I often get an error that the editor or a function doesn't exist yet right after creating a CKEditor instance. An 'onready' or 'render' event could solve a lot of these situations. Alternatively the possibility to define a callback function when initiating the editor. Is this already possible?

You're looking for the "instanceReady" event. This event is fired for both the CKEDITOR object and the specific editor instance. For example:

CKEDITOR.on( 'instanceReady', function( ev )
    {
        var editor = ev.editor;
        ....
    });

CKEDITOR.replace( 'textarea1',
    {
        on :
        {
            instanceReady : function()
            {
                var editor = this;
                ...
            }
        }
    });

var editor = CKEDITOR.replace( 'textarea1' );
editor.on( 'instanceReady', function()
    {
        ...
    };

thatvetguy wrote:change: I don't know if this is possible, but a change event which is fired when the content is changed would be very useful. I'm currently using a task in ExtJS that calls the checkDirty() function regularly. But, obviously, this isn't a very good solution.

Check out this ticket: http://dev.fckeditor.net/ticket/900

thatvetguy wrote:I also would like to create CK events on my own. Something like

event = new CKEDITOR.event(DOMevent);

The result should be the same as the event object that gets passed to listener functions. Currently you get only an object with some functions. The objects mentioned in CKEDITOR.eventInfo (sender, data, etc) in the docs are almost all missing.

I'm afraid there is no support for it at this time, because it's still unclear on how this could used in the real world. Maybe you can give us some light on this.

thatvetguy wrote:One has to figure out a lot on his own. I find the api documentation lacking a lot of information...

I'm sorry to hear it... CKEditor is a huge application so it's definitely important to have good documentation. We'll be working on it.

thatvetguy,

I am working on the same task, i.e. an ExtJS wrapper for CKEditor ending up at the same problem (that's how I found this post anyway). Did you succeed getting it to work? When creating a new editor instance, "instanceReady" still seems to be too early to call editor.resize. In case you made more progress on that I would be more than happy to learn about it.

Thanks,
Henning

Just to let you know: It's all working now by doing some things in a deferred way (and listening to "instanceReady" to apply modified settings later).

Henning