you can replace any panel with any other panel. so maybe instead of modeling your app as pages you can model it as panels
-igor On Wed, Apr 16, 2008 at 11:57 AM, byhisdeeds <[EMAIL PROTECTED]> wrote: > > > > igor.vaynberg wrote: > > > > tabbed panel is meant to be used with panels not with pages. so > > instead of having each tab be its own page, simply make it each own > > panel. > > > > -igor > > > yeah, I get that. But I need to be able to replace the common panel area > being set by any of the tabs with content from a page not linked to the tab > component. I also need to be able to save the selected tab state across > these occurances. I don't seem to be able to do that. > > John > -- > View this message in context: > http://www.nabble.com/Shared-tab-component-across-pages-tp16722526p16730793.html > > > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > 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]
