I've had a similar problem in the past, where we wanted the user to
input as many phone numbers as they were comfortable with, plus an
email address. We had to have at least one of these to continue.
My solution was to have a section (e.g. a fieldset) called "Contact
details" with an instruction u
We use an "Add field" pattern. Simply put, after the field, typically
to the right, we place a [ + ] button. Selecting this button repeats
the field below. Something like this:
--
| | [ + ]
--
Selecting the [ + ] above would reveal a second field
the 3-5 phones I have at any given time.
Bryan
http://www.bryanminihan.com
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Todd
Zaki Warfel
Sent: Monday, January 14, 2008 4:21 PM
To: Switzky, Andrew
Cc: [EMAIL PROTECTED]
Subject: Re: [IxDA Discuss
Either one of those options would work if the system can accept only one
phone number. How do we accommodate for(and maybe even encourage) the
user to enter more than one phone number?
Andy
On Jan 14, 2008, Todd Zaki Warfel wrote:
Wouldn't the easiest thing to do is provide a field for input, th
Wouldn't the easiest thing to do is provide a field for input, then
either:
1. Label input box they could label it whatever (e.g. Mobile, Home,
Business)
2. A drop menu they could select from Mobile, Home, Business
This makes sure you get a phone number and lets the customer/user
select the
Behalf Of
Micah Freedman
Sent: Saturday, January 12, 2008 8:38 AM
To: [EMAIL PROTECTED]
Subject: Re: [IxDA Discuss] Complex Field Requirements
> Why not use one field for phone number instead of 3 if you need
> only 1?
First of all, the phones were just an example. I was looking at the
This is what I'm doing on a project:
Put a drop-down list next to each phone so they can indicate business/
home/mobile, but add a "required field" asterisk next to the first
phone field.
-- Kim
+ + + + + + + + + + + + + + + + + +
Kim Bieler Graphic Design
www.kbgd.com
c. 240-476
> Why not use one field for phone number instead of 3 if you need
> only 1?
First of all, the phones were just an example. I was looking at the
design pattern. In the real case, it's any one of the phones or the
email that is required. Secondly, the other phone types are not
required, but
Micah,
From a data quality standpoint (and to some degree from a user standpoint)
classifying a phone as home / cell is not the best way since a lot of people
have a cell phone as their home phone.
We concluded calling it phone usage and had the labels Personal and Business
(Work). Each phone cou
Micah,
Why not use one field for phone number instead of 3 if you need only 1?
-
Alok Jain
On Jan 11, 2008, at 3:09 PM, Micah Freedman wrote:
> I've got a form where the user must enter one of their work, home, or
> cell phone number. What's the best way, do we think, to indicate to
> users th
I've got a form where the user must enter one of their work, home, or
cell phone number. What's the best way, do we think, to indicate to
users that one of these three fields is required?
*Come to IxDA Interaction08 | Savannah*
11 matches
Mail list logo
