I don't think adding/removing is any more costly than showing/hiding, but
even then, you could make it work that way (show/hide) by simply providing
a DeckLayoutPanel (or an AcceptsOneWidget wrarpper around a DeckPanel). The
problem with such an approach is when your activities don't reuse
Tx, appreciate the response.
Alfredo
On Sun, Feb 5, 2012 at 11:19 AM, Thomas Broyer t.bro...@gmail.com wrote:
I don't think adding/removing is any more costly than showing/hiding, but
even then, you could make it work that way (show/hide) by simply providing
a DeckLayoutPanel (or an
Hello All:
I had a quick question regarding the implementation of Activity Places.
During the implementation of AP, specifically when working with the
activity, one overrides a method:
public void start(AcceptsOneWidget panel, EventBus eventBus) {
As seen above, the interface indicates that
