Tabula Rasa / Funky Circles

[ninetydegrees]

Theme name/layout: Funky Circles / Tabula Rasa
Author: ninetydegrees
Layout info: theme layer
Image info: five. All are my own.

I tried to use as many properties as I could but some don't exist:
- Non standard background positions
- Alternate font bases (e.g. for Linux users)
- Title background color
- Entry hover link background color (I think there should be core props for link background colors. Changing color isn't enough sometimes/for some users)
- Entry content and entry footer border color (this one can probably be omitted)
- Entry footer color
- Entry footer lists color (there's only one for interaction links, I believe)
- Entry management/interaction lists image
- Module lists image

N.B. Link colors apply to contextual pop ups. This makes the pop up links unreadable in light-on-dark layouts such as default Negatives, default Basic Boxes and this theme.

Thanks to afuna, baggyeyes, cesy, turlough, yvi and zvi for testing and providing feedback. *hugs*

I'm willing to work on this more if someone tells me what I should do. :)

Edit: it would be awesome if the nav link .current class could be added to the li in addition to the a. I could change the li image for current link and make it even more visible. However, this implies editing function print_module_list.

Comments

[ninetydegrees]

All right, so I should use the property then (or the string variable if there is one) right?

No, I mean I have two font bases because some Win/Mac fonts aren't available on Linux as it's been pointed out to me (except with the mscorefonts thing I believe) so I always try to include a Linux font base in my declarations.

I don't think so. Here's what's in TB:

.entry-interaction-links a { $entry_interaction_link_colors }

Ok, great. Thanks again. Can I also add more props from Core then? For example, I really want people to be able to set entry_datetime_format_group values because the am/pm drives me crazy. It's not how you say time in my country.

[afuna]

All right, so I should use the property then (or the string variable if there is one) right?

This is for the background position? Hmmm. No, that won't work, because once someone saves via the wizard, the default value (top left, repeat) gets saved.


Two font bases, if I understand your question correctly, you can do something like:

set font_base = "Arial, Verdana, \"Comic Sans\""; # (>_>)



Footer colors: hehe, okay. In that case, please do create new variables. I think what I'll end up doing is moving the variables up from your layer to core2 once you're done with the conversion, and then poking them into any other layouts where it seems appropriate.


Pulling in properties: yes, definitely! I'm slightly concerned about future-proofing of entry_datetime_format_group since, as per http://bugs.dwscoalition.org/show_bug.cgi?id=833, we're planning to add more; I'm not sure if we're planning on removing existing (probably not, though; if we're not, then nothing will break, but noting FYI)

[ninetydegrees]

I'm not sure what I should do. What I currently have is:

#header .inner {
$header_background
$page_subtitle_colors
background-position: 100% 5px;
}

You're saying I should remove $header_background because the user layer will override "background-position: 100% 5px;"?

[afuna]

You could pass a "" to the "position" element of header_background and then override with background-position: 100% 5px.

Or you could even, I think, pass the "100% 5px" to the generate_background_css for $header_background (same effect, either works, so I'd go with whichever seems more readable to you)

[ninetydegrees]

I'll go with option 1 as I use this background four times and have two different positions. Thanks for all your help through this. I'm nearly done with the layout layer and the color theme layer.