TimePicker about gwt-eureka HOT 2 OPEN

[jhulford] @gwt.newsgroup
The way I do it in my date/time textbox (which is more like Jens' suggestion, one textbox for date and time) it to just allow the user to type any numeric values in there and I evaluate every keydown and examine the context which the number is being entered. ie. does entering a 3 after the 9 in 9:30 make sense? No. Disallow. etc. Then evaluate the full string on focus lost if you're implementing value change handlers. It does lead to a bit of validation code and some pains handling highlighted text and key value differences between browsers, but, in my mind, it's a better user experience.

from gwt-eureka.

Both previous issues mainly solved.

• Focus problem
• typing greater than 12 hours in am/pm mode

What's left now is:

• Support for optional time value (allow null value)
• Better user experience when typing

from gwt-eureka.