Refactor form widgets in order to be usable outside of form contexts

basxsoftwareassociation / bread

Engine to create database applications based on Django and the IBM Carbon Design System

BSD 3-Clause "New" or "Revised" License

19 stars 2 forks source link

Refactor form widgets in order to be usable outside of form contexts #16

Closed saemideluxe closed 2 years ago

saemideluxe commented 3 years ago

The current implementation is very unflexibel, good examples to draw from are select.py and multiselect.py (using context variables instead of "magically" appearing properties in the overwritten render method of the widget.

saemideluxe commented 3 years ago

[ ] Define interface for components which are usable as form-input elements. Just for the form-functionality to work a component only needs to set the "name" and "value" attribute correctly (in most cases). Most of the other attributes are only required for correct display I think.
[ ] Maybe get rid of boundfield in all components and rely on the values from djangos build_widget_attrs on a field?
[ ] Add option to customize used form elements (aka replace a defautl widget)

saemideluxe commented 2 years ago

Yey, mostly done :)