David, Can you explain some of the benifits/drawbacks of using the RequestFactory vs gwt-dispatch. I haven't taken the time to really investigate the new RequestFactory, but currently I've got gwt- dispatch wired into my app, I'm just curious if the RequestFactory paradigm will be better for my current usecase.
-Jeff On Oct 8, 12:31 am, Rud <[email protected]> wrote: > Okay, got it to work but it feels ugly. > > In my 'east' I put a class SimpleDisplayUi which is a UiBinder class. > Its ui.xml just has a SimplePanel. > > The trick was in SimpleDisplayUi.showActivityWidget(IsWidget widget) > to do > > simplePanel.setWidget(widget.asWidget()); > > It seems there are two many layers from DockLayoutPanel to 'east' to > SimpleDisplayUi to SimplePanel and finally to the actual panel(s) that > can be changed. > > There are a Activity classes that seem superfluous like SimpleActivity > just to create SimpleDisplayUi. It doesn't get created or called. > > I'll look at cleaning this up but getting SimpleDisplayUi working was > painful so I'm not sure there is much leeway. Just look at its > declaration: > > public class SimpleDisplayUi extends Composite implements > SimpleActivity.SimpleDisplayUi, Display { } > > Rudhttp://mysticlakesoftware.com -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
