I agree, and it would have been better name Text or TEXT to match the setText() methods and to go in parallel with the HTML widget. But bad choice of names is impossible to fix once they are done, and anybody who's ever written an API knows that we all get them wrong from time to time.
There's no issue with divs or how the Label widget works, just that the when writing widgets for HTML-based solutions, Label would have mapped nicer to <label>, and a Text widget would have mapped to an HTML-escaped widget that just contains text (and not markup). That's just my 2 cents. I built my own simple widgets using GWT, so it's not like it can't be done, just that it's not out of the box. No problem at all really, just part of the learning curve. But I do love GWT, and once the holidays are over, I'll investigate SmartGWT further to determine if its widgets are nicer to work with for building business apps. Then the real question is do I deal with proprietary SmartGWT PRO/EE or just stick with the LGPL version and GWT-RPC to plug into their DataSource scheme. It's just not clear to me yet whether SmartClient folks are really committed to GWT since much of their toolset is still JS-based (like ExtJS). But that's another topic entirely <smile> -- 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.
