Ruby on Rails Wednesday, February 1, 2012

On Wed, Feb 1, 2012 at 11:53 AM, Colin Law <clanlaw@googlemail.com> wrote:
On 1 February 2012 09:58, Peter Vandenabeele <peter@vandenabeele.com> wrote:
> I had experience that the typical administrative user, is _very_ fast at
> typing
> dates on her numeric keypad. It is really a lot easier for her to type a
> requested
> delivery_date as 300412 (that is delivery on 30 April 2012) even if we as
> developers frown upon it. Maybe a series of 3 boxes as you suggest
> may also be a good compromise.

I agree that for what one might call an 'internal' app where users
know what is expected that a single box may be ok.

Indeed ! That was an internal application. On the external side, we had
a Datepicker (slower to use, but no ambiguity).

 
In the case of
three boxes then provided tab can be used between them this can still
be quick to type.

Or even jump to next box automatically (my banking app does that for the
account number that has 3 blocks in Belgium). But the inconvenience is
that I cannot copy paste a full account number to it then :-/


>
> The protection against the problem of misinterpretation, is then to show the
> fully expanded date (preferably with a local fast javascript), to verify
> that the
> computer interpreted the data correctly. And use localisation, where users
> in
> EU get dd/mm/yyyy as default setting and users in US get mm/dd/yyyy as
> default input setting.

The most safe way is possibly to provide a drop down select box for
the month then there is no confusion, but it is slower to enter.  I
think date_select will provide this.
Of course there is no "correct" answer to this, different applications
require different solutions.

+1

Peter

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.

No comments:

Post a Comment