Patrik K says:
> just being curious: what´s the argument against defining the rows in the
model?
Hi Patrick,
I think it would be better use of display design if you kept the rows
out of the model. You can achieve as much as you are asking by using
css.
For example, if you do the following:
1) Create your own templates dir, with an admin subdir
2) Copy django/contrib/admin/templates/admin/basesite.html to your
templates/admin/ dir
3) Modify your templates/admin/basesite.html file, extrastyle block to
include your own stylesheet
4) Put your own stylesheet (or symbolic link to one) in
django/contrib/admin/media/css
(If you are lazy - and this is perfectly fine - just modify
django/contrib/admin/media/css/globals.css)
5) put stuff like this in the stylesheet
.modulename .vLargeTextField {
width: 250px;
}
.modulename #id_fieldname {
# we can't give it quite as much room
width: 200px;
}
I think this is more powerful than your suggestion, as you can
customize it per template, per viewer (pda vs screen vs print, etc),
and cascading makes management much easier than separately defining the
models.
-rob
