Some speed ideas.

Gday all,

I have some ideas/thoughts on fck loading speed that I thought I might share.

I noticed that when you load a blank page in a web browser, loading speed is real quick, add some html, still relativley quick, add some javascript.......get slow. When ever I write an application, speed and responsiveness plays a vital in my final product, so I came up with an idea that would theoretically increase the loading speed of the fck editor. The concept may not suit the project, but its something to consider. What if all the plugins, editor definitions, etc, were compiled, and not run during runtime on the client. I think its a waste of resources when everytime the page loads, the user has to reload and parse all the fck editor code. The core fck code could live on the client, but plugins and configs live on the server, for example:

User defines a plugin using javascript, that is parsed by a compiler.
User defines a config file that is parsed by the compiler.
Compiler creates a html blob, that contains the editor as the user sees fit.
Compiler creates a js file with id's and such, so no dom traversal is neccessary.
Server side connector grabs the html and chucks it out to the server, with the custom js file, and the core fck code.
Then wha'la, the editor should just come to live.
No need to dyanmically create dom objects on the client (which I hate, but do )

Obviously the code would allow it to be compiled at runtime, in the case that a server compile isnt avaliable. I never got around to implementing it, but it sounds good in theory. For the techies, it could be implemted using ruby and the ruby-spidermonkey library. I've done some experimenting with it in the past and it worked rather well.

Thoughts, ideas?

Keith