On Friday, January 21, 2011 1:47:19 AM UTC+1, zixzigma wrote: > > could you please explain what is the criteria for data to be "highly > dynamic" ? > > and in case of GWT, the entire app is one page, and we have the > concept of places. > and we don't have to forward to a new place, we can have a place that > also support paging. > > for example, > > employees/p1 > employee/p2 > > p1, displays the first page of result set, p2 the second page, and so > on. > as user clicks on Pager forward/previous buttons, the History token > also changes, > it is not actually another page, p1 and p2 and pN, are used like query > parameters, > that activities can use to know the start position. >
They would still be distinct Place instances (oh you could probably hack around to make it work without changing the current place, but I bet you'd have more trouble than just using distinct Place instances). Just that your ActivityMapper would probably return the very same Activity instance, so the activity isn't "re started" as a result of navigation between pages. if you look at Gmail, when you want to see "Older" emails, (seeing the > next page of result), > the history token changes. I understand gmail is not built using GWT, > but just demontrating the idea. It all depends on the UX you're looking for (i.e. should the "back button" of your browser take you to the previous page?) -- 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.
