Hey Christoph, Thanks for the reference. It seems to me like this would be handled very well with a custom widget that goes through $.widget. You would run whatever setup you need to in the _init method and whatever cleanup/saving you need to in the destroy method. There are no plans to remove the automatic calling of destroy on widgets when they get removed from the DOM. I'd be interested to hear your thoughts on how that might make your development easier or harder.
On Sep 5, 7:14 am, Christoph Boget <[email protected]> wrote: > We use it for functionality similar to google pages. We have the > front end display and we keep and manipulate the configuration for the > page in memory (which is then later saved). By being able to bind > remove, we are better able to make sure the config is up to date with > what is on the screen. We have other, similar roll-your-own > functionality throughout and remove is quite helpful. > > thnx, > Christoph --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery UI" 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/jquery-ui?hl=en -~----------~----~----~----~------~----~------~--~---
