Sounds like an awful lot of extra work to simply avoid learning CSS. Don't get me wrong, CSS is kind of clunky, but I find it hard to imagine that this new solution would be significantly more elegant.
-Ben On Feb 16, 8:31 pm, Kurtt <[email protected]> wrote: > GWT 2.2 introduces the Canvas, which is actually a 2D-API. This is > exactly what Java Swing is based on. And we can create a LooknFeel > class for GWT, which wraps a set of painting Canvas method. If we set > the app a certain LooknFeel, when a widget is showing , the widget > asks the LooknFeel to draw the UI for it according to its own state. > This is similar to how the Java Swing pluggable LooknFeel works. > > benefits are that, 1) apps don't need CSS to define the look. For pure > desktop-app developers like me, i find trouble in writing perfect > CSSs. 2) Further, this guarantees the unified look across platform, > while sometimes you have to write different CSS styles for different > browsers. 3) Canvas supports drawing in the vector way. Nimbus in > Swing is a LooknFeel based on vector-rendering. > > What do you think, guys? > > And, allow me to complain that the Canvas class under GWT 2.2.0 > removed the support for IE 6/7/8. Even though some few effects are not > displayed perfectly in IE and are 30x slower because the canvas tag is > actually simulated, I need the Canvas in IE 6/7/8. Cause in china, the > IE6/7/8 occupies a worth-noting market share (Microsoft executives: > China is IE6 die biggest obstacle:http://www.amieindia.net/ > viewtopic.php?f=244&t=15183). -- 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.
