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

[baggyeyes]

I just loaded the new layout code - and it is now "circles, like Whoah!" I'm sure that is not what you intend. I've left it on, if you want to see it in action.

[ninetydegrees]

Woah, weird! It doesn't do that for me! I see in your CSS that the backgrounds are set to "repeat" but I set them to no-repeat in the theme. I don't know what's going on. :/

[baggyeyes]

I changed nothing, I swear!

[baggyeyes]

The options in the module had it set to "tile" and "top-left" for both header and background.

[ninetydegrees]

I don't get this. Can you tell me how you've used it? I went to Select Style, clicked on 'Your Custom Layers', selected the layer. When I clicked on Customize, the options were set to don't tile for both bkg images and bottom left for the page bkg. The other setting is not important as I'm not using it.

[baggyeyes]

I don't get it either. On my journal, when I set it up, I used the code you linked to on this entry.

Tons of circles.

So I went into Style, and under Images, Background was set to Tile; Top left. Header image was set to Tile; top left. These two options I had to change. I have no idea why my journal changed everything. I didn't alter any of the layout code at all.

[ninetydegrees]

This is really odd. I think afuna turns themes into layout layers when she converts them so I think it couldn't happen then. *crosses fingers*

BTW, is the theme purplish or blueish to you? I have different color settings in Firefox and IE and it's purple in FF but dark blue in IE.

[baggyeyes]

Purple. I like the color.

[baggyeyes]

I think it's something from my journal - maybe an old setting interfering with the layer. I just tried it elsewhere, and that worked fine.

[ninetydegrees]

Could it be a user layer?

[ninetydegrees]

The way it's intended to be then. Great! Thanks for answering.

I like it a lot too but I'm always happy when I get to use my favorite palettes from Colour Lovers.

[foxfirefey]

Oh wow I just saw this for the first time on baggyeyes and it is really pretty!

[ninetydegrees]

Thank you! I'm making a pale green theme for Cesy and working on a Chocolate/Pink one too. I'll probably do a Dark blue too. Any other suggestions?

[denise]

How about a darker green? And maybe turquoise. (You can tell I like all of the cool colors.)

This is really pretty.

[baggyeyes]

I think there may be a style bug - but I am lacking the coherence to properly put itinto words. Some layouts retain former choices I've made, even when I've applied a new layout, such as a theme layer like this one, or previosuly, sven's Bases layout. Or, maybe I've screwed something up, and I can't see teh forest for the trees right now??

If this makes no sense, pat me on the head and send me away.

[ninetydegrees]

Turquoise probably. I'm not sure about green. Cesy's green already turned blueish. I'm not really good with 'pure' green.

[turlough]

Pure green is incredibly difficult to work with I've always found. It either turns out blueish or yellowish when I try.

[ninetydegrees]

Exactly. Or I tend to turn it all Christmasy and combine it with red. I hate that.

[afuna]

Hm, since it's custom behavior thing, I'd suggest skipping the print_module_list altogether, and override print_module_navlinks instead. Something like this (note untested):

function print_module_navlinks() {
    var Page p = get_page();
    open_module("navlinks", "", "");
    var string[] links = [];
    
    println """<ul class="module-list">""";
    foreach var string k ($p.views_order) {
        var string css = """ class="$k" """;
        if ($p.view == $k) { $css = """ class="current $k" """; }
        println """<li class="module-list-item"$css><a href="$p.view_url{$k}">"""+lang_viewname($k)+"""""";
    }
    println "";

    close_module();
}

[afuna]

Non-standard background positions: what I've done so far is hardcode an override them into the CSS.

Alternate font bases: I'm afraid I'm not sure which you're referring to, sorry. Do you mean something other than $*font_base/$*font_fallback?

Entry footer lists color: IIRC, the entry_interaction_links_color color is used for both (we probably picked used that one because it's always text; the other can be either text or images)




The properties you mentioned I think would be good to have in core, but since it's blocking you now, I propose this workaround so you can add the additional props:

1.) create a new layout layer
2.) copy and paste the tabula rasa layout (id=550) into it
3.) copy and paste your theme code into it (but remove the layerinfo type="theme")
4.) add your new properties
5.) edit to your heart's delight

[afuna]

Oh, also the contextual popups, yeah that is problematic! I just filed this bug so that we set a default link color. You can target the div.ContextualPopup, but layouts don't have to care if they don't want to.

Bug here, fyi: http://bugs.dwscoalition.org/show_bug.cgi?id=1727

(Sorry for the comment spam! Did I miss anything? )

[ninetydegrees]

Oh I didn't think you were allowed to do that. Good to know, thanks.

[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]

When viewing the Network page, current is set to read since Network is not a defined view. Are there any plans to change that?

[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.

[afuna]

Ooh, good catch. Sorry for taking so long to respond; managed to lose this in my inbox. I am filing a bug, and shall have a patch up shortly :)

[ninetydegrees]

No worries. I imagine you get tons of e-mails every day!