Hi Adam, Sorry if this was confusing, i certainly wouldn't want to write a pretty new framework for skinning, and this to be used only by Tomahawk. As Martin mentioned we did compare existing approaches besides Trinidad's, like the one from Tobago and I also took a look at Exadel Visual Component Platform's skinning. As far as i know these are all the current approaches for JSF and Trinidad's is the one choosed to be based on, all the features it offers are realy nice and there is room for more, like what Jeanne would like to implement, right?
The goal is to work on making the Trinidad's skinning framework become the skinning framework for MyFaces. There are things to be changed though. Like going all the way with CSS, and not use XSS for the base skins, allow skins to extend each other and not just a base skin, and allow @import rules to be used. The most important changes i was planning to do are related to parsing and merging the CSS files. Right now, Trinidad uses CSS3 syntax for component selectors, and has it's own way of parsing that syntax. What i want to do is use a standard CSS2 compliant parser (an implementation of SAC, http://www.w3.org/Style/CSS/SAC/), with minimal extensions, for example to recognize @agent rules, and have an internal model based on DOM Level 2 Style specifications ( http://www.w3.org/TR/2000/REC-DOM-Level-2-Style-20001113/). This could determine also changing the naming of the component selectors to use CSS2 valid syntax from the beginning but would eliminate the transformation of CSS3 syntax into CSS2 syntax that currently occurs. I would certainly appreciate your feedback on these plans, and help to find to the best approach for bringing Trinidad skinning framework into the overall MyFaces world. Regards, Catalin On 6/14/06, Martin Marinschek <[EMAIL PROTECTED]> wrote:
Hi Adam, inspired means it will be based on the ADF Faces skinning framework. We evaluated Tobago's and Trinidad's thing, and we decided for the Trinidad way. Whatever extensions we write, will go to both Trinidad and Tomahawk (the definitive goal would be a common module we could both base upon). regards, Martin On 6/14/06, Adam Winer <[EMAIL PROTECTED]> wrote: > > Catalin, > > One quick comment: I don't see a reason to write a skinning framework > "inspired by" the Trinidad skinning. Trinidad is part of MyFaces; why > not work on taking the Trinidad skinning framework and bringing it into > the overall MyFaces world? > > -- Adam > > > > On 6/14/06, Catalin Kormos <[EMAIL PROTECTED]> wrote: > > Hi there, > > > > I just want to say that it sounds to me like a very good ideea, having > the > > same skin take care of browsers incompatibilities for example, rather > than > > having different skins take care of that, with need of user > intervention; > > i'm working on the future skinning framework for MyFaces (at least i > hope it > > will become that), which is very much inspired by the current state of > the > > ADF Faces skinning. It's going to be done during the Google's SoC > program > > btw. Would be ok if i take some inspiration from this too? :) > > > > A concern of mine would be about the :lang pseudo selector. Maybe this > one i > > didn't get quite right, but wouldn't this interfere with the standard > usage > > of the :lang pseudo selector, for styling components that renderer their > own > > different "lang" attribute value, maybe on the same page? this might not > be > > the case for ADF Faces components though. > > > > Regards, > > Catalin > > > > > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
