Re: [FCKeditor-Developers] Few Suggestions Regarding Plugins

[Scott M. [S. 8] <sco...@sy...>]

Did anyone get this email? Comments?

Does anyone still use this list?   Should I post these ramblings and have
this discussion on the forum instead?

 

From: Scott McNaught [Synergy 8] [mailto:sco...@sy...] 
Sent: Tuesday, 2 February 2010 12:50 AM
To: 'fck...@li...'
Subject: Few Suggestions Regarding Plugins

 

Hi guys,

 

I have a few suggestions for the plugins architecture for ckeditor.  I think
that everything in the plugins folder should be hierarchical and self
contained.

 

--- Plugins Folder Nesting ---

With the plugins folder, I sometimes find it a bit unintuitive having no
hierarchy and all the plugins in one big folder.  I think with time, this
folder is going to blow out to be massive.  

 

I suggest having folders like:

·         plugins/ui 

o   plugins/ui/button

o   plugins/ui/richcombo

·         plugins/elements

o   plugins/elements/image

o   plugins/elements/flash

o   plugins/elements/table

§  plugins/elements/forms/table/properties

§  plugins/elements/forms/table/tools

·         plugins/custom

o   plugins/custom/sometag

 

Then later on, it would be cool later on to make a builder script on the
ckeditor site that allows you to tick on various features, and it goes and
looks up the dependencies and runs the ckpackager on the server according to
your selection.  Similar to the mootools builder (http://mootools.net/more)

 

--- Languages in Plugin Folder ---

I think each plugin should have its own lang folder.  When developing on
localhost, the client can just make a whole heap more http requests for each
plugin to get the lang file.  The ckpackager can then merge and compile them
into the same lang/en-au.js style files that exist currently, but only for
the plugins in ckeditor.pack.

 

--- Icons in Plugin Folder ---

Each plugin should have its own icons folder as well.  Perhaps with a sub
folder for each skin.  When developing on localhost, again the client just
makes a lot more http requests to get the images.  But when packaged, the
icons.png file and the icons.css file have been dynamically generated by
ckpackager and load the same way as it currently works.

 

 

Fredck, if you would like, I am happy to implement and contribute some of
these changes.

 

 

Regards,

 

Scott McNaught

http://www.synergy8.com/