wicket-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Grigorov <mgrigo...@apache.org>
Subject Re: PagingNavigation extension
Date Sat, 03 Dec 2016 11:51:18 GMT

think org.apache.wicket.markup.html.navigation.paging.PagingNavigator#newNavigation()
should be improved. At the moment it is not possible to return different
component than PagingNavigation.
It would be better if the return type is more general, like Component or at
least MarkupContainer. Then the application developer can override it and
return a Panel with completely custom content, like in your case.
Please file a ticket for this!

The easiest workaround I see is to subclass PagingNavigator:

protected void onInitialize() {
  super.onInitialize(); // this will create the default "navigation"

   replace(new MyPanel("navigation")); // this will replace it with your
panel which will have textbox and whatever else is needed.

Martin Grigorov
Wicket Training and Consulting

On Fri, Dec 2, 2016 at 1:48 PM, ssamarin <stepan.samarin@gmail.com> wrote:

> Hello,
> I'm trying to change PagingNavigation: current page of navigation is a
> not-clickable number by default. I'd like to have textbox instead.
> Straightforward solution seems to be overriding method
> populateItem(LoopItem
> loopItem) from PagingNavigation class.
> But so far I have not figured out how to distinguish link to the current
> page from other links.
> Would appreciate help/ideas.
> Regards, Stepan.
> --
> View this message in context: http://apache-wicket.1842946.n4.nabble.com/
> PagingNavigation-extension-tp4676353.html
> Sent from the Users forum mailing list archive at Nabble.com.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message