On second thoughts, producing a new DateTimeField component is probably wiser.
I'm impressed by the HTML5 "datetime-local" input type. Browsers that don't support it should gracefully degrade to plain textfield. A DateTimeField component based on this HTML5 element would be lighter weight than the existing DateField component, as there would be no need for server round trips to wire the field and picker. Dates would be formatted and parsed on component rendering and submission only. What do you think? Regards, Chris. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
