I'd go straight to what I want to do. I have 3 composites in 1 panel, in 1 entrypoint. I have another entrypoint that pops up when you click a link on the 2nd composite on the 1st entrypoint. on that second entrypoint you can configure stuff, that will affect the displayed data on the first entrypoint's composites. now, im thinking (actually, a friend thought of it, not me) that the observer pattern is great to use in here, as the 3 composites of the 1st entrypoint will listen to whatever the second entrypoint configures, then change themselves according to the specified configurations on the second entrypoint.
Currently, I do the changes on the first entrypoint's composites by calling their static classes (from the second entrypoint's clicklisteners and stuff) that configures them, which I think is not a very good practice to implement because it's not easily extensible and not that good of a design. Now, is it wise to use the observer pattern(personally, I think it is)? If yes, how do you implement that on GWT 1.5? (we use GWT 1.5.2) thanks in advance mives29 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
