On 4 nov, 13:11, walden <[EMAIL PROTECTED]> wrote: > Joe, > > You don't need DOM events, per se. Use Observer Pattern. Your Login > module doesn't need to know who's subscribed. It just needs to > implement the Observable interface (register listeners, fire login > state change events). Your other modules are in fact dependent upon > Login. They need to know how to register listeners, receive events, > recognize Login events, and then I would suggest you let them probe > the Login module directly for login state. > > If you look at how ChangeListener and SourcesChangeEvents work in GWT, > there are all the elements of the Observer pattern you need, and you > can copy that.
Walden, he has and wants (and needs?) distinct *applications* (not only distinct *modules*), Java-GWT is not an option here. @Joe: you'll have to implement such an observer/observable pattern in pure JavaScript in your host page, and use JSNI in your applications to register handlers/fire events. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
