Instead of a TabPanel you would just create HyperLinks with a custom style that looks like a tab and then define a display area where the original TabPanel contents would go to. If your TabPanel contents also contains different areas you would just define these as display areas. So instead of one display area containing for example 4 "sub display areas" you would just define 4 display areas and show/hide them as needed (to get an idea of it you could take a look at: http://95.110.143.4/layoutmvp/layoutmvp.html . It does a nice visualization of that idea. The example contains five display areas and shows and hides them depending on the place and needed application layout).
Or just take a look on the new Google Groups layout. It just gives you the same idea. On the top you have a navigation bar containing "E-Mail, Calendar, Text & Tables, etc"...basically links to different Google Apps. Thats what you wanted to do as TabPanel navigation. If Google would change the Css style it could look like a TabPanel although it isn't one. Below that navigation bar you see three main display areas: horizontal search area, side menu area and main content area. Thats the "TabPanel content" although its not a TabPanel. Imagine you click on Calendar and that app would not need a sidebar.. well..just clear and hide it. In that example each Google App would be a Place thus each "tab" would be a Place. How to deal with more then one display area can be read in Thomas's blog post about nested activities. Basically you will create one ActivityMapper per display area. I hope that helps you to understand how to deal with tab like navigations and Places/Activities. -- J. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
