Re: [Django] #26066: Admin changelist could handle a table wider than the screen more elegantly

[Django]

#26066: Admin changelist could handle a table wider than the screen more 
elegantly
-+-
 Reporter:  chozabu  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  admin css style  | Triage Stage:  Accepted
  layout |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-

Comment (by chozabu):

 Oh - another option could be to simply put the filters box on the left of
 the table...

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.6dcdbd0bb4ca5fef5eb45c1b6b6c7312%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26066: Admin changelist could handle a table wider than the screen more elegantly

[Django]

#26066: Admin changelist could handle a table wider than the screen more 
elegantly
-+-
 Reporter:  chozabu  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  admin css style  | Triage Stage:  Accepted
  layout |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-

Comment (by chozabu):

 Hmm, on my wide table I did not have filters enabled yet - Just tried
 turning them on, and yes that is indeed a problem!
 Though, rather than setting the table to have an overflow which is very
 hard to scroll left and right, I'd rather make the filters box a
 dropdown...
 Having said that - I'd also be happy if my browser kept the tables
 scrollbar onscreen when overflow is active!

 Though, rather than shortening my column headers - I'm still rather happy
 with letting them wrap so
 //Barack
 Obama//
 is still shorter than
 //B. Obama//

 remains more informative, and requires less effort on my part - happy for
 the header to take an extra line or two, each page of the table is
 ~100-200 lines anyhow.

 Still - even with this in place, I have a table or two that are too wide -
 and I'd really like to have the option of wider tables too!

 timgraham, I must disagree - current situation is quite bad - a wide table
 with a full page of data is nearly unusable! Though, I do appreciate this
 ticket being renamed to a positive action, rather than negative
 identification :)

 I'll post  here if I come up with another good general purpose solution to
 solve the problem, rather than reduce it.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.6f935a4b51fca51984899afee42f0f77%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26066: Admin changelist could handle a table wider than the screen more elegantly (was: Admin handles a table of models being wider than the screen badly)

[Django]

#26066: Admin changelist could handle a table wider than the screen more 
elegantly
-+-
 Reporter:  chozabu  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  admin css style  | Triage Stage:  Accepted
  layout |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by timgraham):

 * has_patch:  1 => 0
 * type:  Bug => Cleanup/optimization
 * easy:  1 => 0
 * stage:  Unreviewed => Accepted


Comment:

 I think the current situation isn't so bad -- I agree with the point about
 trying to design the tables not to contain so much information in the
 first place. Of course, if someone comes up with a nice solution we can
 take a look.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.fc1055c47803b11e2659480586cca9b2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.