Check out the docs. https://developers.google.com/web-toolkit/doc/latest/DevGuideUiPanels
When should I *not* use layout panels? The panels described above are best used for defining your application's outer structure — that is, the parts that are the least "document-like". You should continue to use basic widgets and HTML structure for those parts for which the HTML/CSS layout algorithm works well. In particular, consider using UiBinder templates<https://developers.google.com/web-toolkit/doc/latest/DevGuideUiBinder> to directly use HTML wherever that makes sense. On Sunday, April 15, 2012 5:01:35 PM UTC-7, stagirus wrote: > > Pardom me for humanizing the all mighty SplitLayoutPanel. This panel seems > to be very powerful except that it is making itself unfriendly and useless > in the following scenario. > > In our application, we needed a vertical splitter (content in North and > South). We require the widget to spread out within its parent panel, by > calling splitter.setSize("100%", "100%"). But SplitLayoutPanel only takes > pixels (setPixelSize). Providing fixed pixel size is not an option for our > application. (Our custom built spitter is not properly functioning with > Standardards Mode enabled.) > > Why is SplitLayoutPanel forcing pixel sizes only and not supporting the > basic GWT design feature? Is there any work around for this problem? > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/3174niR4xoIJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
