Hi Bart, it seems that it's working now, and it's extending the base skin as it states in documentation. I think the problem was that we had a huge CSS with some syntax errors and the merged CSS had this errors too (although I wasn't able to find them... the base CSS was really huge, trust me). After cleaning the base CSS, clearing cache and restarting server, all worked as expected. Don't know if this is useful for you...
Thanks for your help. Regards, -- Rafa PS: Trinidad's demo has an example on how to extend a skin, using as basis Purple and extendig by Purple bigfont. Hope this helps anyone. On Tue, Feb 2, 2010 at 10:14 AM, Bart Kummel <[email protected]> wrote: > Hi Rafa, > > I have been struggling with the "extends" functionality as well. My > experience is the same as yours: it doesn't work. I asked nearly the same > question as you on this list about a year ago, but I didn't get a > satisfying > answer. I think the "best" way to extend a skin is just copying the CSS and > images and adapt them. I tried several scenarios with the "extends" > functionality, but neither of them gave me a working solution. > > Perhaps you should file a bug in JIRA about this. At least the > documentation > is incomplete, but I think the implementation isn't complete either. > > Hope this helps, although it is probably not the answer you hoped for... > Good luck! > > Best regards, > Bart Kummel > > 2010/1/29 Rafa Pérez <[email protected]> > > > Hi all, > > > > I have been reading about the extending facilities for skinning in > > Trinidad. > > I have created one skin as basis and then have created another one just > to > > override a couple of styles. My configuration is as follows: > > > > - In trinidad-config.xml: > > > > <?xml version="1.0" encoding="windows-1252"?> > > <trinidad-config xmlns="http://myfaces.apache.org/trinidad/config";> > > <skin-family>skin_extended</skin-family> > > <accessibility-mode>inaccessible</accessibility-mode> > > </trinidad-config> > > > > - In trinidad-skins.xml: > > <?xml version="1.0" encoding="ISO-8859-1"?> > > <skins xmlns="http://myfaces.apache.org/trinidad/skin";> > > <skin> > > <id>skin_base.desktop</id> > > <family>skin_base</family> > > <render-kit-id>org.apache.myfaces.trinidad.desktop</render-kit-id> > > <style-sheet-name>skins/prueba/prueba.css</style-sheet-name> > > </skin> > > <skin> > > <id>skin_extended.desktop</id> > > <family>skin_extended</family> > > <render-kit-id>org.apache.myfaces.trinidad.desktop</render-kit-id> > > <style-sheet-name>skins/prueba/prueba_ext.css</style-sheet-name> > > <extends>skin_base.desktop</extends> > > </skin> > > </skins> > > > > The fact is that the styles seems to be merged in the generated CSS file, > > but aren't applied to the page. It's quite weird, because in firebug's > CSS > > tab you cannot see all the styles that are present in the generated CSS > > file. > > > > Am I misunderstanding anything? Is it possible that the generated CSS > file > > is wrong at any point and the browser does not parse it right? > > > > Regards, > > > > -- Rafa > > >
