It's probably just a wart from HTML. The XyzInput widgets correspond more or less to <input type="xyz"> tags, but the Textarea widget corresponds to <textarea>. There's only two tags like this that are HTML form elements but are not <input> tags, the other being <select>, whose widget "Select" similarly has one capital letter and no "Input" suffix. So the naming is consistent, and agrees with the HTML tags, even though it looks a little weird without that knowledge.
Best, Alex Ogier On Sat, Jan 19, 2013 at 3:26 AM, Wim Feijen <[email protected]> wrote: > Hi guys, > > I was just wondering, and maybe my English language skills are > insufficient. > > Django defines several widgets, like: > TextInput > PasswordInput > HiddenInput > DateInput > DateTimeInput > TimeInput > Textarea > > Why isn't Textarea CamelCased: TextArea, like the other widgets? It seems > inconsistent. But maybe I am missing something? > > -- Wim > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/django-developers/-/1V71BI3iUBQJ. > 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-developers?hl=en. > -- You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en.
