Re: [jQuery] Tabs plugin callbacks - what makes most sense?

2006-11-27 Thread Glen Lipka
$('...').tabs({ onClick: function(clicked) { if (clicked == particularTab) { // do soemthing } } }); Having trouble with this. How can I tell what is clicked? I have ID's to differentiate the tabs. Shouldn't I use show instead click anyway? $(this) is

Re: [jQuery] Tabs plugin callbacks - what makes most sense?

2006-11-23 Thread Klaus Hartl
Glen Lipka schrieb: http://glenlipka.kokopop.com/jQuery/tabs/# I'm thinking about extending the callback system in the Tabs plugin to not only allow one callback, but different ones for more flexibility: On My latest prototype using tabs:

Re: [jQuery] Tabs plugin callbacks - what makes most sense?

2006-11-23 Thread Klaus Hartl
Matt Grimm schrieb: I'm a big fan of this idea, Klaus, and even made a first attempt at integrating my own pre-callback. It's useful to me because I am dynamically loading (via AHAH) the content of each tab and I want the content to load before the tab actually makes the switch. As it is, the

Re: [jQuery] Tabs plugin callbacks - what makes most sense?

2006-11-23 Thread Matt Grimm
: [jQuery] Tabs plugin callbacks - what makes most sense? Matt Grimm schrieb: I'm a big fan of this idea, Klaus, and even made a first attempt at integrating my own pre-callback. It's useful to me because I am dynamically loading (via AHAH) the content of each tab and I want the content to load

[jQuery] Tabs plugin callbacks - what makes most sense?

2006-11-22 Thread Klaus Hartl
Hi all, I'm thinking about extending the callback system in the Tabs plugin to not only allow one callback, but different ones for more flexibility: onActivate (invoked on click), onHide (invoked after old tab got hidden), onShow (invoked after new tab is revealed == callback as is now).

Re: [jQuery] Tabs plugin callbacks - what makes most sense?

2006-11-22 Thread Klaus Hartl
Klaus Hartl schrieb: Jörn Zaefferer schrieb: I'm thinking about extending the callback system in the Tabs plugin to not only allow one callback, but different ones for more flexibility: onActivate (invoked on click), onHide (invoked after old tab got hidden), onShow (invoked after new tab

Re: [jQuery] Tabs plugin callbacks - what makes most sense?

2006-11-22 Thread Olivier Meunier
Hi, Klaus Hartl wrote: Besides with simple binding it is not as easy to get the elements that are worked with... instead of having them as arguments already you would have to do some :hidden and :visible checks, so I think the callbacks make some sense. I wrote my own tab JavaScript code

Re: [jQuery] Tabs plugin callbacks - what makes most sense?

2006-11-22 Thread Matt Grimm
div (rather unattractive), then the content loads and pushes the div into shape. m. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Klaus Hartl Sent: Wednesday, November 22, 2006 3:26 AM To: jQuery Discussion. Subject: [jQuery] Tabs plugin callbacks

Re: [jQuery] Tabs plugin callbacks - what makes most sense?

2006-11-22 Thread Glen Lipka
http://glenlipka.kokopop.com/jQuery/tabs/# I'm thinking about extending the callback system in the Tabs plugin to not only allow one callback, but different ones for more flexibility: On My latest prototype using tabs: http://glenlipka.kokopop.com/jQuery/tabs/# I want to actually run