"ActivityManager always calls setWidget(null) in between activities, but just in case...)"
Its great that 2.1provides this intercept capability however I'm now unclear as how to present a glass panel in the new activity if the dom is already cleared before I get there. Am I missing something about this new pattern? Thanks. David On Nov 17, 9:14 am, Thomas Broyer <t.bro...@gmail.com> wrote: > On 17 nov, 09:23, Baloe <nielsba...@gmail.com> wrote: > > > Thanks for the tips!! I'll look into the EagerSingleton. > > > However, regarding the class Root: I don't really want to change it, I > > want to remove it completely. It's not necessary for anything at all, > > it's just because we need to start the code. This program goes to our > > default Place (see getDefaultPlace() call in the code) , the class > > Root is 100% unncessary fill-in code, and extremely ugly as well. How > > can I get rid of it? > > Currently, you can't, there's no "SimpleLayoutPlanel" (and I can't > find an open issue, so feel free to file one) > > BTW, shouldn't you always clear() your Root panel? (ActivityManager > always calls setWidget(null) in between activities, but just in > case...) -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
