maybe adding some event delegation to LiveQuery could improve its
performance.
Ariel Flesler
On 21 nov, 22:46, alexanmtz <[EMAIL PROTECTED]> wrote:
> This is the best discussion that I met about livequery... Im the one
> who loves it at beginning, now the plugin at reacting of weird ways...
> Its a great plugin and necessary, but in a large project with ajax it
> becomes a tricky... Now I dont know what I can do... when I test a
> site that uses it for all ajaxs, I see in firebug the amount of
> scripts duplicates and gives a lot of machine performace and makes
> javascript heavy... And Im think, theres something wrong with the
> system or its the livequery plugin...
>
> I hope we can find a way to make it work for a log ajax navigation
> like a project that Im working...
>
> This project act with a php framework that load the js especifically
> in body for each page... but sometimes with the use of another plugins
> and in some situations that I can detail because its normal situation
> theres a lot of ajax request per time... Im really lost in it...
> jQuery its my work and I was dreaming with that... but when we deep
> into aplications that rely of ajax and go against browsers layws... im
> completely lost...
>
> I have a function to make all ajaxs requests... this functin makes a
> link work with ajax automatically... its a plugin that I dont have a
> way to rebind events in another way at least livequery... My plugin
> have a dependencie of that...
>
> On 1 nov, 14:16, "Yehuda Katz" <[EMAIL PROTECTED]> wrote:
>
>
>
> > 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- Ocultar texto de la cita -
>
> - Mostrar texto de la cita -
