+1. There were just a few small enhancements required, everything else was supported by the skinning system out of the box.
Like I say, there is a lot of power in Trinidad, as Leonardo demonstrated, but not all of it transfers to the stock renderkit. I think it would be good to inject some enthusiasm into the community in order to beef up Trinidad's componentry. Leonardo, good work on this research!! Scott Sent from my iPhone On Jun 22, 2012, at 8:23 AM, Leonardo Uribe <[email protected]> wrote: > Hi > > I tried to mix Trinidad casablanca skin with some Themeroller skins. > Just take a look at these two images: > > https://issues.apache.org/jira/secure/attachment/12533046/redmond%2Bcasablanca-2.png > https://issues.apache.org/jira/secure/attachment/12533047/south-street%2Bcasablanca-2.png > > It just shows how powerful is actually MyFaces Trinidad. > > regards, > > Leonardo Uribe > > 2012/6/22 Joachim Schrod <[email protected]>: >> Scott O'Bryan wrote: >>>> >>>> E.g., I'm active in TeX development since 1982. Without our user >>>> communities, our mailing lists and newsgroups, our fora, where >>>> user-level questions are answered, we developers couldn't make it. >>>> IMHO, both aspects of community are needed. Or do you think that >>>> the postings here with user questions are not answered because >>>> they're too difficult? >>> I fully agree with this Joachim. Thing is, there are some >>> questions that get answered and some that don't. Targeted and >>> informed questions where the user has done their research and has >>> discovered an issue typically get a response. Ones where people say >>> "My app is broken, here it is, fix it" don't. >> >> The latter is clear, no OSS project is going to do that. For >> specific problems, creation of a minimal example is a demand that's >> mandatory if one wants to keep sane. >> >>>>> If there is some >>>>> functionality you'd like to see in Trinidad, please open up a >>>>> discussion on the dev list about it. We'd like to hear from you. >>>> Hmm, my 1st wish would be simple: >>>> Package the SVN-tagged 1.2.15 release. :-) >>> HAHA. ;) I get ya! Like I say, 1.2 has not been my priority and >>> unless you're looking at taking it over, I think it will be the >>> last 1.2.. >> >> Since I sit here at 1:40 am, working on the next TeX Live release >> and on our new CTAN Web site, I'm afraid I'll have problems to pack >> even part-time responsibility for another open source project in my >> schedule. More than two hours a day on a regular base for personal >> OSS projects is not possible. :-) >> >>> I do have a question for you since you seem to be wanting it >>> released... It's one that I have not got an answer for. Do you >>> think that 1.2.15 should have the few outstanding bugs commited to >>> the already tagged release or would you like to see the code from >>> the experimental branches merged in as well. >> >> The few outstanding bugs are sufficient, IMO. >> Integration of experimental branches can/shall be done by someone else. >> >> Probably a (semi-official?) declaration that 1.x is closed as long >> as no new maintainer is forthcoming, but work on 2.x continues, >> would be helpful, too. I know several commercial environments, >> where such EOL announcements are business cases to budget >> transformation projects. >> >> Thanks for taking the patience to answer my emails. >> >> Joachim >> >> -- >> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- >> Joachim Schrod, Roedermark, Germany >> Email: [email protected] >>
