On Jul 17, 2009, at 3:43 AM, [email protected] wrote: > Just thought I'd chuck in my 2ยข ... in the use cases for the various > controllers / actions, I'll define logical roles a user must have in > order to perform the action / access the controller. Then, in the > navigation menu, I simply check if the user has those roles to > determine whether to display the relevant item or not ... I know its > kind a low-tech, gets the job done, though :) > Cheers, > C
Well, my motivation is that I've already defined access rules in the controllers and actions themselves using allow_only and @require and setting up the right predicates. Now that my app is all snug and secure (I hope! :-) ), I'd like to re-use that work instead of repeating it in the navigation code. If Foo.dosomething can check whether a user is authorized, I'd ideally like for the navbar builder to be able to ask it (well, it's decorators). -- Kirk Strauser --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
