|
This, like Behavior.js, can be viewed as nice
and elegant. However, I much prefer the control of defining event handlers
manually. One of my biggest reasons is for proper disposal of the event
handlers when they are no longer needed. I write applications where each “widget”
is an autonomous entity, capable of making it’s own server requests, so
my “pages” can remain un-refreshed for an arbitrarily long period
of time. Behavior and event:Selectors provide a
nice way to attach event handlers in bulk to a group of elements, but I can’t
rely on the page refreshing to cleanup that memory… so I just make sure
all my DOM elements are uniquely IDed and keep my event handlers in object
variables for proper disposal during subsequent “widget”-level
redraws (callbacks). </my2cents> From: This looks quite nice at first glance.. I would love to hear some of your comments pro or con on how
this compares to Behavior. ______________________________________________________________________ Alex Duffield . Principal . InControl Solutions . http://www.incontrolsolutions.com The information transmitted in this electronic mail is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers. |
_______________________________________________ Rails-spinoffs mailing list Rails-spinoffs@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
