I'd love to see this exposed, and I think it'd be a great thing for the JSF community. It's also something we could look at during the development of JSF 2.0.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Kito D. Mann - Author, JavaServer Faces in Action <http://www.virtua.com/> http://www.virtua.com - JSF/Java EE consulting, training, and mentoring <http://www.jsfcentral.com/> http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info * Sign up for the JSF Central newsletter! http://oi.vresp.com/?fid=ac048d0e17 * From: Cristi Toth [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 01, 2007 4:13 AM To: MyFaces Development Subject: Re: [Skinning] independent MyFaces skinning module well, I refactored the old RenderingContext into more simple classes and with a lot less dependencies my approach was also Decorating existing renderers but for Tomahawk, I did one generic Renderer for all components, based on reflection it just searches for any "Class' or 'StyleClass' ending properties in the component and if it finds them then it searches for their name in the defined selectors and sets the appropriate styleClasses into the component it is really important to have the skinning independent, because one that uses tomahawk, might not want to have trinidad dependencies and this module could be adapted to ANY component set but there's still a lot to refactor in that skinning code I still have some minor things to do that Martin Marinscheck suggested, just to be sure that it's compatible with everything and that in the near future Trinidad can use this too well unfortunately, I haven't done any serious documentation, because I was really in a hurry but I'm prepared to do it and afterwards discuss with you guys what to do next thanks for the replies Best regards, Cristi Toth ------------- Codebeat www.codebeat.ro On 8/1/07, Matthias Wessendorf <[EMAIL PROTECTED] > wrote: right, also, do you've documentation already ? On 7/31/07, Simon Lessard < [EMAIL PROTECTED]> wrote: > Hello Cristi, > > It would sure be nice to have an independent common skinning module for > custom component libraries. However, I wonder what version of the skinning > module you used and how you handled dependencies while refactoring it > because there's many changes with skinning with every releases. > > > Regards, > > ~ Simon > > > On 7/30/07, Cristi Toth <[EMAIL PROTECTED]> wrote: > > Hi all! > > > > I just finished my diploma project on Skinning in MyFaces > > More exactly, what I did is refactoring out Trinidad's skinning feature > into an independent module > > I also did a small and simple module that adds this feature to Tomahawk. > > It's very simple to use. It is intended to demonstrate how easy is to add > skinning features to any component-set > > > > In the skinning module I tried to refactor and simplify the old Trinidad > code behind. > > But there is some more work to do. > > > > So how do you think this would be usable to MyFaces? > > I mean what should I do now to get this code used and improved by the > community? > > Wouldn't be nice to try to make Trinidad use this module and get rid of > the skinning code from it? > > > > I'm waiting forward to your feedBack > > > > > > Best regards, > > Cristi Toth > > > > ------------- > > Codebeat > > www.codebeat.ro > > -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ mail: matzew-at-apache-dot-org
