Hi all, I really really like the idea. However, I'd also like to have the skin API redesigned first to ensure better separation of concern, more extensibility, and with stricter contract XML declaration schema than what Trinidad currently has. I'm actually already working a bit on that on my side because I hope to be able to push skinning on the JSF 2.0 EG since it's not in the current public review. If such attempt is successful then the common skinning module for MyFaces should be made compatible or at least similar to 2.0 API in order to facilitate migrations and library upgrades.
Regards, ~ Simon On Fri, Dec 5, 2008 at 9:56 AM, Gerhard Petracek <[EMAIL PROTECTED] > wrote: > hello paul, > > ok - thank you for this clarification. i thought something like that. > anyway, the page isn't that clear. > > at the provided link i found: > >Generic support for skinning. Contains specific classes to use skin-api > and skin-impl with *tomahawk*. It uses SkinResourceServlet to serve css > files. > > regards, > gerhard > > > > 2008/12/5 Paul Rivera <[EMAIL PROTECTED]> > > Hi Gerhard, >> >> The current implementation has both tomahawk and generic support. >> Theoretically, we can use generic support for all myfaces component libs. >> Generic support has a tag that renders the stylesheet into the head section >> of the html output and a SkinResourceServlet that serves the actual css >> file. >> >> But projects like tomahawk already have certain features in place like >> AddResource (to put the css link in the head section of the generated html) >> and ExtensionsFilter to serve files. The tomahawk-support module is >> available to make use of these unique optimizations. >> >> But from the point of view of the jsf developer, the syntax should be the >> same. >> E.g. >> The same tag is used in the jsf page: <ms:skinStyleSheet/>. >> The same syntax is used for the *.xss or skin css syntax. >> >> Although in generic-support, there is only one added configuration of a >> servlet mapping for the SkinResourceServlet. >> >> Hope this sheds some more light on the new project. We'd love to hear >> more comments from the community. :) >> >> Best Regards, >> Paul Rivera >> >> --- On *Fri, 12/5/08, Gerhard Petracek <[EMAIL PROTECTED]>*wrote: >> >> From: Gerhard Petracek <[EMAIL PROTECTED]> >> Subject: Re: [Skinning] Independent skinning myfaces subproject >> To: "MyFaces Development" <[email protected]> >> Date: Friday, December 5, 2008, 5:14 AM >> >> >> hello leonardo, >> >> i prefer one skinning approach for all myfaces component libs. >> >> regards, >> gerhard >> >> >> >> 2008/12/5 Leonardo Uribe <[EMAIL PROTECTED]> >> >>> >>> >>> On Fri, Dec 5, 2008 at 5:12 AM, Gerhard Petracek < >>> [EMAIL PROTECTED]> wrote: >>> >>>> hello leonardo, >>>> >>>> it's an interesting idea. >>>> >>>> the summary mentions >>>> - trinidad >>>> - tomahawk >>>> - tobago >>>> >>>> the details just describe >>>> - trinidad >>>> - tomahawk >>>> >>>> is there a special reason for that? >>>> >>> >>> Hi >>> >>> Well, the idea, as described is use it on tomahawk but keep trinidad >>> compatibility of skin-api and skin-impl modules (since the code comes from >>> there, the option is open for trinidad to use it in the future, and save >>> some work keeping synchronized skin code with trinidad 1.2.x codebase). >>> Eventually, the option is open for tobago to use this library as well, but >>> I'm not checked all details yet about how could fit with this jsf component >>> library. >>> >>> regards >>> >>> Leonardo Uribe >>> >>> >>>> >>>> regards, >>>> gerhard >>>> >>>> >>>> >>>> 2008/12/1 Leonardo Uribe <[EMAIL PROTECTED]> >>>> >>>> Hi >>>>> >>>>> I would like put on consideration this proposal for a myfaces >>>>> subproject. >>>>> >>>>> The idea is simple: create a independent skinning module for skin all >>>>> myfaces jsf components libraries, taking as base trinidad skinning code. >>>>> >>>>> In other words, the long term objective is build a single skinning api >>>>> that can be use by JSF component frameworks like trinidad, tomahawk or >>>>> tobago, based on existing trinidad skin api. >>>>> >>>>> Long time ago this was discussed here >>>>> >>>>> >>>>> http://markmail.org/message/swxy73e3cth5zzaj?q=%5BSkinning%5D+independent+MyFaces+skinning+module >>>>> >>>>> but now we want to propose a solution to separate trinidad skinning >>>>> code into a separate module (some enhancements done on trinidad makes more >>>>> easier this task at this time). >>>>> >>>>> A brief description can be found at: >>>>> >>>>> http://code.google.com/p/myfaces-csi/wiki/MyfacesSkinsProposal >>>>> >>>>> Suggestions are welcome >>>>> >>>>> regards >>>>> >>>>> Leonardo Uribe >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> http://www.irian.at >>>> >>>> Your JSF powerhouse - >>>> JSF Consulting, Development and >>>> Courses in English and German >>>> >>>> Professional Support for Apache MyFaces >>>> >>> >>> >> >> >> -- >> >> http://www.irian.at >> >> Your JSF powerhouse - >> JSF Consulting, Development and >> Courses in English and German >> >> Professional Support for Apache MyFaces >> >> >> > > > -- > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces >
