> I'd like to see these Controls moved into their own sub-project -> click-prototytype, making it very clear to users and focusing the projects efforts.
You mean an Apache Click "subproject", or just a subdirectory (like click examples), or something totally out of Apache like the case of click-jquery?
I proposed for the begining to just use a simple different package, as ANT can be simply changed to create for that package a:
"click-prototype-2.3.0.jar" that would contain only those prototype based classes.
> Supporting jQuery, Prototype, Mootools, YUI, RightJS inside Click doesn't scale and doesn't work in practice.
True. Besides they're mostly never used together, but only one at a time.
> DateField however will be difficult.
Another option might be to have by default a real "DateField" (not a Calendar), i.e. something with comboboxes, like the Rails DateTime Select
from the beginning of this video:
as a fallback mechanism when none of the other mentioned solutions are used.
> HTML5 datetime might help here though. By default DateField could be marketed as HTML5 compliant and have no JS dependency.
> The click-calendar project can be used as an alternative if HTML4 must be supported (HTML4 will be valid until 2020).
Interesting approach. Could be this process automated somehow, so that the users don't need extra effort to have this work with their existing apps?