Thank You : )
your post gave me some comfort : )
Yes, the problem is related to paging, and not necessarily activity/places.
as for your opinion of master/detail,
I think it is a shame to not take advantage of the fact that we can
display master/detail side by side, without a full page reload,
something that was not possible with traditional webframework,
and is nearly possible now with AJAX/GWT, only if there comes a solution
to implement the paging correctly.
regarding your suggestion on using "continuous scrolling",
I am going to investigate that now, and I believe it will work,
however my concern is this,
lets say we have a list of employees with continuous scrolling,
and next to it, we show detail of employee, when one employee is selected from the list.
if we bookmark place employee/777
when navigating to place employee/777 for the first time from bookmark,
how can the master activity which contains a continuous scrolling table/list,
highlight employee with id 777 in the list, when in fact the continuous scrolling list
presents only an X number of items initially, and load the rest on demand ?
do you think this is possible ?
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to firstname.lastname@example.org.
To unsubscribe from this group, send email to email@example.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.