My app has the following layout.. ---header--- --searchbox-- W1, W2, W3 W3 ----W4----
Where W1-5 are widgets, just like on Google Desktop. Using the searchbox basically updates the widgets with results depending on what widgets are mean to show. And yes, user can hit the back button and get back to his previous search. So not only I would need to keep search terms in the URL history but also some widgets settings like page #, chart view vs plain view etc. I plan to make widgets as plain GWT implementations and I do not plan to use UI binders. I am clear about the use the EventBus here but... What should be my strategy for this in terms of - what places do I need? (1 for every widget and searchbox)? - what all activities would I need? (one for each widget, searchbox AND one for the main activity)? - how about activity mappers? I see a note in bottom about Composites, here http://code.google.com/webtoolkit/doc/trunk/DevGuideMvpActivitiesAndP... but is that the best design pattern in this case? thanks in advance... -KD -- 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-toolkit@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.
