>> A different approach is to return the menu structure from the server >> based on a users permissions. > > This is more interesting! What would you actually pass back? An XML > structure from which to build the menu? How would you then hook it > into method calls or events to the controller?
You're asking the right questions ... I didn't take this approach, so haven't thought about it too much. It's kind of interesting that you mention "controller". In my app, the client-side "controller" in terms of navigation is basically a HistoryListener that knows about a user's permissions and has a map of historyTokens to "body panels" along with some hooks for updating the navigation menu. -Dave --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
