Its a great plugin, you say everything I was needing to hear... the absoluteley true... Im using livequery like regular bind calls and are happening thinks not planned... but I can´t find another way to do it...
Livequery becomes a dependency of the plugin that I was trying to develop... I need a complete ajax navigation... somethimes complex... this plugin need the live query... the livequery when I discover was to me a part of core of jQuery... How I can register this plugin... What means with right words "register a plugin"??? I think sometimes that I can enjoy more the plugin... im feeling that Im not using well or I can make it a substitute for bind calls since I make some precautions... its this precautions that Im falling... But the great problem its how decrease a performance... but I dont have a choose that not be a solution... I said that I could make and I'll have to do it... I dont know how my plugin used in a project of my work would survive without livequery... has a way to work with it without callhim everytime???? All in this project is ajax... theres no refresh at least the first load... it has to be this way, thats the original idea... This way I discover all the problem that cames with this idea and how to make it truth... I think livequery great, but my gift maybe gonna be my disaster... On 1 nov, 14:24, Brandon Aaron <[EMAIL PROTECTED]> wrote: > Perhaps you didn't see the example > page:http://brandonaaron.net/jquery/plugins/livequery/test/test.html > > Doing those same two examples without Live Query would require you to > write other helper functions to bind those events and to manually > monitor when an element is added or removed. Hardly just two lines of > code. Feel free to add an element to the list via firebug as well to > see how it works. > > I personally feel that Live Query should not be put in the core. To > many people seem to think it is a replacement for bind and perhaps > that is my fault for making it a little to easy. Remember that the > power comes at the price of performance. Live Query is best used on a > section of your web site that changes via AJAX calls and you need to > bind events or even just know when the change took place. There will > be absolutely no noticeable performance hit when using it this way. It > is when you start using Live Query in place of your regular bind calls > that you will start to see performance drop. > > Live Query should not interfere with any Ajax history manager nor any > hijax methodologies. Live Query is only calling .bind for you. > > Also Live Query doesn't make you lazy ... it simply abstracts a more > difficult task into one line. The only reason to suspect you've become > lazy is b/c you are a programmer and I believe we are all a little > lazy at times. :p > > Live Query is a very cool plugin but don't use it just b/c it is cool. > > BTW ... the adoption rate has been pretty good from my perspective. > > -- > Brandon Aaron > > On Nov 1, 10:09 am, "Lee Hinde" <[EMAIL PROTECTED]> wrote: > > > On 10/31/07, Yehuda Katz <[EMAIL PROTECTED]> wrote: > > > > So as far as I'm concerned,livequeryis 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 thatLiveQuery > > 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.
