I think what I'd be more interested is having a method that would allow me
to really easily *manually* re-apply effects/events to a jQuery object.
For example:
$('li')
.cache('some.name', function(){
// use the helper function hover to bind a mouseover and mouseout event
$(this)
.hover(function() {
$(this).addClass('hover');
}, function() {
$(this).removeClass('hover');
});
});
Now you could do:
$('li').applyCache('some.name');
Something like that would definitely save me some coding. (I'd allow a
manual cache "key", just so you could re-use the chain on other selectors.)
The benefit is you don't have the overhead of having to constantly monitor
the DOM, but you have an easy way to re-apply a bunch of commands to a
selector.
Right now I just use helper functions--which isn't hard, just not very
jQueryish. :)
Too bad there's no way to programmatically know the jQuery chain. It would
be really sweet to be able to do:
$('li')
.hover(function() {
$(this).addClass('hover');
}, function() {
$(this).removeClass('hover');
})
.cache('some.name');
And have the cache() method be aware of all the methods called in the
current chain.
-Dan
>-----Original Message-----
>From: jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED] On
>Behalf Of tlphipps
>Sent: Thursday, November 01, 2007 9:22 AM
>To: jQuery (English)
>Subject: [jQuery] Re: LiveQuery (Discuss Please)
>
>
>I'd like to second this opinion. I'm using livequery more and more,
>but there are plenty of places where I DON'T use it, so not having it
>in the core would still be my preference.
>
>On Nov 1, 5:53 am, James Dempster <[EMAIL PROTECTED]> wrote:
>> My less than one pence worth would be I love and use the plugin, but I
>> don't think it should be included into jQuery core, I would
>> like to see jQuery core stay light and fresh. There's nothing wrong
>> with adding LiveQuery yourself, either just add another js file to
>> your html or append all the plugins you want to the same js file.
>>
>> /James
>>
>> 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
>
