? skinr-[755722].patch ? skinr.documentation.patch ? skinr.fix.install.patch Index: help/features.html =================================================================== RCS file: /cvs/drupal-contrib/contributions/modules/skinr/help/features.html,v retrieving revision 1.2 diff -u -p -r1.2 features.html --- help/features.html 15 Oct 2010 07:26:55 -0000 1.2 +++ help/features.html 15 Oct 2010 21:04:26 -0000 @@ -31,6 +31,12 @@ skinr[skin_system_name][features][] = no Note: node_[node_type] is not yet implemented. +

Regions

+
+skinr[skin_system_name][features][] = region
+skinr[skin_system_name][features][] = region__[region_name]
+
+

Page (body classes)

 skinr[skin_system_name][features][] = page
Index: help/rules.html
===================================================================
RCS file: /cvs/drupal-contrib/contributions/modules/skinr/help/rules.html,v
retrieving revision 1.2
diff -u -p -r1.2 rules.html
--- help/rules.html	15 Oct 2010 07:26:55 -0000	1.2
+++ help/rules.html	15 Oct 2010 21:04:26 -0000
@@ -1,6 +1,15 @@
-
Page rules allow you to use Skinr to
-  add body classes to your page(s) based on user role, path, or PHP code, just
-  like block visibility settings. They can be used to do things like: set a
-  container width for grids, define sections of a site, change font size/face,
-  background colors, etc.
+
Rules are one of the most powerful features of skinr.  Using rules you can apply classes to the body of your page or to regions in your theme depending on an array of options just like block visibility settings. They can be used to do things like: set a container width for grids, define sections of a site, change font size/face, background colors, etc.
 

+
+
Page rules vs. Region rules

+
Page rules allow you to add classes to the entire body, which is helpful if you want to apply changes to the entire page.  With region rules you have more fine grained control because you can apply classes to any region declared in your theme (eg. header, footer, first sidebar).
+

+Note: The select list for regions is currently not grouping regions by theme.
+
+
Visibility options

+
Like block visibility options, with rules you can control where they show on your site based on page path, content type and user role.  You can no longer specify visibility based on PHP code.

+Note: These options have not fully been ported to 7 yet.
+
+
Contextual links

+
Page rules can be created and edited in the skinr admin area but if you want to be able to control them without navigating to the admin page you will have to add contextual links.  See Making skinr work with your theme for more.
+

\ No newline at end of file
Index: help/skinr.help.ini
===================================================================
RCS file: /cvs/drupal-contrib/contributions/modules/skinr/help/skinr.help.ini,v
retrieving revision 1.2
diff -u -p -r1.2 skinr.help.ini
--- help/skinr.help.ini	15 Oct 2010 07:26:55 -0000	1.2
+++ help/skinr.help.ini	15 Oct 2010 21:04:26 -0000
@@ -27,7 +27,7 @@ parent = syntax
 weight = 6
 
 [rules]
-title = "Page Rules"
+title = "Rules"
 weight = 2
 
 [inheritance]
Index: help/theme.html
===================================================================
RCS file: /cvs/drupal-contrib/contributions/modules/skinr/help/theme.html,v
retrieving revision 1.2
diff -u -p -r1.2 theme.html
--- help/theme.html	15 Oct 2010 07:26:55 -0000	1.2
+++ help/theme.html	15 Oct 2010 21:04:26 -0000
@@ -1,38 +1,6 @@
-
Skinr creates a variable containing your skins class that you need to print
-  inside your template files. Thankfully this will not be necessary in Drupal 7,
-  but for now you'll need to add the $skinr variable and all the
-  template files you plan to use yourself.
-

-
-
Printing the $skinr variable

+
Unlike in Drupal 6 where you had to print your $skinr variable, in Drupal 7 this is no longer needed.  To use skinr with your theme you need to include skins in your .info file or enable standalone skins.

 
-
The $skinr variable should be printed in the class attribute of
-  the first, or outer-most <div> in your theme's template
-  files. The variable is the same no matter which type you are dealing with, but
-  you may need to add template files to your theme. The variable is added by
-  doing:
+
Contextual links

+
In Drupal 7 all blocks have contextual links by default, the templates for html and region do not. The body and regions are still able to be edited without contextual links but to add them you will need to have html.tpl.php and region.tpl.php in your theme.  Print the following line right after the body tag in the html template and after the first containing div in the region template:
 

-
-
<?php print $skinr; ?>

-
-
NOTE: Depending on how your template files are structured, you may need to add a blank space before the variable so it doesn't conflict with other classes you might have:

-
-
<?php print ' '. $skinr; ?>

-
-
Template files needed in your theme

-
Here is a list of template files that are typically used and supported by
-  Skinr. See the link for each if you need to create these from scratch in your
-  theme. These links point to Drupal's default code for the template files.
-  You'll be able to copy/paste that code or tpl file to your theme. Then you can
-  add the $skinr variable and modify the code to suit your needs.
-

-
-
-
-
Note: If you have other template files, i.e. node-blog.tpl.php make sure you print the $skinr variable in them, otherwise it wont work.

+

\ No newline at end of file