... and the advantage over the thomas' pattern is that you can incject
any UI implementation form outside withouth defining subclass of the
widget. and it can be implemented WITH or WITHOUT uibinder or even
attached to existing DOM Nodes. - read comments in the example above.
--
You received this
Alex,
DefaultUI.ui.xml and SomeSubClass.ui.xml are not needed for anything
in that example. You should provide
dp.verp.planer.client.ExampleUiBinderWidget.ui.xml and
dp.verp.planer.client.SomeSubClass.ui.xml instead, where
"dp.verp.planer.client." is the JNDI path to your templates (e.g. they
sho
Hi,
I used to apply similar pattern as Thomas bt with some remarkable
difference.
here is the example to illustrate the differences and the concept
itself - it's quite simple and not show all possible combinations but
i think it's just enough for "getting started communication" - if you
were intere
Hi,
I used to apply similar pattern as Thomas described. But with some
differences that are worth to be mentioned.
class SomeUiBinderWidget extends Widget {
public static interface UI {
}
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" grou
