[jira] Commented: (TRINIDAD-89) Server side CSS constants for .css files

["Jeanne Waldman (JIRA)" <de...@myfaces.apache.org>]

    [ https://issues.apache.org/jira/browse/TRINIDAD-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512979 ] 

Jeanne Waldman commented on TRINIDAD-89:
----------------------------------------

We have this feature with aliases. And it seems that aliases are more useful, because you can have more than one css property per alias.

.AFDefaultFont:alias {
  -tr-rule-ref: selector(".AFFontFamily:alias");
  font-size: 11px;
}

af|inputText::content { 
  -tr-rule-ref: selector(".AFDefaultFont:alias");
}

> Server side CSS constants for .css files
> ----------------------------------------
>
>                 Key: TRINIDAD-89
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-89
>             Project: MyFaces Trinidad
>          Issue Type: Improvement
>          Components: Skinning
>    Affects Versions: 1.0.2-core
>            Reporter: Leonardo Uribe
>         Attachments: patchConstants6.patch
>
>
>  Working in my Google Summer of Code, I have found that It would be cool, when you define a css skin file that you can do something like this:
> @constants {
> 	greencolor: #97f099;
> 	f90color : #f90; 
> }
> .AFPanelNavigationHorizontal ul li.off a:hover, .AFPanelNavigationHorizontal ul li:hover a, .AFPanelNavigationHorizontal ul li.over a {
>     background: greencolor;
>     color: f90color;
> }
> Like in server side CSS in PHP.
> I have created a patch that adds this feature. With this, yo can define local constants variables in a .css file that is used as trinidad skin file.
> (If you define a constant in a base skin, the extended skins don't see it). It's a simple but powerful idea.
> Suggestion for improvements of this topic are welcome.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.