For my part, I've not been creating a 'createEditorDriver()' method, but instead 'getEditorDriver()'. This way, there is no concern about binding and traversing the tree more than once.
Am I in error with this approach? Each time my presenters get a ref to the driver and have finished loading data, they call driver.edit (or .display) which should get rid of the old requestcontext, set up a new editor delegate, etc. The existing eventbus/factory should still be good. The only concerns I had were for events that might have already been wired up, say from something implementing HasEditorDelegate, but it should be the implementing class's responsibility to clear out old registrations... Okay, so when (in either case) should those be cleared out? When setDelegate is called again? But what if it isn't called again – then do those subscribed events just keep going off? Or maybe take them out on .flush(), since you know then that "the Editor cycle is finished"? -- 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.
