The jQuery controls look very nice. Also quite heavy, though, but if you used jQuery extensively in application this overhead would not be too bad. I think a site should avoid having heavy controls on the front page, to minimise the initial load.
I think there should be a distinction between jQuery and jQueryUI. Only the latest one is heavy (production jQuery is only 19kb - see jquery.com) It's also much easier to learn and use than Prototype. Also several JS/CSS resources are available on google/public servers (with correct version), so sites using form there, can ease their own traffic, and are also highly cached . Maybe the performance filter could have this option too: to include conditionally from public urls the correct version. Regarding Date/Time, there are several other jQuery plug-ins for this (on that list), so it's not necessarily to use the most heavy one jqueryUI Date picker. Another option would be to use for the default Click Date control a "select" based approach (like the one in Rails) - it is quite efficient too - I think it's much much better than a simple text field. For pure time entry there are several other interesting time entry plug-ins too: http://keith-wood.name/timeEntry.html (the same author has a date entry and a date picker plug-in too) http://www.jnathanson.com/index.cfm?page=jquery/clockpick/ClockPick (innovative way of selecting time) IMO all jQuery (& plug-ins) based Click controls should be put into a separate package (since many of them may overlap with Prototype based, and usually users don't want both in their application - the same way one is not using Cayenne and Hibernate in the same application). Thanks, A. -- View this message in context: http://n2.nabble.com/Click-Feature-Concepts-and-Roadmap-tp2543751p2548720.html Sent from the click-user mailing list archive at Nabble.com.
