Bachir Soussi Chiadmi f2b8ace9b7 FINAL suepr merge step : added all modules to this super repos | 9 lat temu | |
---|---|---|
.. | ||
images | 9 lat temu | |
js | 9 lat temu | |
templates | 9 lat temu | |
LICENSE.txt | 9 lat temu | |
README.md | 9 lat temu | |
core-rtl.css | 9 lat temu | |
core.css | 9 lat temu | |
icons.css | 9 lat temu | |
overlay-child.css | 9 lat temu | |
page.tpl.php | 9 lat temu | |
print.css | 9 lat temu | |
rubik.info | 9 lat temu | |
screenshot.png | 9 lat temu | |
shortcut.css | 9 lat temu | |
style-rtl.css | 9 lat temu | |
style.css | 9 lat temu | |
template.php | 9 lat temu | |
views-admin.rubik.css | 9 lat temu |
Rubik has undergone a slight visual overhaul and structural refactoring to accommodate some key changes in D7. In particular:
Because these changes represent a departure from the previous visual look of Rubik, D7 will be using the 4.x version series. There are plans to backport many of these changes to D6 in a 4.x branch as well.
Rubik is a clean admin theme designed for use with the admin module. It features a set of icons for admin pages provided by Drupal core and aggressive styling to reduce visual noise wherever possible.
You must install the Tao base theme for Rubik to operate properly.
Rubik can be used quite successfully as a base for non-admin themes. Here are some reasons you might want to use Rubik as a base theme:
Before beginning to subtheme based on Rubik, please read the README included with Tao. As Rubik is a subtheme of Tao, many of the principle and ideas in Tao apply to subtheming Rubik as well.
To work with form theming in Rubik (and Drupal in general) you should become
familiar with drupal_render()
. Form rendering in Rubik is done in the
template file, not the preprocess, allowing any additional preprocessors to
alter the form in its structured state.
Rubik pushes many system forms through a series of additional preprocess functions before templating.
rubik_preprocess_form_buttons()
detects any root level submit and button
type elements and groups them together under $form['buttons']
so they can be
placed in a wrapping element.rubik_preprocess_form_legacy()
handles legacy theme function-based forms
that use a declared theme function. It will first render the form using the
function specified by #theme
and then generate a form array that can be used
with drupal_render()
in templates.The admin icons in Rubik are displayed using a CSS sprite and corresponding CSS
class. The class that refers to each icon is based on a link path to the admin
page. For a path at admin/settings/foo
, the classes added to the containing
element of span.icon
are:
path-admin-settings-foo
path-admin-settings
path-admin
This allows for your element to fallback to a more generic, placeholder icon if the most specific class cannot be used.
Rubik groups elements in the tao object template and various forms into two columns.
For object templates (theme('node')
, theme('comment')
, etc.) you can
switch to a typical 1-column layout in you preprocess function:
$vars['layout'] = FALSE;
For form templates, you should use hook_theme()
to and declare the form's
template as form-simple
. If a prior preprocess has moved form elements in
$vars['sidebar']
for the form, you will need to move them back to the
$vars['form']
element.
// Switch comment form back to simple layout.
function mysubtheme_theme() {
$items['comment_form'] = array(
'arguments' => array('form' => array()),
'path' => drupal_get_path('theme', 'rubik') .'/templates',
'template' => 'form-simple',
);
return $items;
}
core.css
provides styles for standard Drupal core markup elements, in
particular form elements, list items, pagers, etc. It does not style any "page
wrapper" or "design elements" like the site logo, navigation, etc.icons.css
provides styles for the admin icons provided by Rubik.style.css
provides styles for the Rubik admin theme page wrapper and other
aesthetic elements. This includes the site title, tabs, navigation, breadcrumb,
etc. This is the file you will most likely want to override to begin your
subtheme.