I don't really agree that a forgiving format should be implemented here. This might very well be a matter of process than just technical. And sometimes, a rule is simply a rule and people need to learn about that once - important is how you teach them. Programming a forgiving input field costs heaps and maybe the vast majority already uses military time - waste of resources?
This is something that only one group can tell you; the users. Ask many of them, implement their main suggestion, test whether they indeed like what they thought they'd like. This because there are more possible solutions: - You could use a singe field with the colon character in there. Input could go via typing 4 numerical chars (only). Disadvantage: you'd have to type a leading zero. - You could use two fields, one for the hours, one for the minutes, with a colon in between. Disadvantage: they'd need to push the Tab button but I guess that could be done automatically as well. - You can use an informational label for the field,e.g. 'time (24h)' - You could process the data they enter in real time, and give feedback on that by changing information next to, or underneath the input fields into '= 7.23 pm' or a full sentence, if you like. Basically, I'd just ask the users first :) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=31500 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
