Here are some thoughts I had after reading through the slides and gist:
- I don't think I'd often use
*prop
. I don't keep track of which properties/values need vendor prefixes (or nonstandard code) to work with the browsers I'm targeting. I use Autoprefixer, which uses data from the Can I Use? database. - A command that generates JSON with keys representing the variable names used in a .gcss file would be handy.
- I feel like I missed the point of storing style variables in JSON. One benefit is "different site themes"--but most of my projects include a "_variables.scss" file that could be swapped out--oh, but that would require recompiling scss. I see. I think I get it now. Never mind!
Cool, thanks for the reply--very informative! I'll file a bug for the utility.
A couple more questions about
*prop
: (I don't mean to obsess about*prop
--I'm sorry if this comes across that way. I know your project/idea is bigger than a single implementation detail.)One of the things I like about Autoprefixer is that it affects more than vendor prefixes, e.g. property names and values:
justify-content: space-between;
becomes
Would
*justify-content: space-between;
do the same in Grips?Autoprefixer can target specific browser versions (so that generated CSS is not bloated with IE6 styles if those are unnecessary). Will Grips itself have a configuration file (maybe JSON) where browser support (or other variables) could be defined?