Hi,
What would be really great is to split the project in different parts
One of this part (the minimalistic one) would be the core api. It consists of a set of methods, events and objects used to manipulate the editable area. No user interface at all in this api. Like this it would be possible to interact with the editable area by code instead of accessing it only by the user interface. This mean that it would allow the developers to create their own user interface, plugins, marco, etc..., but without the hassle of having to manage all the different browsers tricks regarding the editable mode.
I think it would be great to completely separate the user interface libraries from the core library, I mean physically (in different js files).
Best regards
Daniel
What would be really great is to split the project in different parts
One of this part (the minimalistic one) would be the core api. It consists of a set of methods, events and objects used to manipulate the editable area. No user interface at all in this api. Like this it would be possible to interact with the editable area by code instead of accessing it only by the user interface. This mean that it would allow the developers to create their own user interface, plugins, marco, etc..., but without the hassle of having to manage all the different browsers tricks regarding the editable mode.
I think it would be great to completely separate the user interface libraries from the core library, I mean physically (in different js files).
Best regards
Daniel
Re: Independant core api
Frederico Knabben
CKEditor Project Lead and CKSource Owner
--
Follow us on: Twitter | Facebook | Google+ | LinkedIn