Yes, I said it. Going forward I do not think that Adobe should waste time on implementing JS Code libraries. Ext, YUI and others exist so you can easily integrate them into your code already. In the last few months alone I believe there have been 2 or 3 version upgrades alone of the Yahoo YUI tool and a 1 major version upgrade for Ext.

If you want to have an AJAX driven drop down, write it yourself or download a custom tag, or better yet; write the custom tag yourself and distribute it freely. I would much rather see the time spent by engineers working on ColdFusion spent working on the server side portion of ColdFusion vs. doing these seemingly 'cool' integrations. Don't custom tags exist for this purpose alone? Why build it into a server side product?

I'm tired of seeing posts and emails and requests to implement further feature sets, upgrade versions or change libraries all together. ColdFusion does not need to be my meeting ground of technology. If you had spent 2 more minutes writing your code you could have implemented the Ext library yourself, probably done a better job and you won't be beholden to a server side technology for your client side code...

Flame on

In\r\na recent project I had the need to have multiple objects tied a single\r\ndate picker pop-up. What I was really going for was a DIV field to show\r\nthe date so it was true read only and to stuff the value into a hidden\r\ntext field as well.
\r\n
I needed to use it in multiple places and it needed to be flexible for\r\nfuture uses, so I came up with this quick package\r\nYAHOO.EGPS.Utils.DatePicker. It allows you to choose multiple targets\r\n(for the resulted value) and multipletriggers that will make the date-picker \"pop-up\".
\r\n