> Widgets written as current generation of GWT widgets in java vs
> native js widgets (e.g. closure)

Oh, cool. That sounds nifty. I assume that would benefit from
some of the future JS integration improvements? I hadn't thought
about that.

> I hit this problem in new Listbox style that is currently in use by
> Google. Changing the previous internal widget already written around
> appearance pattern was not feasible to adapt to new style due the
> behavior put in to the widget itself that is assumed to be common.

Yeah, makes sense; I was skeptical the appearance pattern would allow
as much reuse as was hoped. As you said, whatever assumptions are made
in the widget, you're stuck with.

> Of course there are benefits to testability as well (isn't that why
> you want to add IsXXX interfaces?).

Yep.

> However, important part of modernization of current widgets in GWT is the APIs
> and themes.

It seems like the APIs could be evolved from what we have now; I assume
it would mostly be adding new/useful methods and not removing old ones.

Themes, I dunno, my take is:

* If you have ListBoxImpl, and try to make ListBoxImpl theme-able by
  using the appearance pattern, or somehow abstracting which
  markup/CSS it uses, it will end up being complicated and have too
  many assumptions in the markup/CSS/features anyway.

Contrast with:

* If you have IsListBox, and make it "theme-able" by deferred binding
  to either ListBoxImpl or ListBoxBootstrapImpl (which may or may not
  share code), then the impls should be fairly free to do whatever they
  want with CSS/markup.

...perhaps this is exactly what you're thinking of? I hadn't really
thought about the theming before.

Seems like if we/I added IsTextBox for TextBox, we could come in later
and add a layer of indirection for deciding which TextBox impl to use
when users asked for an IsTextBox?

- 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.


Reply via email to