id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
13487	Make CKBuilder Better Support CDN Loading	Steve James		"First: Thank you for all your efforts! You guys are extraordinary.

I would like to suggest that CKBuilder be extended to better support those of us who would prefer to load CKEditor from a CDN, but use a lot of extra plug-ins.

I have read your doc on loading from a CDN: http://cdn.ckeditor.com/

I already load jQuery, jQuery UI, and Amplify from CDNs, so it is nothing new to me.

However, I do not want to load CKEditor from a CDN, as of yet.

Here is why: I load a lot of extra plugins that my users like, many of which are not in your available builds from the CDN.  Unless I am mistaken, I would end up with a lot of extra HTTP calls to load those plug-ins from our server that would probably offset the benefit from CDN loading.

Although, your CDN doc is helpful, it begs the question to me of why you do not just extend CKBuilder to be able to create a ""mega plug-in"" (a bunch of concatenated plug-ins w/ setup code, but w/o the core ckeditor) for extra plug-ins that are not part of the standard builds, such as for the CDN builds.  That way, I could just load one of the available builds from the CDN, and I could use CKBuilder to put all the extra plug-ins in one ""mega plug-in"" to be loaded from our server.  It keeps the number of HTTP calls low, and enables me to more easily set up a CDN fall-back for my users in China for whom CDNs are sometimes blocked.

And, yes, I could probably set something up to concatenate the various extra plug-ins myself.  However, isn't that what CKBuilder basically does, anyway?

"	New Feature	confirmed	Normal		Project : CKBuilder	4.0