Extend Twitter Bootstrap with these Bootstrap Form Helpers
vlamanna.github.com
vlamanna.github.com
works impressively well for using inside forms.
I would work on a way to have the formatting decorators (parentheses, dashes etc) only show up if there is data past that point.
So you could include " x" in the event that someone types in an extension or something like that.
Properly parsing/formatting phone numbers is harder than you'd think..
How do you specify the mask for different numbering schemes (other regions/countries)?
Do you pick one dynamically based on the selected country? Do you have that database of masks-to-country?
What if my contact number is international or foreign (even if I pick my country as USA)? Do you let the user select a mask? That feels clunky and more work than just leaving the phone number free-form..
Otherwise, I like it though.
1. It's not "all timezones across the world" but rather Windows time zones from a particular version of Windows. Most people use the much more accurate Olson database that actually gives you correct time offsets, daylight savings rules, etc.
2. Your option values, i.e. offsets, are either meaningless, or if someone actually uses them, erroneous. For example, current UTC is 17:40 but current Central is 12:40 not 11:40. Again, use the Olson database if you want better time conversions - Windows offset numbers are just a part of the timezone name, not an actual offset.
3. Timezone names differ depending on the language settings on your PC, and your list is only a small EN subset of the time zones, which, given the international nature of the list, is not very useful. If your users are in a non-American time zone, it is very likely that their time zone name is not on your list.
4. Timezone names differ from version to version, and are not backward compatible. Your list is only correct for whatever version you collected it on so it should be identified as such. Even better, if someone actually needs Windows timezones - like I said above, most likely you need the Olson timezones - they should take them from the source, by running the tzutil utility, or from microsoft.com.
Your list should be identified as what it is, a list of Windows time zones, (?) OS version. Even then, it's dangerous that whoever stumbles upon it will use the offsets for time conversions.
The name list is just one or two major cities. The assumption is users know their offset.
I appreciate your comments thought.
As far as separate checkbox for daylight savings: (1) there are more rules than just daylight savings, and moreover some timezones have daylight savings other than 1 hour (this is rare but still); (2) most languages have libraries that will calculate the timezone for you, and it's both easier and more accurate, both for the user and the developer, to use these libraries to do all the heavy lifting for you.
Where does your country-state data comes from? I've never seen a list so complete for countries outside the US!
As for the data, I've worked hard to build this and I will also soon release it in other languages.