I know 2.1 doesn't include any effort at linking the new frameworks together, but it seems that there were some ideas thrown around before feature freeze. Specifically, I've stumbled upon various classes that were once commited as part of the Expenses app (com.google.gwt.samples.expenses.client.place) and have subsequently been removed. I'm taking a look to see if I can borrow some ideas for my own application, and would appreciate a little guidance.
- Was there a fundamental problem with this approach that caused it to be abandoned or was there just not enough time to finalize and hammer out the details? - Is there any sample usage of these classes at any time that I could look at in previous commits? It's a little hard to figure out exactly the intended usage just through the API. I tried sifting through commit logs, but nothing stood out. - There is a separate activity for listing vs. editing proxies. If you're creating a master / details view, which seems to be the intended usage of these classes, which place has dominance for the history token? I get how multiple activities could be on screen by utilizing multiple target regions and/or activity mappers, but I'm not sure how that works when there are multiple places involved. For example, if I'm editing customer 2 and have paginated to page 3 of the customer list, what does history token look like? Thanks and we're loving the new stuff so far. Great job! - Amir -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
