Agreed with bookmarks. Thank you. What about browser next-prev buttons support (sample I wrote with paginator)?
On 29 mar, 19:42, Jens <[email protected]> wrote: > The problem is that your (bookmarked) URLs will become useless if you > change the implementation of your UI. If you, as mentioned in your wiki > page, store opened/closed tree nodes in the URL, what happens if you switch > to a flat table or a totally different custom widget? The previous URL is > pretty much useless now. > > Thats why you shouldn't say that each UI component has a URL state. Sure it > has a state, but you don't want to bookmark that specific state. You want > to bookmark WHAT the application in the current place presents the user. > Thats in most cases totally independent on how you implement the UI and > which components you use. > Example:http://domain.com/#/employee/5/details. This loads all employees, > preselects the one with ID 5 and shows the details section of the employees > data. No word about the used UI components in the URL. Got the idea? > > -- J. -- 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.
