#3368: Add USStateField and PhoneNumberfield to django.newforms.fields
---------------------------+------------------------------------------------
Reporter: jkocherhans | Owner: adrian
Status: new | Component: django.newforms
Version: SVN | Resolution:
Keywords: | Stage: Design decision needed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 1 | Needs_better_patch: 0
---------------------------+------------------------------------------------
Comment (by jkocherhans):
Replying to [comment:2 Marc Fargas <[EMAIL PROTECTED]>]:
>
> Hi jkocherhans,
> Please take a look at [http://groups.google.com/group/django-
developers/browse_thread/thread/d15dd089da7d810/184da9764e48ea2e?lnk=gst&q=regex&rnum=3#184da9764e48ea2e
this thread] almost the same could apply for newforms fields.
>
> But anyway, maybe instead of creating a new field type, why don't you
create a new widget? In this case I think a widget makes more sense than a
field.
Oh yes. I knew I saw that thread :) I think {{{USStateField}}} and
{{{PhoneNumberField}}} are still things we're going to want regardless of
how they are implemented. They are core django model fields and AFAIK
aren't going away anytime soon. I don't think a widget would work here.
We're talking about validation, not display.
--
Ticket URL: <http://code.djangoproject.org/ticket/3368#comment:4>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
