Well, the thing is that a merge is way off on the timeline.
True, but OTOH, there's nothing stopping you from grabbing
APIs and code piecemeal from Trinidad today. That doesn't
need to wait for the grand merge. And creating new APIs
that are different will just make the merge that much harder
(and push it off even further). Plus, there is quite an advantage
to taking a codebase that has already been debugged and shipped.
-- Adam
And Cagatay has something right now, why not take it in?
regards,
Martin
On 7/13/06, Mario Ivankovits < [EMAIL PROTECTED]> wrote:
> Hi!
> >
> > > Also, recognize that client-side validation is only half of the
> > > picture; you
> > > also need client-side converters.
> > Lets do this once needed. In fact, I hope Trinidad become a more
> > integral part of MyFaces so that we can use Tomahawk and Trinidad and
> > ... together :-)
> >
> >
> > How can you not need it? Verifying that dates are correctly formatted
> > is really important, for example, and that's in converter land. I'd
> > even go out on a limb and say that client converters are *more*
> > important than client validators.
> The real question is, should we reimplement all the stuff already
> existing in Trinidad, or should we try hard to make Trinidad work with
> other component libraries too.
> I would like to see the second one instead of reinventing the weel over
> and over again.
>
> Ciao,
> Mario
>
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
