.catbase virtual overflow: hidden border-radius: 5px padding: 5px 10px 5px margin-bottom: 4px border: 1px solid rgba(0,0,0, .15) font: 700 1.4em/20px $big_font img vertical-align: -3px .cat extends .catbase background-color: #b3afa9 color: white a color: white text-decoration: underline font-size: .92em text-shadow: none :hover color: #fc9 | .cat final background-color: #c3b9c3 border-color: #fd9604 border-width: 2px 0 0 0 text-shadow: black 0 1px 2px .table_list & margin: -5px .title extends .cat padding: 4px 8px border, margin: 0 #sidebar & margin-top: 6px a color: #faf8f8 |
1. | The main Wess core... |
2. | The list of functions that create the actual CSS and JS files and pass them through Wess or other functions. |
Wow, I just learn to theme a little bit... And now I have to learn this? :P
While such a tool would be great to sort things out, i do wonder if its the way people use CSS that tends to make files big and cluttered. Too often they dress something with a unique style that could be just as well made into a common class. If they took the time to strip it down to bare bones, and THEN start looking at where things would be different, it would be better.Curve theme is a prime example of just adding template specific style after style..when theres clearly so much common items between pages. Evey little tweak gets a new style...
Personally I doubt I will be using it that much - having it the old cluttered way force me to be more efficient(and i haven't up to now, really, but with my latest I do try to do exactly that).
Another thing is also that making a design - at least when everything isn't already drafted out - tends to be a nonlinear thing. You think of a certain look, and don't bother looking at existing styles, just throw in a new to get that *look* and move on in the creative process. When the time comes to clean up, its often too easy to just let it be."it works" lol.Been victim to that too.
Thats why i think this will appeal more to coders doing design - but not necessarily designers doing code. ;)
But who'd want to destroy their life on duplicating common CSS rules when you can use this new syntax with extend and all the neat stuff?
It'd be nice, er no, awesome if CSS4 implemented at least some of those features.
link=msg=262641 date=1308472960]
I belong to the school of semantics, by far, although I think using inheritance is only sensible.
I know I'm often the first person to write my own version of something, and I love learning from it and see if I can do better. And here as well, I think writing a PHP version makes a lot of sense.
But, considering Sassy recently moved to using CSS-style syntax,
and I personally hate Python style syntax, perhaps it makes sense to gravitate to the rules of another syntax?
That could make the documentation needs lighter.
WeCSS is the old name... John being the only one who prefers it, and there are more things to worry about that this... :P
Anyway, if you'd read the feature list, it has its own topic....