[ 
https://issues.apache.org/jira/browse/TOBAGO-898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Udo Schnurpfeil resolved TOBAGO-898.
------------------------------------

    Fix Version/s: 1.5.0-alpha-2
                   1.5.0
       Resolution: Fixed

> CSS class naming: Replace "aspect" with "markup"
> ------------------------------------------------
>
>                 Key: TOBAGO-898
>                 URL: https://issues.apache.org/jira/browse/TOBAGO-898
>             Project: MyFaces Tobago
>          Issue Type: Improvement
>            Reporter: Udo Schnurpfeil
>            Assignee: Udo Schnurpfeil
>             Fix For: 1.5.0-alpha-2, 1.5.0
>
>
> To get more logical and more strict naming conventions for CSS classes, 
> rename all existing aspects to markups.
> E. g. tobago-in-required -> tobago-in-markup-required
> Advantage: The "aspects" can be defined in the theme-config per renderer. So 
> we can define, if an renderer supports e. g. the required feature.
> For migrating a theme from Tobago 1.0 to Tobago 1.5 all matching classes must 
> be renamed like this:
> tobago-<rendererName>-<aspect> -> tobago-<rendererName>-markup-<aspect>
>  
> For all aspects: inline, required, error, disabled, readonly.
> For the aspect "default" see TOBAGO-880. 
> Also some other CSS class names will be renamed and using "markup" e. g. 
> tobago-sheet-row-odd -> tobago-sheet-row-markup-odd, because the idea of 
> "odd" is a property of markup, and not a subcomponent.

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

Reply via email to