[Define New Theme] 3. We need to use a pre-processor such as LESS or which ever is decided upon at least in development.

[brunoais]

Has anyone here looked at this?
http://pleeease.io/
Sounds like a cool thing to use that solves many of the issues that CSS preprocessors have been used for, it seems to be quite lightweight and it is a lot some sort of the cutting edge CSS today (on browsers that don't support it). I'll investigate more on it.

[callumacrae]

Has anyone here looked at this?
http://pleeease.io/
Sounds like a cool thing to use that solves many of the issues that CSS preprocessors have been used for, it seems to be quite lightweight and it is a lot some sort of the cutting edge CSS today (on browsers that don't support it). I'll investigate more on it.

Too small, use autoprefixer for browser prefixing and myth.io for spec-conforming variables and stuff in CSS.

LESS is way better, though. Not sure why you have a problem with it.

[brunoais]

My main problem with LESS is the power it gives that allows making the CSS a mess. Outside of it, I'm perfectly fine with it, I actually intent to use it on my next project.
Anyway, I still prefer something more on the: "The syntax of today now" than "new syntax that is processed and later becomes a mirror of todays syntax".

[hanakin]

how exactly does less provide messy css if you run it through gulp with csslint?

[callumacrae]

My main problem with LESS is the power it gives that allows making the CSS a mess. Outside of it, I'm perfectly fine with it, I actually intent to use it on my next project.
Anyway, I still prefer something more on the: "The syntax of today now" than "new syntax that is processed and later becomes a mirror of todays syntax".

How does it allow you to make the CSS a mess? Are you talking about too deeply nested or overqualified selectors? If so, a decent linter will sort that out (as will correct development in the first place).

how exactly does less provide messy css if you run it through gulp with csslint?

RECESS is where it's at! Supports LESS, too, and handles compiling and beautification if required.

[callumacrae]

This is a good read about why CSS post-processors are a bad idea: http://blog.rodneyrehm.de/archives/30-C ... -Myth.html

[Senky]

Using preprocessor is a must in today's development. As well as using Grunt to parse it. So what about starting using Grunt?

[hanakin]

their is a topic for that specifically but we are using gulp which is far more powerful.

Demo: http://hanakin.github.io/phpBB-StyleGuide/
Repo: https://github.com/hanakin/phpBB-StyleGuide/

[phpdummie]

Unless you are intending to implement on-the-fly LESS compilation inside phpBB and distribute the less files as a part of the standard distribution, the benefit of this is entirely lost on me. Sure, you can make all the LESS files a part of the graphics kit, that would help those who use LESS. However making this some sort of requirement is strange.

And I wish people would stop talking about LESS variables because they are variables only for those who have no clue what a variable is.

[hanakin]

Unless you are intending to implement on-the-fly LESS compilation inside phpBB and distribute the less files as a part of the standard distribution, the benefit of this is entirely lost on me. Sure, you can make all the LESS files a part of the graphics kit, that would help those who use LESS. However making this some sort of requirement is strange.

And I wish people would stop talking about LESS variables because they are variables only for those who have no clue what a variable is.

Its a requirement for development purposes for us not for the end user, with the added benifit for any user who can work with LESS (front-end Designers/Developers)