On Nov 14, 3:06 am, Brian Rosner <[email protected]> wrote:
> On Nov 13, 2009, at 12:46 PM, bobhaugen wrote:
> > Navbar improvements include:
> > * Project/tasks retains the Project maintab hilite (that's a bug fix)
> > * Likewise Company/Project/Tasks retains the Company maintab hilite
> > * Current subnav links are hilit (related
> > tohttp://code.pinaxproject.com/tasks/task/115/
> > )
>
> From the sounds of it these can likely get moved back upstream. I'll
> take a closer look and let you know.
The Project maintab hilite was retained by adding a block.super to
tasks/base.html, like so:
{% block body_class %}{{ block.super }} tasks{% endblock %}
(was jtauber's idea...)
I think that should get moved upstream.
The subnav link hilites use the same technique and also require id's
on the il's which are then used in site_tabs.css. Not sure that is
the best way to do it, but it works, and fits the overall pinax nav
pattern of the moment.
Company/projects/tasks navbars required a bunch of other finagling
including a body_class parameter. It works, but is ugly (not the
body_class parm but the other kludges), and I would rethink it all
after I see how you handle nested groups.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Pinax Core Development" 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/pinax-core-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
