Ashton, if you have a List of items in the West Region, and are going to display the details of each item in Center Region (upon selection from the list in west region),
do you think we are going to need One Place or Two Places ? how about Activities ? One Activity or Two Activities ? I think we need One Place:for example CatalogPlace, and then map this CatalogPlace to Two Activities ItemListActivity and ItemDetailsActivity ItemListActivity and ItemDetailsActivity are managed by two different ActivityManagers. we can use WestRegionActivityMapper to map CatalogPlace to ItemListActivity and use CenterRegionActivityMapper to map CatalogPlace also to the ItemDestailsActivity however, with every selection from the itemList (in the west), as we navigate to a new place (to display the details in the center region), the ItemListActivity is again called by its ActivityMapper, resulting in data from the list being reloaded. I am also thinking we need to use CachedActivityMapper/ FilteredActivityMapper as Brian mentioned. but i am not sure. regardless, what do you think is the best approach in implementing the use case described above with GWT MVP 2.1 Activities and Places ? -- 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.
