> > > Adding getTextBox() only changes things by giving them access to the one > that we create if they don't provide their own, right? And it means that we > have no option to change the implementation in to one that doesn't use a > text box--right now we're "allowed to" if they use the default constructor. > > I suppose I just said that I vote against the accessor. What problem is > being solved by adding it >
Yep, but I think I disagree with your reasoning. In that if we ever did want to have a suggest box that was not backed by a text box, I think we would want to create a new widget, because we would break a lot of user expectations. > >> >> >> -- >> "There are only 10 types of people in the world: Those who understand >> binary, and those who don't" >> >> >> > > > > -- "There are only 10 types of people in the world: Those who understand binary, and those who don't" --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
