On 10/31/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > On 10/31/07, noah <[EMAIL PROTECTED]> wrote: > > On 10/31/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > > > did a quick look and found these two statements: > > > -Apache Trinidad requires that the developer create the tag library > > > file and a renderer. > > > > > > => you write meta-data and a renderer. The meta-data is used to > > > *generate* TLD/the components. Metadata is also useful for tools. > > > > Sorry, I must have misunderstood. I wrote most of that six months ago, > > and there wasn't any documentation about how it works/how to use it. > > > > > > > > -Components developed with Trinidad only work properly with the > > > Trinidad view root. > > > > > > => there is no "TrinidadViewRoot" class. > > > > Sorry if I misunderstood, but there wasn't any documentation about it > > when I wrote that. Am I wrong that Trinidad generated components will > > only work with Trinidad? I'm not trying to spread misinformation, > > that is just my understanding of the way things worked a few months > > ago. > > there is a <tr:document> OR <trh:html / body> that render the links to > the required source like CSS / JavaScript, but you can mix Trinidad > with Tomahawk, for instance.
... and even these aren't really necessary. You can get by with a simple trh:styleSheet to pull in the CSS. (It used to be necessary to use one of tr:document, tr:panelPartialRoot, or trh:body for PPR to work, but that restriction went away back in 1.0.2.) -- Adam > The big issue general is that lot's of component libs don't work 100% > with others, I hope that JSF2 will provide a "better integration > mechanism"
