David Johnson
Top achievements
Rank 1
Rank 1
David Johnson
asked on 11 Jun 2009, 11:52 PM
This is not so much a help question, it's more of a general development query. I've noticed the AJAX editor loads 2149873971239472934 times faster than the classic editor - what fundamental changes did you make to make this happen? Are you using a single CSS sprite instead of multiple images? Gzip compression?
1 Answer, 1 is accepted
0
Hi David,
Of course, there is not one single loading speed optimization implemented in the *new * RadEditor, but many.
Yes, the editor now uses a single image sprite for all tools - which is certainly a major factor in speeding things up. Then the markup itself has been reduced by making it more semantic (using UL and LI tags), the output of localization strings has been reduced, the code of the editor has been refactored and reduced, the number of scripts needed has been reduced, the AjaxSpellChecker code (which is about 30K) is not loaded until the user clicks on the spellcheck button - these are some of the more important optimizations.
This has made the new editor load in about 25% (a quarter) of the time needed for the Classic version.
In addition to this, loading times of the new editor can be reduced even further by turning off application debug mode from the web config, e.g. <compilation debug='false'>.
Hence, for all these improvements we hope that you are already using the new editor :)
All the best,
Tervel
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
Of course, there is not one single loading speed optimization implemented in the *new * RadEditor, but many.
Yes, the editor now uses a single image sprite for all tools - which is certainly a major factor in speeding things up. Then the markup itself has been reduced by making it more semantic (using UL and LI tags), the output of localization strings has been reduced, the code of the editor has been refactored and reduced, the number of scripts needed has been reduced, the AjaxSpellChecker code (which is about 30K) is not loaded until the user clicks on the spellcheck button - these are some of the more important optimizations.
This has made the new editor load in about 25% (a quarter) of the time needed for the Classic version.
In addition to this, loading times of the new editor can be reduced even further by turning off application debug mode from the web config, e.g. <compilation debug='false'>.
Hence, for all these improvements we hope that you are already using the new editor :)
All the best,
Tervel
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.