Sadly, none of my wiquery components seem to work under 1.1.1. Previously, I
had to disable auto-import of jquery resources because I was having
conflicts with other jquery-based components (jgrowl, custom stuff). Maybe
that's why. I assume 1.1.1 is backwards compatible and setup is the same?
Anyway, tabs do work in *certain* places using 1.03. A panel with a broken
tab will work if placed on a different page/panel. (In other words, if I use
the app's cms interface to position the panel somewhere else). Once tabs
start working, they work everywhere in the application until logout. I can't
figure out what's different between the working and non-working instances of
the same panel. It's odd. I suppose I need to debug into wiquery and/or
wicket.
If I switch to 1.4.12, no problems at all.
-----Original Message-----
From: Brian Topping
Sent: Monday, November 29, 2010 3:48 PM
To: [email protected]
Subject: Re: Wicket 1.4.14 and WiQuery Tabs
Ah, great point. I am already using 1.1.1!
On Nov 29, 2010, at 4:34 PM, julien roche AKA indiana_jules wrote:
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
<[email protected]>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: [email protected]
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: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
