Re: [jQuery] unload and unload

2006-12-13 Thread Andreas Wahlin
so no .click() then?

ANdreas


 The best thing to do is always use .bind(event, fn) for your  
 events. There
 is no ambiguity when you do that. Many of those confusing shortcuts  
 will be
 going away in an upcoming version.


___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/


Re: [jQuery] unload and unload

2006-12-13 Thread Karl Swedberg

On Dec 13, 2006, at 6:54 AM, Andreas Wahlin wrote:

so no .click() then?

ANdreas



The best thing to do is always use .bind(event, fn) for your
events. There
is no ambiguity when you do that. Many of those confusing shortcuts
will be
going away in an upcoming version.



I think the decision about what to do with the shortcuts has not been  
finalized yet.


Whatever happens to the other shortcuts, .toggle() and .hover() are  
going to stick around, because they're special cases. I'd be  
surprised if .click() went away anytime soon. It's just too quick,  
useful, and ubiquitous to get rid of it. Of course, none of these  
decisions are up to me, so take what I say with a grain of salt.  
However, a recent chat with John Resig led me to believe that .click 
() wasn't going to be relegated to a plugin, at least not in 1.1.


--Karl
_
Karl Swedberg
www.englishrules.com
www.learningjquery.com



___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/


Re: [jQuery] unload and unload

2006-12-13 Thread Aaron Heimlich

I think people were leaning towards removing the shortcuts from the core and
putting them into their own plugin, but I could be wrong about that.

--Aaron

On 12/13/06, Karl Swedberg [EMAIL PROTECTED] wrote:


I think the decision about what to do with the shortcuts has not been
finalized yet.

Whatever happens to the other shortcuts, .toggle() and .hover() are going
to stick around, because they're special cases. I'd be surprised if .click()
went away anytime soon. It's just too quick, useful, and ubiquitous to get
rid of it. Of course, none of these decisions are up to me, so take what I
say with a grain of salt. However, a recent chat with John Resig led me to
believe that .click() wasn't going to be relegated to a plugin, at least not
in 1.1.

--Karl
_
Karl Swedberg
www.englishrules.com
www.learningjquery.com




___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/




--
Aaron Heimlich
Web Developer
[EMAIL PROTECTED]
http://aheimlich.freepgs.com
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/


[jQuery] unload and unload

2006-12-12 Thread Markus Peter
Hello

I'm a bit puzzled by the existence of two unload functions in  
jQuery - one which is the unbinder for load, and one which is the  
binder for unload. Now, the way it's currently implemented, the  
unload event binder will probably simply overwrite the load  
unbinder, if I understand the source correctly?

I'm a bit concerned about what the behavior is which the API actually  
guarantees and which I can rely on?

-- 
Markus Peter - SPiN AG   
[EMAIL PROTECTED]




___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/


Re: [jQuery] unload and unload

2006-12-12 Thread Dave Methvin
 I'm a bit puzzled by the existence of two unload functions
 in jQuery - one which is the unbinder for load, and one
 which is the binder for unload. Now, the way it's currently
 implemented, the unload event binder will probably simply
 overwrite the load  unbinder, if I understand the
 source correctly?

The best thing to do is always use .bind(event, fn) for your events. There
is no ambiguity when you do that. Many of those confusing shortcuts will be
going away in an upcoming version.

Speaking of that, can we undocument those *now* but still leave them in
while the discussion goes on about what exactly will be removed?




___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/