I'm a bit late to chime in on this thread, but I think the problems with the calendar control and d/m vs m/d formatting can both be overcome. Before that though, I'm wondering about this timezone issue - why does timezone support matter to tracks, which appears to only support one timezone and has todos at day-level granularity? (heck, ruby barely supports timezones out of the box without the tzinfo project) The RDoc for chronic claims it can support both styles of date format, though it doesn't mention how it would disambiguate 11/12 as nov 12 or dec 11. A possible solution to that is to try and parse the date as normal, which will catch any standard date formats, then if that fails, pass the string on to chronic for further processing. As for the interaction with the calendar control, how about configuring the calendar control to pop from a button next to the text field rather than when the focus is in the text field - that way people can use either date entry method? As in the way datebocks ( http://datebocks.inimit.com/ ) works. Or we could just use that now that I stumbled across it. (though it too seems to have issues with iso vs us date format) Just some thoughts about possible solutions. The keyboard shortcuts that were proposed will work for some people, but they're pretty obscure :/
_______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
