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 >
