If ever introduce isXxx, I personally want them to be future proof. That might require deprecating some methods and introducing new ones. Also we can use this as an opportunity to provide a compatibility layer across different vendors and/or different widget systems.
In upcoming weeks, we will start talking more about improving UI+widget development in GWT. It is good to wait until that gets more concrete before introducing/changing any APIs. On Thu, Mar 21, 2013 at 2:15 PM, Stephen Haberman <[email protected]>wrote: > Hey, > > I've brought this up before, but if I put together a patch that added > IsXxx interfaces for all/most of the widgets (IsTextBox, etc.), > assuming the patch was otherwise fine, would the GWT team/other > contributors tend towards +1, -1, or +/-0? > > - Stephen > > -- > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > --- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit Contributors" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups "Google Web Toolkit Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
