I'd cast my vote for leaving it out of core for now. The beauty of jQuery is
the leaness of the core. I've had my eye on LiveQuery for quite some time
but haven't had a chance to put it into practice for our enterprise toolkit.
Performance is a major concern but of greater issue is the inconsistency
within our organization for jQuery code. I fear too many developers would
just use it as a replacement for bind and with the level of dom manipulation
that we do the performance hit would be too much.
Again let me state that this is not reflective of jQuery or LiveQuery but
the browser limitations and the sheer size of data we internally have
to deal with on a single page.
I would theorize that the majority of jQuery users have onReady event
binding. For those that have dom manipulation it's probably pretty light and
thus the benefit of LiveQuery isn't realized.
Cheers,
-Jonathan
On 10/31/07, 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
