http://blog.ehour.nl/index.php/archives/18
2009/10/16 Ding Zenberg <zenberg.d...@gmail.com>: > Hi all, > > We'll plan to use wicket in our application for one enterprise's > information management system. > > the app's portal layout is someting like this: > > ----------------------------------------- > | Header | > ----------------------------------------- > | | | > | | | > | Nav | Client | > | | | > | | | > | | | > | | | > | | | > | | | > | | | > ------------------------------------------ > | footer | > ------------------------------------------ > > When we use Wicket's layout way --> Orgnized everything into one page > using <child>, we found that it's reload everything ( header nav etc.) > everytime when click links in client area. > > Is there a nice way organize those pages in a ajax partial refresh way? > > For example , > > Nav and client are all represent by a separated *independent* page, > When click nav area, only refresh client area, (*Note* client area is > represent by a client Page, not a panel). > > Thanks. > > Zenberg Ding > > -- > Keep It Simple & Stupid. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
