Template access to LJ::set_(active|dynamic)_crumb and LJ::need_res

[pauamma]

foxfirefey's let's keel BML ded (and eat its head) nudged me into TTizing the stats pages before they get too unwieldy. So (because that page uses crumbs) I'm looking at how to set a crumb in the template (which I think is the proper place to do it, since templates map better onto pages than controllers do IMO). The interface I'm thinking of (tentatively - I haven't actually tried this yet) is something along the lines of:

(something relying on RAWPERL, which is (and will likely remain) disabled, so filter/plugin it is instead, per exor674's comment below)

I'm also wondering whether to make it a filter (or something) in DW::Routing::Apache2 instead, but I don't want to make further work on it harder if I can avoid it.

Anyone has a thunk about this? (Specifically exor674 and foxfirefey, since they're leads on this, but not limited to them)

Comments

[mark]

Given that we don't use crumbs in any of our site schemes, we may consider just removing them. Unless someone sees a real good reason for them.

They're lots of maintenance, yet another thing to work into the UI, and I was never a big fan of them anyway.

[denise]

I was thinking about enabling them, but honestly, crumbs are generally only useful when you don't design your menus/navigation well enough, and we have.

I'd +1 them dying.

[pauamma]

lynx displays them for those pages that set them. (If it shouldn't, I'll miss them, but it's your site, so *shrug*.)

And I just realized I meant to address need_res too, but only mentioned it in the topic. Any thoughts about an in-template interface to it?

[exor674]

PERL/RAWPERL isn't enabled ( and unless I can help it, it won't be -- If we do that, we'll eventually fall into the same thing we did with BML, where the entire page is just a glorified perl script, and the controller is empty )

If we end up doing this, a filter would be best, or a DW-specific TT Plugin.

[pauamma]

*nod* (I think doing this would be useful, for need_res if not for crumbs.)

a filter would be best, or a DW-specific TT Plugin

Do you have a preference between those? (And if a filter, where should it be to make maintenance/planned changes to DW::Routing::* easier?