The main problem that I see with that idea is the part about rendering the HTML at the server. You say that it's possible in Ruby, but I don't think that it will be easy for almost any other language, so it might be useful only for a few people, not most of the users.
keith.pitt wrote:I also had another idea, fck could piggy back on other frameworks the user is loading. Very much like what Ext http://www.extjs.com does. If the user has prototype on the client, fck could call utility functions from prototype, as apposed to internal functions. There obviously could be a fck version of the functions, so fck can run by itself.
alfonsoml wrote:The main problem that I see with that idea is the part about rendering the HTML at the server. You say that it's possible in Ruby, but I don't think that it will be easy for almost any other language, so it might be useful only for a few people, not most of the users.
True, but I would say most developers know about ruby, and are able to install it quite happily. I also believe a ruby script can be compiled into a standalone .exe, which should work on all machines. You could also provide an online solution for those who do not have access to ruby. The idea was to render the html on the server, save it as a blob of html in a file, and have the server script open the file, and throw that html at the client. The rendering of the html would only be done in ruby. I know prototype and script.aculo.us were able to deploy there projects with ruby rakefiles and test suites. But yeah, anyway its a idea.
One of the aspects we'll be strongly concentrated during the development of V3 is loading speed. There are definitely several points for enhancements in the current implementation. We expect to have huge improvements in this sense.
I'm not sure that having the static HTML for the editor interface would speed up that much the editor loading. Not in such noticeable way. For instance, the HTML for the toolbar of FCKeditor 2 is about 20KB, so it would impact also in the download time.
Anyway, at the right moment, let's try to measure the time to build the editor interface, then we could consider this based on numbers.
keith.pitt wrote:I also had another idea, fck could piggy back on other frameworks the user is loading. Very much like what Ext http://www.extjs.com does. If the user has prototype on the client, fck could call utility functions from prototype, as apposed to internal functions. There obviously could be a fck version of the functions, so fck can run by itself.
keith.pitt wrote:True, but I would say most developers know about ruby, and are able to install it quite happily.
What a statement! I asume that you also know about IBM System i (formerly AS/400, and the most used business machinery in the industry) and know how to "install" DB2 on it?
Re: Some speed ideas.
Re: Some speed ideas.
Re: Some speed ideas.
Re: Some speed ideas.
True, but I would say most developers know about ruby, and are able to install it quite happily. I also believe a ruby script can be compiled into a standalone .exe, which should work on all machines. You could also provide an online solution for those who do not have access to ruby. The idea was to render the html on the server, save it as a blob of html in a file, and have the server script open the file, and throw that html at the client. The rendering of the html would only be done in ruby. I know prototype and script.aculo.us were able to deploy there projects with ruby rakefiles and test suites. But yeah, anyway its a idea.
Keith
Re: Some speed ideas.
I'm not sure that having the static HTML for the editor interface would speed up that much the editor loading. Not in such noticeable way. For instance, the HTML for the toolbar of FCKeditor 2 is about 20KB, so it would impact also in the download time.
Anyway, at the right moment, let's try to measure the time to build the editor interface, then we could consider this based on numbers.
Frederico Knabben
CKEditor Project Lead and CKSource Owner
--
Follow us on: Twitter | Facebook | Google+ | LinkedIn
Re: Some speed ideas.
Frederico Knabben
CKEditor Project Lead and CKSource Owner
--
Follow us on: Twitter | Facebook | Google+ | LinkedIn
Re: Some speed ideas.
Re: Some speed ideas.