I use both. My goal is to be IE8+ compliant, so many problems go away. Then, for others, I use GWT to avoid writing CSS hacks.
Be aware that Panels are for Quirks Mode and Layout are for Compliant/ Standard Mode. In the first mode, browser have many differences, which Panels try to correct. In the second mode, there are, for recent browser, less differences. I always write my pages as XHTML (strict if possible) so I don't need many GWT complex component. Finally, for website, I never use Panels like Stack, Dock... because its not for website, it's for app. That the reason there must be replaced by there Layout counterparts. Olivier On 27 mai, 09:51, googelybear <googelyb...@gmail.com> wrote: > I also prefer to do the styling with CSS and not via gwt methods. But > I still use the panels as one of the strengths of gwt is that it knows > best how to create them in a cross-platform/ cross-browser way and > deals with the browser differences for me (at least in theory). I then > just style them with CSS to look the way I want. > If I would implement everything with html tags I would have to deal > with browser differences again and start implementing browser hacks > which I want to avoid at all cost. What do you think? > > Dennis > > On May 26, 10:06 pm, Olivier Monaco <olivier.mon...@free.fr> wrote: > > > When I want to create a website like app, I use as many HTML tags as > > possible with UiBinder. Then, I use CSS to sets the position, border, > > color... and never the GWT methods. That way, I have a true web site > > but using GWT. I don't like to create a website-like app (something > > that looks like a web site but with widgets like in app): you want a > > website (HTML + CSS) or an app (Widgets + Layout). > > > Olivier > > > On 26 mai, 13:53, googelybear <googelyb...@gmail.com> wrote: > > > > Are you not afraid that they will get removed soon? > > > I always get deprecated warnings when using them: "StackPanel is > > > deprecated. Use the StackLayoutPanel instead." and same for others > > > (DockPanel, TabPanel, ...). > > > > What's the official policy on this? > > > > On May 26, 11:49 am, Olivier Monaco <olivier.mon...@free.fr> wrote: > > > > > For a "traditionnallayout", I use the "old school"panels. It's not > > > > really a old school, it just has another goal. > > > > > Olivier > > > > > On 26 mai, 10:33, googelybear <googelyb...@gmail.com> wrote: > > > > > > Hi, > > > > > > I am developing a webapp that should "behave" like atraditionalweb > > > > > page, meaning that when the content grows in height the browser should > > > > > display a vertical scroll bar. Unfortunately I was foolish and jumped > > > > > right in on the new, shinylayoutpanels. As I found out later these > > > > > are not suitable for me, as they create a more "application-like" look > > > > > and feel with scrollbars displayed in the individual gwtpanels > > > > > instead of the browser (try resizing e.g. google wave -> When the > > > > > available area is too small scrollbars will appear inside all the > > > > >panels, the browser will never display any scrollbars) and also they > > > > > are working with lots of fixed sizes (in my case the content is > > > > > dynamic). > > > > > I tried toachievethetraditionalbehaviorwith my LayoutPanels but > > > > > failed. I couldn't get the browser to display scrollbars, only inner- > > > > > panel scrolling, and stuffing a layoutpanel inside a scrollpanel is > > > > > not the desirable approach (stuffinglayoutpanelsinside non-layout > > > > >panelsusually ended badly for me..). > > > > > So my conclusion is to revert to the "old school"panels. But I am > > > > > afraid that support of these will be dropped soon. What do you think? > > > > > Are there better alternatives? Anyone fought with a similar problem? > > > > > > thanks for any suggestions, > > > > > Dennis > > -- 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-tool...@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.
