Code push: New things for styles

[momijizukamori]

On top of new styles and themes live with the new code push, we have some new options in /customize to play with!

The first is making something we've had a little easier to use - web fonts! They've been settable in layers for a while, but now the option to use them is in the wizard, too, down at the bottom of the Fonts options, no layer editing necessary.

The second is a little more complicated to explain, but something that's been repeatedly requested. Some styles (Practicality, Crisped, Corinthian, Line Up to name a few of them) styled the navstrip CSS using color properties from other parts of the layout. This can be very striking, but there was no way to choose to turn it off if users wanted. That has changed - and now, if you like, you can also customize the navstrip colors for any layout. The options are found at the bottom of the Display options (a little unintuitive, I know, but all the other navstrip options were there). Checking 'Use custom colors on this journal' will show the options for picking colors, which get saved along with all the other layout colors.

Base layouts that used custom navstrip CSS have it turned on by default now, and colors have been grandfathered in to all the old themes that were live at the time of the push, so there won't be any huge changes to how old layouts look, for the most part. New themes won't have these unless the theme designers specifically add them, though.

Comments

[tree]

yay for web fonts!

[momijizukamori]

I know, I'm super-excited about that :D

[ninetydegrees]

Don't know whether it's always looked like this or not but I think the background gradient needs positioning (top center) because it sits in the center for me and it looks a bit odd. :)

Also, since the gradient seems to have been implemented with a check box, does that mean custom_control_strip_colors doesn't work?

[momijizukamori]

Hmm, I'll poke the core2 code for that - I didn't notice, but most of the stuff I was doing had no gradient.

That code actually ties into custom_control_strip_colors :) It just presents the options in a different way than core2 seems to suggest (I have no idea why, I was fixing up someone else's code there). Checking both boxes sets custom_control_strip_colors to 'on_gradient', while leaving the background gradient unchecked sets it to 'on_no_gradient'.

[ninetydegrees]

Sorry, I forgot to answer this. If this option has been implemented differently then I think it should be edited in Core. This is pretty confusing otherwise.

[musyc]

With the new navstrip customizing (Side note, OH MY RUTTIN' GOD THANKSSSSSSSSSSSSSSSS FOR FIXING THAT MWAH MWAH MWAH), is it easier on patchers if theme designers designate those colors in advance? I ask because (as we know, Bob) I hate custom navstrips, but I'm willing to put in the coding if that's easier on patchers.

[momijizukamori]

I'll have to talk to D, but in the absence of any other input, if there is no navstrip colors in the theme file (which is where they get saved - with all the other colors), I am personally not putting them in. Back-editing all the currently live themes was borderline nightmarish. So it's entirely up to you. If you don't want to do your designs with navstrip colors, you don't have to!

[musyc]

*flumps over* Oh, that would be a relief. I don't begrudge anyone who wants the navstrip customized, because IDIC, but I'd really rather avoid it if possible. I just didn't want to leave them out deliberately and have that result in extra work of edit/choosecolors/insert/curseatmonitor for all y'all in git or whatnot.

[momijizukamori]

We don't generally add new property lines while patching unless they're absolutely necessary (like someone assuming a white background instead of actually setting the page background to it), and I assume the navstrip will be the same.