I think the best (the most consistent) way is to implement wrapper objects
for HTML elements that would contain references to raw DOM objects and
access the elements through these objects. This is the way most js libraries
deal with that AFAIK.
--
To view archived discussions from the
On Tue, Feb 22, 2011 at 3:30 AM, RobG rg...@iinet.net.au wrote:
On Feb 22, 12:09 pm, Diego Perini diego.per...@gmail.com wrote:
Mark,
use event delegation and only setup one listener on the document
for the type of event you want notifications.
And for those events that don't bubble?
In
On Feb 22, 9:45 pm, Diego Perini diego.per...@gmail.com wrote:
On Tue, Feb 22, 2011 at 3:30 AM, RobG rg...@iinet.net.au wrote:
On Feb 22, 12:09 pm, Diego Perini diego.per...@gmail.com wrote:
Mark,
use event delegation and only setup one listener on the document
for the type of event
On Feb 22, 8:19 am, Mark McDonnell storm.m...@gmail.com wrote:
Hi there,
I need help understanding the Adapter design pattern so I can help
standardise the API usage on a library I'm working on.
Let me clarify that I mention the Adapter design pattern but if there is
another way to do
On Feb 22, 12:09 pm, Diego Perini diego.per...@gmail.com wrote:
Mark,
use event delegation and only setup one listener on the document
for the type of event you want notifications.
And for those events that don't bubble?
--
Rob
--
To view archived discussions from the original JSMentors