Hi,
There is two type of layouts: RIA-like and web-page-like. The RIA-like
layout is done using the layout panels. The app stretch to the whole
available space. There is no scrollbars. The web-page-like layout is
done using HTML tags (and some standard panels). The app don't
stretch. If the content is larger than the viewport, scrollbars
appears, like in traditional pages.
Looking at the first screenshot, here is my proposal:
1) The main panel is a DockLayoutPanel attached to RootLayoutPanel.
2) The north slot contains the header.
3) The center slot contains a TabLayoutPanel.
But when you show data (list, form...) you may have no enough space to
show all. Here you start to use web-page-like layout. So:
4) The contain of the contact tab is a LayoutPanel with four slot:
Tighformat, the list, Detail view, Relations.
5) Tighformat, Detail view and Relations are standard panels
(FlowPanel) into ScrollPanels. If there not enough space, a scrollbar
will appear.
6) The list is some sort of DockLayoutPanel with the headers top, the
navigation buttons bottom and the contains of the list in the center
with a scrollbar is needed. The exact implementation depends on the
used widget for the list (SmartGWT, GXT, gwt-incubator...)
Hope this helps.
Think also to invert the color between selected tab and not selected
tab. When i saw the screenshot, I thinking that blue tabs are not the
current tab and white one are the current... The current tab must be
the lighter.
Olivier
On 16 juin, 17:48, ingo <
ingo.jaec...@googlemail.com> wrote:
> hello oliver,
>
> thank you very much for the link! i want to achieve a page layout
> similar to the google code uihttp://
code.google.com/p/honeycrm/:tabs
> on top of the screen and right under the tabs is the module specific
> content. if the content right under the tabs is too big the whole page
> or the content of the tabpanel component should have scrollbars.
>
> at the moment i do not really care where the scrollbars are - more
> importantly is that there are scrollbars at all :-)
>
> what do you mean with your suggestion to use a dockpanel instead of a
> docklayoutpanel? should this solve the problem, too? i tried and it
> did not work out for me.
>
> i will read the stuff in the docs and play around with the different
> containers. would really find a solution for this issue. has anyone
> some sample code that i can have a look at? in the meantime you can
> have a look at my code by browsing through the projecthttp://
code.google.com/p/honeycrm/source/browse/#svn/trunk/src/honeyc...