I agree, more components does not make for a better spec. The place for neat components are libraries such as Tomahawk. The last thing I want in JSF 2.0 are some funky ajax-ified components, but rather more native
thanks! :) third-party is the place to go. standard JSF should be standard html
support for ajax across the board. I get the feeling that products like ajax4jsf would have a lot fewer bugs if the JSF lifecycle provided better hooks for what they are trying to do.
framework and api; as said. do you know mabon ? quite interesting approach.
By the way, I noticed that Jacob refers to you as "the great Matthias." Either you've been leading legions of soldiers to conquer neighboring countries, or you're developing quite the reputation in the JSF world. ...then again, it could be the beer talking. ;)
yeah, I think the beer. My in person i am taller. Perhaps it was that ? :)
Regards, Jeff Bischoff Kenneth L Kurz & Associates, Inc. Matthias Wessendorf wrote: > I expect framework extensions from jsf6 (see [1]) and perhaps an > client side api. > But, please no random-components and no calendar and no xxx-components. > Let's work on the API / Framework, but on *blowing up* the sepc with > new components. > > -M > > [1] http://www.jroller.com/page/mwessendorf?entry=jsf_version_6 > > On 11/1/06, Jeff Bischoff <[EMAIL PROTECTED]> wrote: >> Sounds painful. >> >> I really hope that a future version of the JSF spec integrates AJAX more >> directly into the framework. For now, I am seeing more ajax components >> showing up in Tomahawk/Sandbox and that at least is something. >> >> Regards, >> >> Jeff Bischoff >> Kenneth L Kurz & Associates, Inc
-- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
