<!–texy–>[13] See the "calc() function in the CSS3 draft":[http://www.w3.org/TR/2006/WD-css3-values-20060919/#functional]

<!–texy–>[6] Are you serious? Something like that would be the greatest thing in CSS3 for me, hope it happens .

<!–texy–>[11] No, I'm not using PSPad. Every programmer, even the beginner, can program a simple program or script for that easy replacements. But it doesn't solve the problem. How would you use it in large projects, how would you edit and adjust CSS with it in large stylesheet containing hundreds selectors, how would you apply it within a production teams? There are thousands options for a "workaround" of this, but only the native implementation into CSS can really solve it.

Additionally, imagine, when will be CSS3 available for public and how could look out the internet in the future. Reusable APIs, predefined templates, a need for easily adjustable CSS skins, variable color palettes with single layout etc. is what we can meet even today…

<!–texy–>If you are using PSPad editor, you can try this script http://temp.bulant.cz/down/komanc/preprocessingCSS/ver%201.1/preprocessingCSS.js (copy this script to directory in /PSPad/Script/JScript). After start (click in Skript menu or press CTRL+SHIFT+ALT+A hotkey) action will be create new file in directory with original "template" file.
It coming-out from syntax this article. But I programmed it only for fun. No warranty

<!–texy–>If anybody is interested in my CSS Alias Concept from around 2003, just go to:
http://www.mezzoblue.com/archives/2005/09/16/css_optimiza/#c023873

I know that saving of bandwidth is not that important as it used to be, but aliases could be applied to make the working with long CSS files easy for users.

<!–texy–>And why not (before CSS3 and browsers support for CSS3) this way:

/*source stylesheet:*/
body {
color: #bad001;
background: #bad002;
}
a:hover {
color: #bad002;
background: #bad001;
}

/*source replacements:*/
#bad001 #003366
#bad002 #f0f0f0

…and from source stylesheet and source replacements generate (once) output -> live stylesheet for web… And #badxxx values must not by just colors, it can by any posible values for property. Or more: snippet of CSS code – something like class definition in CSS (not in (X)HTML), …

Ak sú tam chyby tak sorry, ale angličtinu zvládam čítať, s písaním je to už horšie… Išlo mi o myšlienku.

<!–texy–>[8] I don't think so. I consider the @-notation correct, for the @-prefix are not used yet in property values, as well as consistent, because the "@" is typical operator used in CSS (unlike the dollar symbol). In fact, the CSS grammar "allows":[http://www.w3.org/TR/css3-syntax/#grammar] @-keywords as the valid property value (but it's not used yet, AFAIK).

However, the syntax really doesn't matter, the principle is important. I don't care, if other syntax is used to allow predefined constants or variable values in CSS, I also would be satisfied.

<!–texy–>Something like that will be nice, but using `@` for variables reference is imho fail.

I'm preparing asp.net preprocessor for something like this:

/–code
/* definition */
@var $company-blue: #2465B7;
@var $company-green: #A0B424;

a{color:$company-blue;}
a:hover{color:$company-green;}

/* other rules… */
\–code

It will be mor powerful with preprocessor conditions like `@if IE6 { … }`.

<!–texy–>I agree with your suggestion, pixy. In my mind, there is a similar idea – variables do not represent values but attribute-value pair ev. multiple definitions (this is maybe closer to the inheritance conception [1]). But also I'm not able to evaluate practical side of each approach.

<!–texy–>[5] Yes. Anyway, expressions are already a part of the CSS3 draft.