Opened 8 years ago

Closed 8 years ago

#6634 closed (invalid)

Default widgets and formfields in dbfields

Reported by: Petr Marhoun <petr.marhoun@…> Owned by: nobody
Component: Forms Version: master
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

What shall I do when I want to have dbfield with another default formfield and/or widget?

  1. Use arguments formfield and/or widget in the constructor of the dbield.
  2. Use argument formfield (directly for formfield or indirectly for widget) in the constructor of the dbield.
  3. Create custom dbfield with overwritten method formfield_for_dbfield.
  4. Do something else.
  5. 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.

Change History (1)

comment:1 Changed 8 years ago by mtredinnick

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to invalid
  • Status changed from new to closed

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.

Note: See TracTickets for help on using tickets.
Back to Top