Allow any theme to declare their own views-admin.{theme_key}.css

Patch attached.

This allows any theme to declare a css/views-admin.theme_name.css file and views will load that.

The current behavior is almost the same, except views uses the wrong path for any theme thats not included in the views module.

Oh, being that views is trying to do this for any theme, yet it gets the wrong path, this might be a bug report instead of a feature request, but I'll let the maintainers be the judge of that. :-)

@merlinofchaos, I didn't see your comment before attaching the patch. If thats the case then this is probably a bug report.

[double post]

I'm not entirely sure how to fix the problem, without hard-coding which theme views support. But here's some more details.

<?php
    // This is how views adds all the css for other themes.
    $list[$module_path . "/css/views-admin.$theme_key.css"] = array(
      'group' => CSS_THEME,
    );
    // $module_path is always set to  drupal_get_path('module', 'views_ui');
?>

So what ends up happening when testing with Rubik for example views call drupal_add_css for these files:

sites/all/modules/views/css/views-admin.rubik.css
sites/all/modules/views/css/views-admin.tao.css (rubik base theme)

Note: If you decide to test this, you will need to modified rubik to correct the filename, and place it in the right directory.