Re: Proposal: TabbedPanel variant that does all the work on the client

[Ernesto Reinaldo Barreiro <re...@gmail.com>]

>From time to time I have seem people asking for similar functionality... I
would add it to the wiki with a brief explanation (example) of how to use
it... or create a jira issue asking it to be included on the framework.. or
both of them.

Thanks for sharing!

Ernesto

On Fri, Nov 6, 2009 at 1:59 PM, spam2008@meeque.de <sp...@meeque.de>wrote:

> Hello Everyone,
>
>
> I'm pretty new on this list and I don't know if this is the right place
> for such contributions. However, I recently developed a subclass of
> TabbedPanel (from wicket-extensions) that IMHO may be useful for others,
> so I'd like to share it.
>
> The main idea is that it's a drop-in replacement for TabbedPanel, but it
> does all the work on the client side. That is, all the tab contents are
> preloaded, and the user can switch between the tabs using client-side
> JavaScript only. No additional HTTP Requests involved.
>
> The good thing is, that this fits in really neatly with all the other
> TabbedPanel stuff. My new class ClientSideTabbedPanel is only a few
> lines of Java and JavaScript code, and no markup. But it still supports
> fallback, if JavaScript is deactivated.
>
> The main benefit of ClientSideTabbedPanel is that it is more responsive
> when switching tabs. It may also be better in terms of search engine
> optimization, since all the tab-contents are being indexed in one page.
>
> You can see it in action here for instance:
> http://www.airline-direct.de/fluege/nach/London-LON
>
> So, how can I share this? Should I just post the code to this list?
> Anyone interested at all?
>
>
> Regards,
> Michael Riedel
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>