Opened 18 years ago
Closed 18 years ago
#6634 closed (invalid)
Default widgets and formfields in dbfields
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Forms | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
What shall I do when I want to have dbfield with another default formfield and/or widget?
- Use arguments formfield and/or widget in the constructor of the dbield.
- Use argument formfield (directly for formfield or indirectly for widget) in the constructor of the dbield.
- Create custom dbfield with overwritten method formfield_for_dbfield.
- Do something else.
- Don't to it.
What is the right method? I hope that 1 or at least 2. And I would like to create patch for them.
Note:
See TracTickets
for help on using tickets.
Please have design discussions like this on the django-developers mailing list. otherwise, there's no possible way to resolve the ticket and on the mailing list, everybody can participate.