I'll chime in on this topic as well. The Javascript objects that are available in CF8 are, as Rey said, simplistic and for people who need a neat little widget in their application. I am still heavily reliant upon ajaxCFC because I use the Ext library with the jQuery adapter. For advanced AJAX development, the CF8 widgets are too restrictive.
On Oct 4, 8:34 am, "Christopher Jordan" <[EMAIL PROTECTED]> wrote: > Ohhhh... wrappers around the jQuery UI components sounds cool. Gotta keep us > posted about that one! :o) > > Chris > > On 10/3/07, Rey Bango <[EMAIL PROTECTED]> wrote: > > > > > > > Brook, > > > CF8 provides quite a number of options in terms of prebuilt Ajax > > controls but I tend to refer to them as "intro" widgets. They don't > > provide the level of functionality available in jQuery or many other > > libs and do not adhere to any form of progressive enhancement. Also, few > > users want to use Spry for their development and CF8, out of the box, > > already includes an outdated and non-upgradeable version of YUI. > > > AjaxCFC most certainly remains relevant as it provides a very easy > > interface for making Ajax calls to your CF templates and leveraging > > native CF data types. In addition, since jQuery is included in AjaxCFC, > > you now have the capability to leverage the wealth of jQuery plugins > > available. And since it's open source, you can upgrade things as needed > > instead of having to wait until Adobe patches the libs. > > > Rob and I will be working on updating AjaxCFC to jQuery v1.2.1 soon and > > possibly creating wrappers around jQuery UI components. > > > Rey... > > > Brook Davies wrote: > > > Can Rob or Rey shed some light on this? Is ajaxCFC still relevant with > > > the release of CF8? > > > > BrookD > > --http://cjordan.us
