[jifty-devel] tutorial talks of overriding default _elements/nav

Jesse Vincent jesse at bestpractical.com
Fri Jul 6 08:47:21 EDT 2007

On Jul 5, 2007, at 11:45 PM, Matthew Lenz wrote:

> On Thu, 2007-07-05 at 21:49 -0400, Jesse Vincent wrote:
>> On Jul 5, 2007, at 9:16 PM, Matthew Lenz wrote:
>>> but if you take a look at the _elements/nav it says:
>>> %# Navigation frobbing now handled in Dispatcher plugins
>>> %# This exists for backwards compatibility
>>> Is there an example of using the dispatcher to draw the nav?
>> _elements/nav wasn't so much to draw nav as to set up Jifty->web-
>>> navigation
> I found an example in some 3 part slide show that uses the dispatcher
> for just about everything.
>>> Which brings up another question on which I was hoping I could get
>>> some
>>> clarification.  I'm having a bit of difficulty understanding the
>>> implementation of authorization throughout an application.  Am I
>>> correct
>>> in that most authorization could feasibly be placed into the
>>> dispatcher?
>> Have a look at Jifty::Plugin::Authentication::Password
> that's for authentication right? maybe i didn't use the right term.

You did. I was tired. Sorry about that. Generally, I push  
authorization down into the model. It doesn't generally matter if  
someone can display a page, so long as they can't see/edit the data.   
perldoc Jifty::Record for sterling's latest work in easy authz  
controls on model classes.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.bestpractical.com/pipermail/jifty-devel/attachments/20070706/9212b467/PGP.pgp

More information about the jifty-devel mailing list