I think you're misunderstanding how GWT works. Everything written using GWT compiles down to HTML, CSS, and other "native" web technologies - there is no difference between panels (LayoutPanels or otherwise) and widgets as far as "mapping" goes.
What seems to be the issue here is that the abstraction provided by GWT can be rather leaky. If you don't understand what the generated code looks like and how it is rendered, then you will likely run into problems. For example, the HTML markup you posted previously contains an empty, (presumably) statically positioned DIV - this is rendered by the browser as an element with zero height. It's not a problem with GWT per se; if anything, the problem is that your expectations don't match those of the framework. It's also worth noting that while GWT offers fairly reliable abstractions for some things (e.g. basic layout, scripted behaviors), it does not eliminate the need to understand how CSS influences presentation. What it does do is provide mechanisms for cleanly separating browser-specific requirements, so that you or someone else can do the hard work just once and have it available for re-use in the future. -- 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/-/Lmq_d16h2VQJ. 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.
