Each element's events point back to a central dispatch function, which looks for the target element's __listener expando, in order to call onBrowserEvent(). The beauty of this is that it allows us to set and clear a single expando to clean up any potential event leaks.
serializer wrote:Is using a 3rd party framework such as jQuery being considered? (http://www.jquery.com) Since I already use it in many of my projects, the overall result would probably be a reduction in JS weight - since I am already loading jQuery, and FCK's code would be far lighter without implementing its own DOM manipulation. jQuery itself is only 15k with optimal compression.
serializer wrote:I could see clear advantages to working with an existing open source framework; the development effort towards abstraction and browser compatibility is combined across the community, and projects like FCK can focus solely on their features and interface.
fredck wrote:Wait... the minified version of jQuery is a 52.8 KB file (currently). I'm getting the minified version of it because it uses the same compression mechanism we use for FCKeditor.
Re: DOM Abstraction and Memory Leak Free
Keith
Re: DOM Abstraction and Memory Leak Free
Frederico Knabben
CKEditor Project Lead and CKSource Owner
--
Follow us on: Twitter | Facebook | Google+ | LinkedIn
Re: DOM Abstraction and Memory Leak Free
DOM Events, Memory Leaks, and You
Re: DOM Abstraction and Memory Leak Free
abstracts
Frederico Knabben
CKEditor Project Lead and CKSource Owner
--
Follow us on: Twitter | Facebook | Google+ | LinkedIn
Re: DOM Abstraction and Memory Leak Free
Re: DOM Abstraction and Memory Leak Free
Re: DOM Abstraction and Memory Leak Free
52.8 KB
Frederico Knabben
CKEditor Project Lead and CKSource Owner
--
Follow us on: Twitter | Facebook | Google+ | LinkedIn
Re: DOM Abstraction and Memory Leak Free
http://www.julienlecomte.net/blog/2007/08/13/