Support SCSS (Sass) (variables, mixins, nesting, inheritance)
Stylizer would be the ideal UI over the top of Sass. You're already kind of doing mixins with your little diamond properties. Why not allow users to define their own mixins and variables? The grid would make an idea UI for nesting. If you implement these things, why not follow the well trodden patterns already established by Sass?
More info on Sass: http://sass-lang.com/
-
MrAnalogy commented
You could just set something up (maybe even use something like Kickstarter) where people sign up and pay for a pluggin ($30 or whatever) and when you get to enough orders, you agree to do it.
I realize that integrating a framework would be tough but VARIABLES would be INCREDIBLY useful (if only for COLOR)
-
WizOne Solutions commented
What is the current stance on this giving the rising popularity of SCSS + Compass?
-
xmRipper commented
I would prefer http://lesscss.org/ support. More popular, more functional.
-
dwhite commented
SASS is the new default in Rails 3.1, more reason to add it to Stylizer!
-
Paul Albrecht commented
I agree! SASS in combination with Stylizer would be a huge WIN. And i agree that it COULD be tough to figure out the UI to make it usable.
As Stylizer becomes more popular (especially now with the Mac Version) demand for this technology will rise.
SASS Programmers would love Stylizer. -
Bryan Downing commented
The problem with not supporting sass is that you can't use Stylizer if you want to use sass. It's a tough choice to make.
-
dave08 commented
I think this is a great idea! I'm currently using lessPhp for my symfony project, and have a big conflict... the big advantages of Stylizer or the easier to manage lessphp stylesheets. The mixins help me integrate any css framework I want w/o touching the html. I can define color schemes w/ variables and use the variables throughout my stylesheets, so that I can change one or two values to change the whole theme. I can use partials that get compiled into one file, to make css more module (with mixin functions to parameterize the values).
You already have a certain amount of this implemented in your shortcut properties, why not make them user definable and give the option to save them behind the scenes as sass or lesscss. The variables can be some kind of theme tab that holds all the values in a grid and these values can be used in the proper places like the font-family list of values (but highlighted differently...). This can all be implemented in a way understandable by designers. If the users want regular css, the additional info can be saved in the comments or in a user specified file...
Sound nice?
-
Adminskybound (Admin, Skybound Software) commented
The problem with CSS variables is that designers don't think like programmers. It was in Stylizer years ago, but we took it out because a grand total of zero people were using the feature, and it was increasing the visual footprint of the interface. The idea of re-using values is great in theory, but in practice, it needs to be implemented in a different way than the obvious "programmer way" in order for it to make sense to designers.
Rule nesting is useful, but it's tough to get the interface/hotkey combinations right.
Allowing people to add their own shortcut properties is not as easy as you might think.
-
charlesroper commented
I forgot to mention, with Sass support, you could also employ the riches present in the Compass metaframework.
http://compass-style.org/
Intro screencast for Compass (highly recommended): http://vimeo.com/11671458