Hi Stephen, This is not an arrogant philosophy. It is simply not designed for this. IMO, Ajax4JSF can help you.
Please check these articles : http://www.javabeat.net/articles/19-introduction-to-ajax4jsf-1.html http://www.jroller.com/HazemBlog/entry/the_magic_of_ajax4jsf Good Luck. On Sat, May 24, 2008 at 1:50 AM, Stephen Friedrich <[EMAIL PROTECTED]> wrote: > Too bad - and a strange (or arrogant) philosophy. > If there aren't any technical issues I haven't yet understood, I think > such a feature/tag should be included. > Why be so inflexible and malignant considering other technologies? > > Trinidad: All your html are belong to us? > > That might perhaps have been an Oracle strategy, but it doesn't suite an > Open Source project that well. > > My app does indeed use mostly Trinidad components. > PPR is a great feature and time saver. > I would not want to do without panelFormLayout. > Lighweight dialogs are desperately needed. > > There are just a few cases where a couple of lines of html plus > some css saves me from creating custom renderers or jsf components > (like a highly creative process train (think "advertising agency > employee with a faible for photoshop")). > > > > Scott O'Bryan wrote: > >> The reason is one of philosophy. And there has been some debate over this >> on the dev lists. I think Andrew has something which may be thrown into the >> sandbox.. however.. >> >> Trindiad renderkit works off the assumption that most of your content will >> be trinidad content. As such, it has PPR built in to each component and the >> famework necessary to support that PPR. Components external to Trinidad are >> assumed to be able to do their own PPR and that is where the philosophy >> comes in. Trinidad does not try to PPR the world, it only tries to ppr >> itself so it can better optimize. >> >> Some renderkits (like A4J) take the opposite approach and basically look >> at adding AJAX functionality to existing non-ppr enabled renterkits/content. >> Maybe you would be better off using a technology like that instead of >> Trinidad for your application. >> >> Scott >> >> Stephen Friedrich wrote: >> >>> I have some very specific components in my project, made using facelets >>> and containing mostly pure html (with some ui:repeat thrown in). >>> >>> How am I supposed to make such a component the target of PPR? >>> >>> Why isn't there a simple non-rendering trinidad component for that >>> purpose, e.g. >>> >>> <tr:fragment partialTriggers="region"> >>> ... html ... >>> </tr:fragment> >>> >>> That component could also have a rendered attribute which is nicer than >>> using <c:if> (and avoids confusing facelets). >>> >>> Is there any other component that I could misuse for that? >>> >>> >> > -- Hazem Ahmed Saleh Ahmed http://www.jroller.com/page/HazemBlog
