Has anyone tried using multiple views in one Place then having separate activities for each one? This scenario occurred to me when I wanted to save work on having to repeat the same header for multiple Places in my application. It was done using one view as a container, acting like a frame for a header view and a body view so that every time my app would move from one place to another, the activity code would just get the root view then replace the child widget in the body with the view I wanted to show thus keeping the header view in place without having to repeat it all over different views if I didn't use this technique. It works fine, except that I am bothered by the fact that I have a Place and Activity for the header view separate from the others which is doesn't quite fit the essence of Activities and Places as I understand them. Ideally, there should be only one Place and Activity for each "page" in my application. It just so happens that in order to save coding for sections of a place that are repeated over many places, I have to define a separate Place and Activity class for it. Perhaps there could be a new concept that will cover this gray area that would make it easier explain separately defined repeating sections of a Place.
- Owen -- 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.
