On Fri, Feb 25, 2011 at 12:34 PM, Stephen Haberman <[email protected] > wrote:
> > > Please take a look at the design doc and let me know what you think: > > Out of curiosity, would this allow Panels (all the way up to RootPanel) > to render their initial contents/major changes as one giant SafeHtml + > set innerHTML operation, CellTable-style? > We're working toward that. We could add support for Cells in HtmlPanel, such that a UiBinder backed HtmlPanel containing only HTML and Cells would render as a sstring. > > If so, that seems pretty slick. > > - Stephen > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > Which is true, but I don't think the Appearance pattern will alleviate > this? E.g. if ButtonCell's default appearance outputs a certain DOM > structure (whether by SafeHtml/otherwise), aren't users' apps going to > couple themselves to the resulting DOM structure, either via custom > Element-based hacks, or CSS rules that use selectors based on the DOM > output? > Seems like you'll still end up with DefaultAppearances that can never > change? We can add a new appearance and maintain (or deprecate) the existing DefaultAppearance. The behavior would depend on the constructor that the user uses. ButtonCell(); // The default appearance would be replaced ButtonCell(Appearance); // The user specified appearance remains ButtonCell(DefaultAppearance.Resources); // The user continues to use the old DefaultAppearance -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
