Hi all,
Can you try tabs with the last release of wiquery ? (the 1.1.1). A lot of
changes and refactoring were don into the core. Maybe that will solved your
problems.
Can you give me your feedbacks please .
Thank you
Regards
Julien Roche
On Mon, Nov 29, 2010 at 9:33 PM, Brad Grier <brad.gr...@salusnovus.com>wrote:
> Okay, well...it's more than a contribution problem. It looks like the tab's
> associated div, ul and li tags do not get modified by wiquery in 1.4.14.
> WiQuery assigns classes to these tags (ui-tabs, ui-tabs-nav,
> ui-state-default, etc). Those are all missing when I run in Wicket 1.4.14.
>
> Since it works fine for you, I'm not sure where to look.
>
>
>
> -----Original Message----- From: Brian Topping
> Sent: Monday, November 29, 2010 2:04 PM
>
> To: users@wicket.apache.org
> Subject: Re: Wicket 1.4.14 and WiQuery Tabs
>
>
> On Nov 29, 2010, at 3:02 PM, Brian Topping wrote:
>
>
>> On Nov 29, 2010, at 2:39 PM, Brad Grier wrote:
>>
>> My tabs are on panels that get swapped in and out via ajax. Are you using
>>> this approach?
>>>
>>
>> They are ajax, but I haven't bothered looking at how it works. Here's
>> what I use in populateItem():
>>
>> mainContentPanel =
>>> cp.loadComponentInstance("mainContentPanel");
>>> mainContentPanel.setOutputMarkupId(true);
>>> AdminPage.this.replace(mainContentPanel);
>>> target.addComponent(mainContentPanel);
>>>
>>
> Erm, that should have been "what I use in my onClick()"...
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
