[wp-trac] [WordPress Trac] #22862: Consider a CSS preprocessor

WordPress Trac noreply at wordpress.org
Tue Aug 6 16:49:52 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):

 Replying to [comment:44 jorbin]:
 > With the new setup that @koop just announed on the make blog
 (http://make.wordpress.org/core/2013/08/06/a-new-frontier-for-core-
 development/) , we won't need to push any buttons.  We'll be able to use
 grunt tasks that can watch andauto run our preprocessor.  Both SASS
 (standalone and with Compass) and LESS have grunt tasks ready for us to
 use.

 Yep, it fits in perfectly with this ticket. (I actually noticed that
 [https://github.com/koop/develop/commit/c7a359b5b2ffe41e706334bc7a184e10804a8771
 on GitHub] a few days ago, hence the updates here. ;) )

 Based on discussions with nacin, the Apache license of LESS may be a bit
 prohibitive here, whereas both Sass and Compass are MIT licensed. I
 personally don't think it matters, since this is tooling rather than part
 of the source, but it may matter in that it's generating code distributed
 with WP. I suspect a similar argument to [http://www.gnu.org/licenses/old-
 licenses/gpl-2.0-faq.html#CanIUseGPLToolsForNF using GCC] applies, but
 don't quote me on that.

--
Ticket URL: <http://core.trac.wordpress.org/ticket/22862#comment:46>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list