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

$('...').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 t

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

t: Re: [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 ta

Re: [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 before the tab actually makes the switch. As it is,

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

Glen Lipka 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: > >>> > > > > > > On My latest prototy

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

>>> 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 ac

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

e tab switches to an empty 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] T

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

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 co

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

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

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

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 is revealed =

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

> 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). > >

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

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). First