My example was shorthand for the problem that's being solved. LiveQuery
allows you to define behaviors on the DOM that will be applied on current
*or future* nodes. It basically takes the selector engine from being a
snapshot tool to making the DOM "alive", just like CSS (in CSS, if a class
is removed, all styles are removed; with liveQuery, if a class is removed,
all associated behaviors are removed).
Also, re: liveQuery breaking Hijax: can you give some more detail about why
this is the case?
Finally, use in every single app is not a requirement for inclusion in the
Core. There are a number of features that are not ubiquitously used, but
represent extremely common usage patterns, and are in use in a large number
of apps (think getJSON, for instance).
-- Yehuda
On 11/1/07, Lee Hinde <[EMAIL PROTECTED]> wrote:
>
>
> 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");
> >
>
> Since this is an evangelism discussion, I'd suggest that LiveQuery
> page doesn't explain the problem it solves. And your sample takes two
> lines of code and reduces it to two lines of code. That's not, in and
> of itself, compelling.
>
> A lot of us beginners don't get what itch is getting scratched. The
> specific suggestion would be to update the Live Query page with an
> introduction as to why the plug-in is useful, with an emphasis on DOM
> changes via Ajax calls.
>
--
Yehuda Katz
Web Developer | Procore Technologies
(ph) 718.877.1325
