V3 : ToolbarSet feature

[Frederico Caldeira Knabben]

Currently, CKEditor offers a way to provide the toolbar definition by setting it directly to the "toolbar" setting.

While that is useful, it would be still nice to have more than one toolbar definitions in the configuration file, making it possible switching them with a simple setting, just like V2.

The idea would be introducing the "toolbarSets" object setting, which accepts several definitions, and then make the "toolbar" setting smart. If it receives a string, its the toolbarSet name, otherwise it's a toolbar definition.

[Frederico Caldeira Knabben]

There is a simpler solution, which would also bring the possibility of having different toolbarsets sharing the same name in different instances (I know, a rare situation, but people is quite creative out there, so why not?).

Instead of creating a specific object to define toolbarsets, let's leave it all inside the config object as independent properties, to be sure we'll not having one instance mixing things with others. For example:

CKEDITOR.config.toolbar = 'Full';  // May be the toolbar definition.

CKEDITOR.config.toolbar_Full  = [ ... ];
CKEDITOR.config.toolbar_Basic = [ ... ];

So, when loading the toolbar, we simply take editor[ 'toolbar_' + editor.config.toolbar ].

Btw, let's take the opportunity to rename the "Default" toobarset to "Full". We'll have more on this later.

Also, do not change the editor.config.toolbar property to the relative toolbarset on init. Just put it in a local variable when needed. Who knows how the config properties can be used elsewhere.

KISS!

[Artur Formella]

I added the wrong patch by mistake. Correct patch is 3235_2.patch

[Artur Formella]

Fixed with [3328]