Re: [Django] #18129: Capitalization of verbose_name bad design decision. Why waste computer power.

[Django]

#18129: Capitalization of verbose_name bad design decision. Why waste computer
power.
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Uncategorized|   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:  capitalize   |  Unreviewed
  verbose_name   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by lukeplant):

 Replying to [comment:4 mail@…]:
 > I have an verbose_name label that reads something like this "xABC"...

 Try this:
 {{{
 class NoUpper(unicode):
 def upper(self):
 return self
 def __getitem__(self, key):
 return self.__class__(super(NoUpper, self).__getitem__(key))

 ...

 verbose_name = NoUpper(u"xABC")
 }}}

 My brief experiments suggest this should work:
 {{{
 >>> capfirst(NoUpper(u"xABC"))
 u'xABC'
 }}}

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18129: Capitalization of verbose_name bad design decision. Why waste computer power.

[Django]

#18129: Capitalization of verbose_name bad design decision. Why waste computer
power.
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Uncategorized|   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:  capitalize   |  Unreviewed
  verbose_name   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by mail@…):

 I agree with the contributor: when verbose_name is explicitely set it
 should at least be possible to disable automatic capitalisation. I have an
 verbose_name label that reads something like this "xABC". The lowercased x
 in the Acronym is semantically relevant. Auto-capitalization destroys
 that. Hopefully there's an easy, and consistent way to override that
 behavior.

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18129: Capitalization of verbose_name bad design decision. Why waste computer power.

[Django]

#18129: Capitalization of verbose_name bad design decision. Why waste computer
power.
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Uncategorized|   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:  capitalize   |  Unreviewed
  verbose_name   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by adrian):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 We rely on verbose_name *not* having initial caps in your models, and we
 add caps wherever appropriate. It wouldn't work the other way around
 (expecting models to have initial caps, and lower-casing them when
 appropriate) because a verbose_name might be an all-caps acronym that
 shouldn't *ever* be lower-cased. And displaying verbose_names without an
 upper case just looks ugly. We have standards. :-)

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18129: Capitalization of verbose_name bad design decision. Why waste computer power.

[Django]

#18129: Capitalization of verbose_name bad design decision. Why waste computer
power.
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.4
Component:  Uncategorized|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  capitalize   |  Unreviewed
  verbose_name   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Evil Clay ):

 I'm sorry, i meant no harm with the title, just an attempt to describe
 relevant points in a short line. I like django very much, I programed in
 java for 5 years using Apache Wicket. But i can say that in many ways
 django is better. So thank you all, you have done a great job, and sorry
 for this "spam" comment, just wanted to set thing straight.

 to add something to the matter at hand, i understand the backward issue i
 saw the changes in admin where all verbose_names were changed to
 lowercase. But i feel this is something that has to be done sooner or
 later.

 Maybe you could add an default setting that will ensure current behavior
 but will also rise an deprecation warning on server start and you can
 override this setting you a project local settings file to turn off the
 Capitalization and this will also silence the deprecation warning.
 As for the admin part, probably a lot of manual work to capitalize the
 verbose_names. I could help with that.

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18129: Capitalization of verbose_name bad design decision. Why waste computer power.

[Django]

#18129: Capitalization of verbose_name bad design decision. Why waste computer
power.
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.4
Component:  Uncategorized|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  capitalize   |  Unreviewed
  verbose_name   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Despite the needlessly aggressive tone, this might be interesting,
 therefore not rejecting immediately (which was my first reflex when I read
 the title).

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #18129: Capitalization of verbose_name bad design decision. Why waste computer power.

[Django]

#18129: Capitalization of verbose_name bad design decision. Why waste computer
power.
--+
 Reporter:  anonymous |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Uncategorized |Version:  1.4
 Severity:  Normal|   Keywords:  capitalize
 Triage Stage:  Unreviewed|  verbose_name
Easy pickings:  0 |  Has patch:  0
  |  UI/UX:  0
--+
 When djnago generates names from model members, capitalization may be a
 good thing (but should be configurable, todays modern web designs often
 use lowercase labels [yes you can do this in css, but why must I?]). But
 to capitalize verbose_names is an waste of computer power and makes django
 slower. Verbose name should be displayed as it was entered without any
 change when using in modelforms form.as_

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.