myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anand V Nath (JIRA)" <...@myfaces.apache.org>
Subject [jira] [Commented] (TRINIDAD-2406) externalize skin repositories by using SkinProvider SPI
Date Fri, 11 Oct 2013 05:50:41 GMT

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

Anand V Nath commented on TRINIDAD-2406:
----------------------------------------

Can someone review and commit the latest patch?  	er-skin-provider-more-comments.patch 

> externalize skin repositories by using SkinProvider SPI
> -------------------------------------------------------
>
>                 Key: TRINIDAD-2406
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-2406
>             Project: MyFaces Trinidad
>          Issue Type: Improvement
>          Components: Skinning
>    Affects Versions: 2.1.0-core
>            Reporter: Anand V Nath
>         Attachments: er-skin-provider-more-comments.patch, er-skin-provider-review3.patch,
er-skin-provider-without-pom.patch
>
>
> Introduce SkinProvider SPI. Users can use this to create their own skip repositories
and expose their skins to the skinning framework.
> Provide an API to query skin using skin family, skin id, render kit - This will make
use of the existing SkinFactory APIs. Only change here is that it should go over all the available
SkinProvider SPIs to find a match.
> Create internal SkinProvider SPIs to handle the Trinidad and RCF skins (or skins defined
using trinidad-skins.xml).
> Provide an API to list all the available skins from all SkinProvider SPIs and make the
skin metadata thus available.
> Make SkinExtension part of public API so that users can use this class to create the
Skin objects which they expose through their SkinProvider SPIs



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message