2008/9/10 kaspar.ru <[EMAIL PROTECTED]>: > it seems inconvenient.
I suppose you could look at it that way, but the fact remains that widgets must be rendered by modifying the DOM, the DOM is a tree, and trees can't contain nodes with more than one parent. It doesn't really have anything to do with convenience. > In this case I've to synchronize the state > between them You could model the navigation widgets as views on a model, and things should work pretty easily. Just create a model class to describe the navigation (probably current page, and total number of pages, or something similar), and then expose an interface your views can use to manipulate the model. You'll probably need methods like setCurrentPage() and/or goToNextPage() and goToPreviousPage(). You'll also need some events, maybe current-page-changed, or similar. It should be straightforward MVC. Ian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
