I have a module that produces a lot of pages. A set of these are handled by a particular part of my application, and I would like all these to have a class added to either
body. I'd settle for
I'd have to create that hook and then tell it to go somewhere else to determine which page call back was used and which class to apply - it's all backwards. Drupal's already selected the right callback, so a 2nd lookup is another thing to maintain and an inefficiency.
I could of course do something like set a
global $extra_page_classes variable and then implement the hook to add these classes to the page, which is more efficient but it's still messy. Or I could add (yet another) wrapping
<div> to my callback output, but that's not going to give a themer chance to adapt the rest of the page elements outside of the main content.
Seems odd that a page callback, responsible for the substantial content of the page, can't set page-level attributes. A page callback can, for example, choose to call
drupal_add_css(), but it (apparently) can't do something as simple as add a class to the page.
As it seems odd and Drupal usually has some (often hidden) elegance, I thought I'd ask specifically if there was a better way.