Extend the functionality for the text field plugin

Is there a way where we could extend the functionlity for the existing plugins like text field, text area, image etc. I dont want to add code to the exisiting js, but rather use the existing js in another way and add functionality to it. Like say I want to make the text field databound, so how to go about it.

Quick response would be greatly appreciated.

Thanks in advance.

Wed, 03/20/2013 - 09:29

reinmar

Joined: 24/08/2012

Posts: 631

Check this sample: http:/

Check this sample: http://nightly.ckeditor.com/standard/samples/plugins/dialog/dialog.html

You can modify existing dialogs using dialog API.

Piotrek (Reinmar) Koszuliński
CKEditor JavaScript Developer
--
CKSource - http://cksource.com
--
Follow CKEditor on: Twitter | Facebook | Google+

Wed, 03/20/2013 - 13:36

(Reply to #2) #3

K Vasavi Sivakumar

Joined: 20/03/2013

Posts: 2

Hi - I went through the

Hi - I went through the dialog plugin. Thanks for that. But is there a way where I could extend the existing functionality of the plugin, say use the existing textare.js and add few more elements to it. Meaning I dont want to mess up with the existing textare.js

Thanks

Wed, 01/22/2014 - 19:48

kalupa

Joined: 22/01/2014

Posts: 1

Extending core plugins

Hi,

I hate to recusitate an old post, but I'm also interested in doing the same thing.

I wanted to have the Font drop down fire beforeCommandExec and afterCommandExec events as it doesn't do so right now.

Any help would be greatfully accepted.

Wed, 02/05/2014 - 14:16

moniuch

Joined: 12/01/2012

Posts: 4

Very interesting. I kind of

Very interesting. I kind of missed the ability to extend plugins until I digged into that example.

@reinmar: you said "You can modify existing dialogs using dialog API" What if I wanted to subclass my widget (with own button and command) on an existing plugin? I don't seem to see a method to specify base widget definition or dialog definition on top of which we want to build our widget/dialog. Are you considering the following on your roadmap?

editor.widgets.add('esa_quotebox', { defn }, 'baseWidget')

and:

CKEDITOR.dialog.add('esa_quotebox', 'path.js', 'baseDialog'); // <-- dialog that we know exists through "requires:" dependency

or perhaps via:

CKEDITOR.dialog.getDefinition('tableProperties'); // <-- get definition alone, for use in event handlers, such as:

CKEDITOR.on( 'dialogDefinition', function( ev ) {

var baseDlg = CKEDITOR.dialog.getDefinition('tableProperties');

  baseDlg.addContents( {
      id: 'customTab',
     label: 'My Tab',
      // elements
  })
});

Or is it feasible in another way?