gwt-platform have a better design for nested Presenters.
That's where nesting presenters becomes handy, because you would create a
upper layer presenter that has a content slot from every other presenters
to be shown in and only this one would have the header and the footer in
it. I always call
Ok, got your example going...
On Jul 21, 5:35 pm, Thomas Broyer t.bro...@gmail.com wrote:
(using @UiChild methods
to allow adding child widgets when you use it in another ui.xml template)
That's basically what I want. Is it also possible to declare some
methods abstract to change their logic
If you have a custom widget, e.g. MyPanel, you can do something like the
following in any other *.ui.xml file:
my:MyPanel
my:header
g:LabelHeader/g:Label
/my:header
my:footer
g:LabelFooter/g:Label
/my:footer
/my:MyPanel
Your Java implementation of MyPanel would then contain
On Friday, July 22, 2011 1:03:55 PM UTC+2, Alexander Orlov wrote:
class SuperClass {
// ..
static class Layout {
// ...
// put you @UiField, @UiHandler, etc. here
@UiField
Button test;
}
final Layout layout;
public
On Fri, Jul 22, 2011 at 1:22 PM, Jens jens.nehlme...@gmail.com wrote:
my:MyPanel
my:header
g:LabelHeader/g:Label
/my:header
/my:MyPanel
Your Java implementation of MyPanel would then contain methods:
@UiChild
public void addHeader(Widget w) {
//your add logic
}
Great,
