On Mar 29, 3:10 pm, "Todd O'Bryan" <[EMAIL PROTECTED]> wrote:
> On Thu, 2007-03-29 at 13:02 +0000, Jonas Maurus wrote:
> > > I think there are lots of situations where you need to normalize the
> > > labels with some string. Why not just make it an optional parameter to
> > > the Form class with a default value.. maybe ":"?
>
> > > Rune
>
> > so that would make
>
> > name = forms.CharField(label='What role do you want to play?')
>
> > into
>
> > name = forms.CharField(label='What role do you want to play',
> > punctuation='?')
>
> > for *sometimes* saving you from typing one character? I still think it
> > makes no sense to append anything at all. Not to mention the pending
> > unicodization... the Japanese, Chinese, Korean and Cyrillic alphabets
> > don't use western punctuation...
>
> > Unless there's a better argument than sometimes saving one character
> > or being backwards-compatible to 0.96, I'm still against this.
> > However, I don't carry much weight around here ;-)
>
> I think he was suggesting in the form, not each field:
>
> form = forms.Form(punct='')
>
> would let you create a form with no colons. You could also do something
> like
>
> form = forms.Form(punct='-->')
>
> or whatever. This would also allow you to override the punctuation based
> on locale. Seems like a not bad solution. People who hate the colons
> could create their own subclass of Form and use it instead of the
> default form and then they wouldn't have to set the punct value each
> time.
>
> Todd
You're of course right.
I see that this would allow Django to be backwards-compatible by
introducing this new parameter, so I could go for that because I think
backwards-compatibility is very important. I still disagree with the
concept anyway because I think that:
* it's a newbie-trap ("where does this colon come from it's neither
in the template nor in my string???"and
* it doesn't really save any significant amount of time or space (12
characters saved on a form with 12 fields) and
* it splits your label string between two classes so it's a concern
for l10n and
* it's not very friendly to languages that don't use english/western
punctuation
So I guess it comes down between backwards-compatibility and "doing
the right thing as currently defined by Jonas Maurus". I think that
it's clear that requiring to write a full template for all form-fields
just to remove the colon would be really bad, at least. Btw, how does
the Django-community usually decide such a thing? by a vote like in
Apache projects? or do we wait for one of the core developers to show
up? :-)
cheers
Jonas
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
