[prev in list] [next in list] [prev in thread] [next in thread] 

List:       myfaces-user
Subject:    Re: [announcement] JTK: An Ajax JSF Component Development Framework
From:       noah <iamnoah () gmail ! com>
Date:       2007-10-31 15:45:16
Message-ID: 68e8c72e0710310845s2b3a9937vcfa062d202e155b5 () mail ! gmail ! com
[Download RAW message or body]

On 10/31/07, Adam Winer <awiner@gmail.com> wrote:
> On 10/31/07, Matthias Wessendorf <matzew@apache.org> wrote:
> > On 10/31/07, noah <iamnoah@gmail.com> wrote:
> > > On 10/31/07, Matthias Wessendorf <matzew@apache.org> 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"
>

I'm apologize for messing up the details, but my point is that if your
customers use Ajax4JSF, you can't sell them Trindad components, or at
least, the Ajax enabled ones wont work. Or vice versa.  Right?  As a
component author, that's kind of a problem.
[prev in list] [next in list] [prev in thread] [next in thread]