Are there plans for skinr at this stage? I see they have released a 960 stylesheet that seems to replace the regular dash with underscore. If someone wanted to take a crack at it, is there any reason you can see it wouldn't ork or things I should be aware of?

CommentFileSizeAuthor
#23 grid_12_column.inc_.txt7.54 KBpaskainos
#23 grid_16_column.inc_.txt9.29 KBpaskainos
#23 grid_24_column.inc_.txt12.78 KBpaskainos

Comments

himerus’s picture

himerus commented
Status: Active » Postponed (maintainer needs more info)

i have investigated this before, and played with skinr a few times.
A lot of people love it, and what it can do... for me, it sort of replicates my own "normal" ways of doing things.
I had at one point the skinr grid code in the .info file and then removed it.

The biggest issue is to replicate the 12, 16 AND 24 column 960 grids using skinr settings, it adds several hundred lines of code to the .info file which I'm not a huge fan of. The only situations I ever used it was when theming out a single column panels page where I could use skinr to assign the region width... HOWEVER, in an even easier fashion, I could also just put a simple "grid-6" in the css field in panels as well...

I really need to install and dig into fusion to see how they are really using skinr that goes above and beyond what can be done easily another way.

I'm a BIG FAN of making this theme easily usable by ALL themers... and easy for site admins to adjust, etc. hence the interface for the grid settings. I want it to be widely adopted, and usable by all, not just by coders that can extend it, so with that in mind, I'm not opposed to getting skinr put in and working... just have some things to consider in how that affects things elsewhere.

R-H’s picture

R-H commented

Big vote here for getting Skinr 2 integrated in this theme. Please take a look at the latest version. Skinr 2 would allow for additional css to be applied to elements on the page as needed including floats and positioning in addition to widths.

himerus’s picture

himerus commented
Version: 6.x-1.0-beta4 » 7.x-2.x-dev
Assigned: Unassigned » himerus
Status: Postponed (maintainer needs more info) » Active

I WILL be including skinr support for the 7.x-2.x branch of Omega.

While trying to make the default base theme a little more presentable out of the box, skinr is definitely the best option for this. I've NEVER been opposed, but more just had the issue of what kinds of styles I should include by default, when the core of the base theme was meant to just be that... a base theme.

However, with trying to beautify the basics out of the box, and include some powerful sub-themes, this will be included in the newest version for Drupal 7.

R-H’s picture

R-H commented

Very cool! If I may suggest, I think it would be awesome to have skins that handle alignment in the region: left, center, right. Float might assist with that.

Andy Britton’s picture

Andy Britton commented

Did this get implemented with 7.2? I'd love to be able to setup different styles for coloring, background imaging etc of blocks.

Regards

Andy

himerus’s picture

himerus commented

At last check, the 7.x version of Skinr is still not ready. I would like to implement into Omega (although it should be easy enough to implement in any subtheme of Omega as well)

I'll check back on Skinr soon!

break9’s picture

break9 commented

subscribing

g.k’s picture

g.k commented

subscribing

fubhy’s picture

fubhy commented

Himerus and me are discussing this already. It will probably become a part of Omega 3.x and get backported to 2.x, too.

jeffwidman’s picture

jeffwidman commented

subscribe

tuthanh’s picture

tuthanh commented

subscribe

robloach’s picture

robloach
he/him
commented
Version: 7.x-2.x-dev » 7.x-3.x-dev
Status: Active » Postponed

Skinr homepage:

The Drupal 7 version is under heavy development. It is not stable, functional, or supported right now.
webankit’s picture

webankit commented

Any updates

Anonymous’s picture

Anonymous (not verified) commented

Since there is no native skinr support so far, how can we implement its functionality ourselves? I can install Skinr and add custom classes to almost every object. But I can't get the UI to show me my skinr styles info. Now, unfortunately I don't know wether the theme lacks some configuration somewhere or wether skinr is buggy.

I added
skinr[api] = 2
in every .info file.

Did anyone here have any success to get this to work? I simply want to make a couple of box formatting options available to users, nothing fancy in terms of grids or anything.

marcoka’s picture

marcoka commented

skinr is pretty undocumneted as i last looked. look at fusion and steal it from there :D

Anonymous’s picture

Anonymous (not verified) commented

Yes actually that was the way to go. ;-) I basically just "reimplemented" everything the same way Fusion does and now I have styles for my blocks in Omega! Yay! The problem was a mix of filename-, function- and directory-conventions. Actually with Skinr 2.x I didn't had to change one single line in any tpl.php files at all. Sweet.

marcoka’s picture

marcoka commented

genox, would you tell us some details. maybe we could use them?

Anonymous’s picture

Anonymous (not verified) commented

I'm not sure wether that's the appropriate way of doing it but it works for me:

1. Add skinr variables to template.info. I just added this to the .info file in my sub theme.

skinr[api] = 2
skinr[directory] = skins

2. Create a skinr definition file:
mytemplate/skins/mytemplate/mytemplate.inc

3. Add some style definitions, for example:


function mytemplate_skinr_skin_mytemplate_info() {

  $skins = array();

  $skins['mytemplate_bgcolor'] = array(
    'title' => t('Background color'),
    'description' => t('None'),
    'type' => 'select',
    'default status' => TRUE,
    'options' => array(
      'color_1' => array('title' => t('Green medium'), 'class' => array('medium-green-bg')),
      'color_2' => array('title' => t('Green light'), 'class' => array('light-green-bg')),
      'color_3' => array('title' => t('Blue dark'), 'class' => array('dark-blue-bg')),
      'color_4' => array('title' => t('Blue dark opaque'), 'class' => array('dark-blue-opaque-bg')),
      'color_5' => array('title' => t('Blue medium'), 'class' => array('medium-blue-bg')),
      'color_6' => array('title' => t('Gray dark'), 'class' => array('dark-gray-bg')),
    ),
  );
  $skins['mytemplate_rounded_corners'] = array(
    'title' => t('Rounded corners'),
    'description' => t('None'),
    'type' => 'select',
    'default status' => TRUE,
    'options' => array(
      'rounded_1' => array('title' => t('Slightly rounded'), 'class' => array('slightly-rounded-corners')),
      'rounded_2' => array('title' => t('Well rounded'), 'class' => array('well-rounded-corners')),
    ),
  );
  $skins['mytemplate_inline_menus'] = array(
    'title' => t('Format ul.menu as inline menu'),
    'description' => t('None'),
    'type' => 'checkboxes',
    'default status' => TRUE,
    'options' => array(
      'inline' => array('title' => t('Enable inline menu'), 'class' => array('inline-menu')),
    ),
  );
  $skins['mytemplate_link-color'] = array(
    'title' => t('Change color of links'),
    'description' => t('None'),
    'type' => 'select',
    'default status' => TRUE,
    'options' => array(
      'link-color1' => array('title' => t('White links'), 'class' => array('white-links')),
      'link-color2' => array('title' => t('Dark gray links'), 'class' => array('dark-gray-links')),
    ),
  );
  return $skins;
}

4. Clear template cache. I used "drush cc all".

Afterwards, I was able to use skinr normally.

Problems I encountered:

a) The naming convention (functions, arrays, directories, files) for skinr are not as documented - IIRC. This is why I couldn't get it to work in the beginning. Or I just did it wrong - I don't remember correctly. Just make sure the pattern matches the above examples.

b) I took most of it from the D7 fusion template, but: the current Fusion version for D7 doesn't use Skinr anymore, the release I used was only available via git repo, not on the project page.

c) CLEAR CACHE ;)

d) Make sure you have the following array elements defined in each style's array. Without those, Skinr's form elements are not being rendered at all.

 'description' => t('None'),
 'type' => 'select',
 'default status' => TRUE,

This should do the trick. However, your mileage may vary.. It feels awfully hackyish to me. :-P Mostly because the first time, I tried to get things working by following the official Skinr documentation, but it didn't work. Maybe they changed the syntax in the dev-version or will change it to match the documentation yet - I wouldn't use this on a large site just yet. I just use it for a small project, basically as a "prototype experience".

marcoka’s picture

marcoka commented

thx. some misunderstanding. i know how to use skinr. you explained in detail how to use skinr. i thought you somehow added the grid solution from omega. thats what i am thinking about at the moment. i mean how to do that the best way.

atm i made a custom css with the widths, because if you use the core grid classes, very block gets margin left and right. thats the kind of stuff i meant.

fusion: the forekd skinr, called it fusion_accelerator and now use that. but i really dont know why the did that..

paskainos’s picture

paskainos commented

7.x-2.0-alpha1 was recently updated... Lots of [continual] improvements, but grid support is still unclear as far as I can tell... Anyone have a chance to take a[nother] look at 7.x-2.x lately?

himerus’s picture

himerus commented
Assigned: himerus » Unassigned
Priority: Normal » Minor
Status: Postponed » Postponed (maintainer needs more info)

This issue "should" be addressed. I do not personally use skinr, and because of it's slow development at the beginning of the D7 life cycle, it was a poor option to even attempt to implement.

I'd "like" to see this implemented in some way in a future release (either a upcoming 3.x release as maybe an additional starterkit with skinr support?? or maybe in 4.x??)

I'm remarking this as "needs more info" as it'll take some investigation how skinr SHOULD be implemented in the base theme (or starterkit) layer to best suit the masses that DO choose to use skinr.

However, this is not a high priority as skinr can ALWAYS be implemented in a subtheme manually by following standard setup instructions on skinr's project page/documentation.

vinoth.3v’s picture

vinoth.3v commented

It would be very great if Omega has new style of skinr implimentaions of its own. without this I am forced to use fusion theme :(

paskainos’s picture

paskainos commented
StatusFileSize
new grid_24_column.inc_.txt12.78 KB
new grid_16_column.inc_.txt9.29 KB
new grid_12_column.inc_.txt7.54 KB

Once Skinr's enabled, adding a grid system for block layout & positioning combining Omega (I'm using 7.x-3.x) with Skinr (I'm using 7.x-2.0-beta1) is a surprisingly simple & easy (three step) process:

Step 1:
Add the following lines to your theme's .info file: 
skinr[api] = 2
skinr[directory] = skins
Step 2:
Add the attached file(s) (only one to avoid clutter, or all if you choose) corresponding to the grid system you're using in your Omega (sub)theme to the /sites/all/themes/[your_theme]/skins/omega_grids directory (removing the '_.txt' extension goes without saying). Note: the extra folder (omega_grids) follows Skinr's 'Multiple skin plug-ins per module or theme' convention.
Step 3:
Open the file(s) and change 'MYTHEME' to your theme's file name.

That's it - you're done! Since the 'skins' call on Omega's native Alpha grid classes, there's no css to add or anything. You can view the skins at /admin/structure/skinr/library, and the skins can be implemented on blocks via a block's contextual links.

steinmb’s picture

steinmb commented
Title: Skinr » Skinr support
Version: 7.x-3.x-dev » 7.x-4.x-dev
Issue summary: View changes
Status: Postponed (maintainer needs more info) » Active
avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Component: Feature Request » Code
Category: Feature request » Support request