Except you forgot to mention that JQuery's Themeroller doesn't display properly on IE (not that I have anything against JQuery--a great library, but the things you are pointing out don't look as nice or as intended on the most popular browser, so that alone can make it undesirable in many cases).
On Feb 20, 9:29 am, CJ Wilks <[email protected]> wrote: > Geraldo, that Eric Meyer post is fantastic, most importantly because > he wrote it, and so perhaps people will listen and do something about > it. > > Certain GWT uses of tables are clearly an abomination (e.g. > DecoratorPanel, DialogBox). There is no need to introduce a table and > 9 cells, when other kits like jquery-ui's Themeroller are doing the > same thing with CSS -- for example see .ui-corner-all > athttp://docs.jquery.com/UI/Theming/API#Corner_Radius_helpers > > See it in action athttp://jqueryui.com/themeroller/-- fyi, since the > jquery theming api is well documented, there's no reason you can't > apply the same style classes to GWT widgets. > > On the other hand, sometimes tables are the simplest tool for the job. > I am working on a GWT layout that needs to be 3 columns (33% each) at > times, and 2 columns (200px + remainder) at other times, depending on > which UI elements are present onscreen. I was trying to make it work > by applying YUI Grids but the css became too complicated. Some > browsers rendered it fine and others would push the righthand column > downscreen. More importantly the markup was full of nested divs > sprinkled with yui-gb and yui-u and yui-b and doc3 lots of other css > junk that I won't remember next week. > > On Feb 18, 2:27 pm, Geraldo Lopes <[email protected]> wrote: > > > José Vicente, > > > Please read this: > > >http://meyerweb.com/eric/thoughts/2009/02/17/wanted-layout-system/ > > > Hope this helps, > > > Geraldo > > > On 18 fev, 07:44, Zé Vicente <[email protected]> wrote: > > > > Hello All, > > > > I am currently developing an application with GWT. It has all I need > > > in order to create a smart/dynamic user interface. But I just would > > > like to start a discussion about the usage of Grid, FlexTable, > > > Vertical Panel, HorizontalPanel and all other component in GWT that > > > generates after the compilation HTML Table structures. When I started > > > my developing I did use a lot those components. But today, I can > > > create my layout organization only using the FlowPanel component which > > > generates a HTML <div>. By using FlowPanel and CSS I can build my > > > layout and place my fields, images, links where I want. > > > > Now I only use GRID, FlexTable when I really want to display a search > > > result. That is the goal of Tableless right? > > > > This is my feedback: > > > > I found out that is much more easy and fast to use FlowPanel + CSS to > > > build layouts than any other GWT components. I only use GRID, > > > FlexTable and similar when I am displaying a real "Grid". > > > I chose FlowPanel to organize my layout because it generates after the > > > compilation a <div> element. If I add CSS to it, I can do whatever I > > > want with my layout without changing the Java code. > > > > What I expect from the community: > > > > 1. I would appreciate if you can share your experience in terms of > > > layout organization with GWT and the usage of Grid, FlexTable, > > > Vertical Panel, HorizontalPanel components in your code. > > > 2. Are there others developers with similar strategy: FlowPanel + CSS? > > > 3. Does anyone know if GWT can be faster if it has to build a layout > > > with less <table> tags? > > > > Thank you in advance. > > > José Vicente --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. 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 -~----------~----~----~----~------~----~------~--~---
