[wp-trac] [WordPress Trac] #22862: Consider a CSS preprocessor
WordPress Trac
noreply at wordpress.org
Tue Aug 6 00:13:31 UTC 2013
#22862: Consider a CSS preprocessor
-----------------------------+------------------------------
Reporter: chriswallace | Owner:
Type: feature request | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Administration | Version:
Severity: normal | Resolution:
Keywords: |
-----------------------------+------------------------------
Comment (by rmccue):
Worth mentioning that there's also [https://github.com/leafo/scssphp
scssphp] by the same author as the previously mentioned lessphp. Jetpack
actually bundles both of these for the Custom CSS feature.
Replying to [comment:39 wonderboymusic]:
> Currently converting my patch to SCSS - I don't like it. Syntax sucks,
and you can't overload mixins - meaning, you can't have multiple versions
of a mixin that take a different number of arguments.
Also true of PHP. I'm not sure you really need it to be honest.
> As it stands right now, SASS by default compiles via Ruby gem - a
lateral move from NodeJS.
Anecdotally, I've found it much, much easier to install and use Sass (via
Compass) on Windows.
> No matter what the method of development, at the end, someone's going to
have to push a button that compiles the code so they can run it in the
browser.
That's true, and I think both the tools are at parity there.
I'll take a look at your SCSS version this afternoon and see if there's
anything we can do better in that. There's a few things in there I can see
that I'd improve, so I'll see if I can clean it up a little (unless
someone else gets to it first).
--
Ticket URL: <http://core.trac.wordpress.org/ticket/22862#comment:41>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list