Hello,

If I understood your suggestion correctly it involves to markup files:
one - for the content area and another one - for the tab content.
However, I would like to use a single markup file for the entire page.

Did I understand your solution correctly?

Thanks

On Sun, Jun 13, 2010 at 8:04 PM, Jeremy Thomerson
<jer...@wickettraining.com> wrote:
> On Sun, Jun 13, 2010 at 8:54 PM, Alec Swan <alecs...@gmail.com> wrote:
>
>> Hello,
>>
>> I am working with a web designer who delivers a single HTML page which
>> should display a panel with arbitrary number of tabs. In the HTML the
>> tabbed panel consists of a <ul> list of links and the content of the
>> first tab. The content for the remaining tabs is loaded from the
>> database at runtime.
>>
>> I know how to implement tabbing using tab swapping or TabbedPanel.
>> However, both of these approaches require a separate panel object and
>> markup for the tabs. Instead, I would like to be able to use the HTML
>> page I received from the designer unmodified.
>>
>> Is there a way to create a WebMarkupContainerWithAssociatedMarkup
>> object which is mapped to a specific element on the page markup? If
>> so, can I implement tabbing by swapping such objects when tabs are
>> clicked?
>>
>> Any ideas would be appreciated.
>>
>> Thanks
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
> Just make the content area a panel, add links to each of the tabs, and in
> the onClick, call replace(...) with the panel that contains the content for
> that tab.  This will make each content area (for each tab) into a panel, but
> you will not have to modify the markup of the tabs themselves.
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to