Deep theme switching with Crumbs + Themekey

I will probably be sprinting for CiviCRM on Friday, while the others are sprinting for Drupal... But I will have a session about Crumbs on Sunday. I need to get a few things finished on that module, before the session :)

Theme switching is one of the big promises of the crumbs module, and I thought it would be cool to have some perspective that I can present in the session.
So far this perspective is to use crumbs in combination with sections, with a PHP condition. I also considered context with context_reaction_theme. This will all work probably, but in the end I would like to have something that does not require to hack PHP into the database - even if it's just small snippets.

I think I will simply explain ThemeKey as a possible perspective, but for now people have to stick with context and sections.

Just noticed your own session is early in the morning (10:00). This is tough, for a sunday! Although I had the plan that this time I don't want to sac sessions to parties.

Damn, I did not manage to catch you up :/

I'm on Drupal Camp Gent 2012 :)

I don't remember much of this issue and the internals of themekey.. but this could change in the next hours, going to use it on a project :)

Hey, it was not so difficult actually :)

(in crumbs.module, going to commit and push soon)

/**
 * Implements hook_themekey_properties()
 */
function crumbs_themekey_properties() {

  $attributes = array();
  $attributes['crumbs:trail_paths'] = array(
    'description' => t('Crumbs trail paths'),
    'validator' => '',
    'page cache' => THEMEKEY_PAGECACHE_SUPPORTED,
  );

  $maps = array();
  $maps[] = array(
    'src' => 'drupal:get_q',
    'dst' => 'crumbs:trail_paths',
    'callback' => '_crumbs_themekey_path2trailpaths',
  );

  return array('attributes' => $attributes, 'maps' => $maps);
}


function _crumbs_themekey_path2trailpaths($path) {
  $trail = crumbs_get_trail($path);
  $paths = array();
  foreach ($trail as $k => $item) {
    $paths[$item['alias']] = $item['alias'];
    $paths[$item['route']] = $item['route'];
    $paths[$k] = $k;
  }
  return array_values($paths);
}

When I created this issue, the idea was to apply every themekey condition to every themekey item.
Now I changed my mind, and instead I just let the admin define one parent path (with wildcard) per themekey rule.

This is long implemented!

Title should be adapted to being in the Crumbs issue queue.

Thanks!