For quite a while, we have been using a wrapper class we call DOMEventCache. Our widgets each their own instance of this class, which has a dispose() method, so when the widget refreshes its UI, dispose is called, which (among other things) unloads it's own local dom events. I highly recommend undertaking this type of encapsulation if you are authoring complex long running AJAX apps.
On 12/3/07, Tuan <[EMAIL PROTECTED]> wrote: > > > Oh man - yeah, the removal of this method really wreaks havoc on our > web app. We use UnloadCache() as part of our AJAX handling code - with > it gone, there's no way to wipe the slate clean with event handlers > for ajax loads. It's nice that it's called automatically on page > unload for IE, but what about for AJAX updates? I would looooooove for > this to be made public again! Until then, I guess we have to stick > with prototype 1.5 :( > > -Tuan > > On Dec 3, 10:14 am, kangax <[EMAIL PROTECTED]> wrote: > > >> "have been made truly private through the use of closures" > > > > Which sometimes becomes a real pain when you want to work with Event's > > cache, dom:loaded and other "private" methods... > > > -- Ryan Gahl Manager, Senior Software Engineer Nth Penguin, LLC http://www.nthpenguin.com -- Architect WebWidgetry.com / MashupStudio.com Future Home of the World's First Complete Web Platform -- Inquire: 1-262-951-6727 Blog: http://www.someElement.com LinkedIn Profile: http://www.linkedin.com/in/ryangahl --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
