This project is archived and is in readonly mode.

#1 ✓resolved
Thomas Aylott

Extension to Garbage - manual dispose method

Reported by Thomas Aylott | May 28th, 2008 @ 09:59 AM | in 2.0 (closed)

Originally posted on Trac by bbakerman@…

Original Trac Ticket

Description

The current Garbage.collect mechanism only actually "garbage collects" on page unload.

However many AJAX frameworks that might use mootools dont move off the page but rather do dynamic DOM insertion of thier complete lifetime, hence no window.unload and hence no garbage collection occurs.

Mootools in such an environment would simply "use omre and more memory" with no reclamation.

I propose that a method be in put in the Garbage class that could force a cleanup for a given element and any of its children.

That way as elements go out of "logical" existence, one could then "call" the Garbage class to clean it up.

It might be called Garbage.dispose(element) and it would clean up that element and perhaps any of its children.

Trac Attachments

Trac Comments

Changed 1 year ago by digitarald


        
(In [328]) * Merged trunk in my branch 
* Updated length in Hash.remove (closes #108) 
* Refactored Garbage and added .dispose to dispose single Elements and their childs (refs #100) 

      

Changed 1 year ago by digitarald


        
solved in r337 

                  Changed 1 year ago by digitarald

          status
              changed from new to closed
        
          resolution
              set to fixed

solved in r337 

          status
              changed from new to closed
        
          resolution
              set to fixed
        
      

Comments and changes to this ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

Shared Ticket Bins

People watching this ticket

Pages