As far as I cel tell LiveQuery runs every time the DOM is modified,
adding extra overhead to the already slow DOM operations (This isn't
jQuery or LiveQuery's fault, it's just a fact of web development that
manipulating the DOM is slow). If you can get away without using
LiveQuery then it's best to from a performance point of view. Don't
get me wrong, LiveQuery is great, you just hace to remember that its
power comes at a price, and tha price is high enough to justify
keeping it as an optional plugin.
On Nov 1, 2:04 am, "Yehuda Katz" <[EMAIL PROTECTED]> wrote:
> So as far as I'm concerned, livequery is the biggest advance in jQuery since
> its inception (no, I am not its author). I'm trying to understand why it's
> having such a slow rate of adoption.
>
> it solves this problem:
> $("div.klass").draggable();
> $("#foo").load("url", function() { $("div.klass").draggable(); });
>
> beautifully, as you now only need to do:
>
> $("div.klass").livequery(function() { $(this).draggable() });
> $("#foo").load("url");
>
> Obviously, that was only a simple example. The more general case, wanting to
> bind some event handler to a selector regardless of when it appears on the
> page, is extremely common. So again, I'm trying to understand why the rate
> of adoption has been so slow. Any thoughts?
>
> --
> Yehuda Katz
> Web Developer | Procore Technologies
> (ph) 718.877.1325
