> If you create a Is* widget like IsButton you have to think about when
> to create the contains Widget variant like the Button class.
No, for the simple case (that I am proposing anyway), it's just:
class Button implements IsButton {
// nothing else changes
}
So no lazily creation/delegation of methods/etc. At least in the
default widgets. If you want to do that with your own wrappers, that is
fine.
> I buffer it, such that I can run these operations in unit tests (not
> GWTTestCase...
The simpler thing than buffering is just to have a StubButton, e.g.:
class StubTextBox implements IsTextBox {
private String currentValue;
// get/set/etc.
}
Then you just need a factory/something somewhere, "newButton" that in
GWT code returns real Buttons and in test code returns StubButtons.
Tessell already has stubs for most widgets; I was going to explore
moving to GWT proper as well, after/if the widget interfaces are
accepted.
- Stephen
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
---
You received this message because you are subscribed to the Google Groups "GWT
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
