> On 12/27/05, patrick k <[EMAIL PROTECTED]> wrote:
>> - how do i change the numrows for a textarea-field?
>
> You can do this with CSS; create custom admin templates that include
> some custom CSS code.
what i meant was changing the numrows for each textarea-field seperately.
e.g., a body-field needs more space than a summary (at least in my app).
why not thinking about extending the textfield-model with something like
"numrows=xxx"?
>> - why is it always the first column of the list which is linked to the
>> detail-page? when listing the ID, i´d like the ID to be the first field in
>> the list. nevertheless, i´d like the title to be linked. is that possible?
>
> We've never had a need to link any other column to the detail page. We
> use the first column for consistency. It's currently not possible to
> choose which column gets linked. (Of course, it *is* possible to
> designate the order of the fields on the change list, so, if you want
> the title linked, you can just make sure the title is first in the
> "list_display" setting.)
well, i´d like to have the ID first and the title (=linked) second.
however, i can live with that (although it´s not very pretty IMHO).
>> - we have automatic fields for createdate and updatedate (auto_now,
>> auto_now_add). what about automatically inserting the logged in user who
>> creates (or updates) the record? i don´t know about anybody else, but i need
>> that all the time. that´s especially interesting when using manipulators,
>> because with "request.user" you won´t have the ID of the user (if i´m right
>> here?).
>
> This currently isn't possible. Implementation suggestions are welcome!
i´m not much of a python-programmer (coming from PHP, still trying to figure
out the whole thing). maybe someone else needs that feature!!??
right now, i´m passing the userid via
return render_to_response('manage/milestones_form', {
'form': form,
'user': user_list,
'group': group_list,
'project': project,
'userid': userid,
}, context_instance=Context(request))
where userid is request.user.id
in the template i´m using a hidden input-field.
of course, that only works with custom admin-pages.
>> - the many-to-many javascript filter interface does work in the
>> admin-interface, but it does not work with my own page based on
>> AddManipulator.
>
> You might need to include some JavaScript in your custom HTML page for
> that. See django/contrib/admin/media/js/SelectFilter.js.
already included
core.js
RelatedObjectLookups.js
calendar.js
DateTimeShortcuts.js
CollapsedFieldsets.js
SelectBox.js
SelectFilter2.js (resp. SelectFilter.js)
still, doesn´t work.
patrick
