Depends on the situation, but in general its much easier on users if things they can't do/edit aren't shown to them. Or, alternatively, if they are shown, be shown with some visual indicator of restricted access. A panel full of blank values with no UI feedback is somewhat unintuitive. A panel with a shadowbox over it that says "ADMINS ONLY", for example, makes a bit more sense, and will get you many fewer support calls.
I maintain a collection of user role objects in my application model, which is available to all presenters in the application. The presenters can each poke at this to see what they should be displaying. -Ben On Mar 2, 11:10 am, zixzigma <[email protected]> wrote: > could you please explain, why the check on client-side is necessary, if the > server does the check ? > > and on the client-side, do you mean having a UserRoles object, which > contains user's permission ? > > Thank You -- 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.
