Recent Topics

1 Oct 06, 2015 20:47    

Having enabled the Prism plugin a few days ago, I'd begun to conclude that I wasn't totally happy with the way it was rendering colours for the code. On digging in a little, it seems that its not using the built in prism.css, and is using the CSS for the skin I'm using. What I'm not sure, is whether that's down to something in the way Prism has been implemented into b2evo, or perhaps the way the skin (Vastitude) has been put together, though I'm not too sure where to look to clarify that.

Can one of the team offer any suggestions on that?

2 07 Oct 2015 01:55

I think we merged prism CSS into a global CSS file for performance reasons.

You may override all the prism styles by re-adding or re-loading the prism.css in the specific skin you use.

3 07 Oct 2015 06:54

That may well answer the question then, as it does appear that any codeblock I drop in to a post is picking up the general colouration from my skin. The skin is one that I've been carrying around for the last 10 years and has been pretty much untouched in that time. I'll do some comparisons with my test installation and just see if I can confirm what's going on.

4 07 Oct 2015 16:54

Yes, definitely different in terms of the way the CSS is being used. On the test installation, everything is coloured as I'd expect. The other difference is that on the test installation, the codeblock is quite a bit shorter in height than the live one, which appears to be displaying all the code I posted.

It looks like I'll be uploading the newer version once I've changed the header image and what have you.

5 08 Oct 2015 20:38

Hmmm... it's fixed width. This is going to require more radical surgery than I'd imagined. Scalpel!


Form is loading...