Andrew, Thanks for your reply. And yes, this makes sense to me as well. My thoughts were along the same lines. I will easily have the ability to add menu items for my user without having to change my template and the flip side, I will be able to change my template without impacting how the controller passes down the menus. Seemed like a win win.
Please let me know where you plan to post your navigation stuff and I will share mine their as well. Thanks, Wayne Piece of Py http://www.pieceofpy.com On Sep 26, 2:48 pm, "Andrew Smart" <[EMAIL PROTECTED]> wrote: > > -----Ursprüngliche Nachricht----- > > Von: pylons-discuss@googlegroups.com > > [mailto:[EMAIL PROTECTED] Im Auftrag von > > [EMAIL PROTECTED] > > Gesendet: Mittwoch, 26. September 2007 16:40 > > An: pylons-discuss > > Betreff: Displaying page elements based on AuthKit authentication? > > > Hello, > > > Maybe I am missing something obvious, but I am using Pylons > > with the AuthKit middleware and mako templates and I am > > curious what the best method for controlling what elements > > are displayed to the user based on their authentication is .. > > should the logic exist in the template? > > Should the controller push down the element to the template? > > An example would be changing the login form to an action menu > > once the user is authorized. > > I forgot something: auth-kit is dealing only with authentication, > Authorisation and access (AAA). It is not focused to help you with > navigation - and I think this is the right approach. Seggregation of > duties, seperation of code and stuff... > > Regards, > Andrew --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
