views v2 corner images: pelt.screen.css, hex rcX.svg.xslt and 
corner-importsX.svg.xslt
--------------------------------------------------------------------------------------

         Key: FOR-723
         URL: http://issues.apache.org/jira/browse/FOR-723
     Project: Forrest
        Type: Improvement
  Components: Views  
    Versions: 0.8-dev    
 Environment: any
    Reporter: kevin
    Priority: Minor


new pelt.screen.css that
references corner images with hex values so the old skinconf is
not used ie:
#header .round-top-left-small {
    background-image: url(../skin/images/rc-t-l-5-X294563-X4a6d8c-
X4a6d8c.png);
    background-repeat: no-repeat;
    background-position: top left;
}
I have made comments in pelt.screen.css to understand where and how
all images are used. There are some comented out.

plus

rcX.svg.xslt and corner-importsX.svg.xslt
that deal with hex values rather than skinconf color names
to go in main/webapp/skins/common/images as a fallback

Note:
an update to resouces.xmap to match this request is needed:
         <map:match pattern="skin/images**/*c-*-*-*-X*-X*-X*.png">
           <map:call resource="read-svg2png-corner-resource">
             <map:parameter name="path" value="images/{1}" />
             <map:parameter name="name" value="{2}cX" />
             <map:parameter name="orientation-tb" value="{3}"/>
             <map:parameter name="orientation-lr" value="{4}"/>
             <map:parameter name="size" value="{5}"/>
             <map:parameter name="bg-color-name" value="{6}"/>
             <map:parameter name="stroke-color-name" value="{7}"/>
             <map:parameter name="fg-color-name" value="{8}"/>
           </map:call>
not sure if this goes in the core it would be a fallback from themer plugin
resources.xmap if the request wasn't matched?

Also themer sitemap.xmap used lm for *.css matches not sure how it should be
used here. So I let it go to resources.xmap for above testing.



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira