What on earth are Django-crispy-forms?<\/strong><\/h2>\n\n\n\nDjango-crispy-forms is a high-level Python web framework. The primary motivation here is to encourage quick development and make an attractive design.<\/p>\n\n\n\n
Moreover, the Django framework was built by professional developers. It tackles the issues of web development hassles so that IT specialists can focus on creating their apps pain-free. There\u2019s no need to reinvent the wheel. Django project<\/a> is free and open for any aspiring developer.<\/p>\n\n\n\nHow does Django play?<\/strong><\/h2>\n\n\n\n![\"\"](\"https:\/\/alternative-spaces.com\/blog\/wp-content\/uploads\/2019\/04\/Z7GxFMfCznWlJuqOQ_cI4F8-bcs_1sw8-1024x466.jpg\")
<\/figure>\n\n\n\nDjango DRY (fun word for crispy) forms can help to build reusable programmatic layouts. Here the developer has full control of the rendered HTML without the necessity to write HTML in templates. All this can happen without breaking the standard way of doing things in Django, so it plays nice with any other form application.<\/p>\n\n\n\n
Django-crispy-forms is built to support Python 2.7\/Python 3.3+ and Django 1.8\/Django 1.10+<\/p>\n\n\n\n
The application basically gives such options:<\/p>\n\n\n\n
- A filter called |crispy | that will render neat div based forms. You can imagine it as the built-in methods: as_table, as_ul and as_p. The output cannot be tuned up, but it can be easily launched to life.<\/li>
- A tag named {% crispy %} will render a form which is tailored to developer\u2019s configuration and particular layout setup. This gives computer gurus lots of \u201csuper-powers\u201d without much hassle, helping them to save loads of time.<\/li><\/ul>\n\n\n\n
The boons of Django-crispy-forms<\/strong><\/h2>\n\n\n\nDjango-crispy-forms helps developers bring some style to input forms\u2019 properties (i.e., method, CSS classes or \u201csend button\u201d) on the backend. The good news: these forms don\u2019t have to be re-written in the template. In this way, the plain Django forms become more readable. It is also easier to render them. The programmer can even restrict them to one life of code.<\/p>\n\n\n\n
More significantly, Django-crispy-forms improves the look of the forms. They add CSS classes to all the buttons, individual fields so that an entire form looks gorgeous. <\/p>\n\n\n\n
Installing Django-crispy-forms is a piece of cake<\/strong><\/h2>\n\n\n\nDevelopers need to follow a standard procedure to install django-crispy-forms. They need a pack manager \u201cpip\u201d or \u201ceasy_install.\u201d Then, they add the installed App \u2018cryspy_forms\u201d to the INSTALLED_APPS list.<\/p>\n\n\n\n
If the Bootstrap<\/a>(or any other CSS framework as Foundations)<\/a> is used, then it needs to be imported to the project. That\u2019s all to it. For more details and advanced options, check out the official django-crispy-forms documentation<\/a>.<\/p>\n\n\n\nHow Django crispy forms layout saves the day<\/strong><\/h2>\n\n\n\n![\"\"](\"https:\/\/alternative-spaces.com\/blog\/wp-content\/uploads\/2019\/04\/TqWepPJJFITLS-UM7O2JoeYbKG_OvqZZ-1024x723.jpg\")
<\/figure>\n\n\n\nDjango-crispy-forms can define another strong class: Layout. This class is an excellent help for rendering the fields of a form. It opens access so that fields can be ordered and wrapped in structures. Then HTML is added, and various classes are set, etc. All of this is an excellent asset at hand for a busy programmer. <\/p>\n\n\n\n
Now the developer doesn\u2019t have to write a custom form template \u2014 no need for programmatic layouts any longer. The programmer can attach the layout to a helper. Layouts are optionally used, but the bottom line here is that they are the best stuff offered by django-crispy-forms. So they shouldn\u2019t be overlooked. <\/p>\n\n\n\n
Layout objects are the building bricks for Layout. They are the DNA of the form building process.<\/p>\n\n\n\n
Feel free to dig deeper into it by reading about Universal layout objects<\/a>. It\u2019s important to remember that a different template is generated by various components which have a different purpose.<\/p>\n\n\n\nFor instance, let\u2019s imagine a developer wants to have a couple of different layouts for their form. How would this form class look like in real life? NB: Some layout objects are tied to a particular template.<\/p>\n\n\n\n
Imagine ButtonHolder is for uni_formtemplate_pack, while FormActions is for bootstrap template pack. Here are some django crispy forms layout examples: <\/p>\n\n\n\n
from crispy_forms.helper import FormHelper<\/em><\/p>\n\n\n\nfrom crispy_forms.layout import Layout, Fieldset, ButtonHolder, Submit<\/em><\/p>\n\n\n\nclass ExampleForm(forms.Form):<\/em><\/p>\n\n\n\n […]<\/em><\/p>\n\n\n\n def __init__(self, *args, **kwargs):<\/em><\/p>\n\n\n\n self.helper = FormHelper()<\/em><\/p>\n\n\n\n self.helper.layout = Layout(<\/em><\/p>\n\n\n\n Fieldset(<\/em><\/p>\n\n\n\n ‘first arg is the legend of the fieldset’,<\/em><\/p>\n\n\n\n ‘like_platform’,<\/em><\/p>\n\n\n\n ‘favorite_watch’,<\/em><\/p>\n\n\n\n ‘favorite_price’,<\/em><\/p>\n\n\n\n ‘favorite_restaurant’,<\/em><\/p>\n\n\n\n ‘notes’<\/em><\/p>\n\n\n\n ),<\/em><\/p>\n\n\n\n ButtonHolder(<\/em><\/p>\n\n\n\n Submit(‘submit’, ‘Submit’, css_class=’button white’)<\/em><\/p>\n\n\n\n )<\/em><\/p>\n\n\n\n )<\/em><\/p>\n\n\n\n super(ExampleForm, self).__init__(*args, **kwargs)<\/em><\/p>\n\n\n\nWhile rendering the form, the developers use now:<\/p>\n\n\n\n
{% load crispy_forms_tags %}<\/em><\/p>\n\n\n\n{% crispy example_form %}<\/em><\/p>\n\n\n\nWhat\u2019s next? The fields are included in the fieldset, whose legend will be switched to \u2018first arg is the legend of the fieldset.\u2019 The order of the fields\u2019 will be in this fashion: like_platform, favorite_watch, favorite_price, favorite_restaurant, and notes.<\/p>\n\n\n\n
Then the submit button can be wrapped in a <div class=”buttonHolder”> which Django uni-form turns from ashes to beauty. That button is under the jurisdiction of its own CSS class which is set to button white.<\/p>\n\n\n\n
Now, let\u2019s say the developer wants to explain the notes. In such a case HTML layout object can be used:<\/p>\n\n\n\n
Layout(<\/em><\/p>\n\n\n\n Fieldset(<\/em><\/p>\n\n\n\n ‘Tell us your favorite stuff {{ username }}’,<\/em><\/p>\n\n\n\n ‘like_platform’,<\/em><\/p>\n\n\n\n ‘favorite_watch’,<\/em><\/p>\n\n\n\n ‘favorite_price’,<\/em><\/p>\n\n\n\n ‘favorite_restaurant’,<\/em><\/p>\n\n\n\n HTML(“””<\/em><\/p>\n\n\n\n <p>We use notes to become smarter get better, <strong>please help us {{ username }}<\/strong><\/p><\/em><\/p>\n\n\n\n “””),<\/em><\/p>\n\n\n\n ‘notes’<\/em><\/p>\n\n\n\n )<\/em><\/p>\n\n\n\n)<\/em><\/p>\n\n\n\nThe fieldset legend is \u201ccontext-conscious,\u201d and it can be written as if it were a piece of a template (where the form will be rendered to). The HTML object will tag a message before the notes are provided. It\u2019s also \u201ccontext-aware.\u201d Layout objects such as Fieldset, Div, MultiField, and ButtonHolder can contain other Layout objects within.<\/p>\n\n\n\n
Let\u2019s play a bit further. This time we\u2019ll do a different layout for the same form:<\/p>\n\n\n\n
Layout(<\/em><\/p>\n\n\n\n MultiField(<\/em><\/p>\n\n\n\n ‘Tell us your favorite stuff {{ username }}’,<\/em><\/p>\n\n\n\n Div(<\/em><\/p>\n\n\n\n ‘like_platform’,<\/em><\/p>\n\n\n\n ‘favorite_watch’,<\/em><\/p>\n\n\n\n css_id = ‘special-fields’<\/em><\/p>\n\n\n\n ),<\/em><\/p>\n\n\n\n ‘favorite_price’,<\/em><\/p>\n\n\n\n ‘favorite_restaurant’,<\/em><\/p>\n\n\n\n ‘notes’<\/em><\/p>\n\n\n\n )<\/em><\/p>\n\n\n\n)<\/em><\/p>\n\n\n\nThis time a MultiField has been used which is a layout object. As a rule of thumb, it can be utilized in the same places as Fieldset. The difference here is: all fields can be rendered wrapped in a div. If some potential errors happen in the form submission, then they are displayed in a list farther from the field.<\/p>\n\n\n\n
Welcome to the world of universal layout objects<\/strong><\/h2>\n\n\n\nThe layout objects are found in module crispy_forms.layout, but they are not specific to a template pack. Let\u2019s take them one by one and see their usage examples:<\/p>\n\n\n\n
- Div:<\/strong> It wraps fields in a <div><\/em>:<\/li><\/ul>\n\n\n\n
Div(‘form_field_1’, ‘form_field_2’, ‘form_field_3’, …)<\/em><\/p>\n\n\n\nDISCLAIMER:<\/strong> There is a possibility to set kwargs in all layout objects that will be utilized as HTML attributes. The developer should use css_class<\/em> as class<\/em> is a keyword in Python. For example:<\/p>\n\n\n\nDiv(‘form_field_1’, style=”background: white;”, title=”Explication title”, css_class=”bigdivs”)<\/em><\/p>\n\n\n\n- HTML:<\/strong> It\u2019s quite a powerful layout object. It should be used to render pure HTML code. In essence, it acts as a Django template. HTML has access to the overall context of the page where the form is being rendered.<\/li><\/ul>\n\n\n\n
- Field:<\/strong> A principle layout object. It can be used for setting attributes in a field or rendering a particular field with a custom template. That is how the necessity to override the field\u2019s widget can be avoided. That is the way to pass over a weird attrs<\/em>dictionary:<\/li><\/ul>\n\n\n\n
Field(‘password’, id=”password-field”, css_class=”passwordfields”, title=”Explanation”)<\/em><\/p>\n\n\n\nField(‘slider’, template=”custom-slider.html”)<\/em><\/p>\n\n\n\nThis layout object can be used for an easy Django\u2019s widgets extension.<\/p>\n\n\n\n
- Submit:<\/strong> Used to help to create submit button. There are two parameters. The first one is the name<\/em> attribute of this very button. The second one is the value<\/em> attribute:<\/li><\/ul>\n\n\n\n
Submit(‘search’, ‘SEARCH’)<\/em><\/p>\n\n\n\nSubmit(‘search’, ‘SEARCH’)<\/em><\/p>\n\n\n\nis rendering to:<\/p>\n\n\n\n
<input type=”submit” name=”search” value=”SEARCH” class=”submit submitButton” id=”submit-id-search” \/><\/em><\/p>\n\n\n\n- Hidden:<\/strong> was creating a hidden input:<\/li><\/ul>\n\n\n\n
Hidden(‘name’, ‘value’)<\/em><\/p>\n\n\n\n- Button:<\/strong> for creating a button:<\/li><\/ul>\n\n\n\n
Button(‘name’, ‘value’)<\/em><\/p>\n\n\n\n- Reset:<\/strong> was used to create a reset input:<\/li><\/ul>\n\n\n\n
reset = Reset(‘name’, ‘value’)<\/em><\/p>\n\n\n\n- Fieldset:<\/strong> It wraps fields in a <fieldset><\/em>. The first attribute is the command line for the fieldset legend. As indicated earlier, it acts as a Django template:<\/li><\/ul>\n\n\n\n
Fieldset(“Text for the legend {{ username }}”,<\/em><\/p>\n\n\n\n ‘form_field_1’,<\/em><\/p>\n\n\n\n ‘form_field_2’<\/em><\/p>\n\n\n\n)<\/em><\/p>\n\n\n\nWe\u2019ve just scratched the surface of django-crispy-forms capacities. Of course, more things can be done with their help. For example, django views can switch on “helper.” It can also be overwritten.<\/p>\n\n\n\n
Django is also helpful if you want to submit class for button creation: <button type=”submit” class=”btn btn-primary”>Sign in<\/button>. Moreover, developers can create their own templates for specific fields within a form.\\<\/p>\n\n\n\n
Final thoughts<\/strong><\/h2>\n\n\n\n![\"\"](\"https:\/\/alternative-spaces.com\/blog\/wp-content\/uploads\/2019\/04\/ULhvqJLq8Qh3d7xR2GuqgMY0FWwLjShC-1024x723.jpg\")
<\/figure>\n\n\n\nIf you\u2019re curious to delve deeper into the complexities of django crispy, feel free to digest its official documentation<\/a>. Additionally, you can watch this video<\/a> for a better grasp of this topic. <\/p>\n\n\n\n
How does Django play?<\/strong><\/h2>\n\n\n\n<\/figure>\n\n\n\nDjango DRY (fun word for crispy) forms can help to build reusable programmatic layouts. Here the developer has full control of the rendered HTML without the necessity to write HTML in templates. All this can happen without breaking the standard way of doing things in Django, so it plays nice with any other form application.<\/p>\n\n\n\n
Django-crispy-forms is built to support Python 2.7\/Python 3.3+ and Django 1.8\/Django 1.10+<\/p>\n\n\n\n
The application basically gives such options:<\/p>\n\n\n\n
- A filter called |crispy | that will render neat div based forms. You can imagine it as the built-in methods: as_table, as_ul and as_p. The output cannot be tuned up, but it can be easily launched to life.<\/li>
- A tag named {% crispy %} will render a form which is tailored to developer\u2019s configuration and particular layout setup. This gives computer gurus lots of \u201csuper-powers\u201d without much hassle, helping them to save loads of time.<\/li><\/ul>\n\n\n\n
The boons of Django-crispy-forms<\/strong><\/h2>\n\n\n\nDjango-crispy-forms helps developers bring some style to input forms\u2019 properties (i.e., method, CSS classes or \u201csend button\u201d) on the backend. The good news: these forms don\u2019t have to be re-written in the template. In this way, the plain Django forms become more readable. It is also easier to render them. The programmer can even restrict them to one life of code.<\/p>\n\n\n\n
More significantly, Django-crispy-forms improves the look of the forms. They add CSS classes to all the buttons, individual fields so that an entire form looks gorgeous. <\/p>\n\n\n\n
Installing Django-crispy-forms is a piece of cake<\/strong><\/h2>\n\n\n\nDevelopers need to follow a standard procedure to install django-crispy-forms. They need a pack manager \u201cpip\u201d or \u201ceasy_install.\u201d Then, they add the installed App \u2018cryspy_forms\u201d to the INSTALLED_APPS list.<\/p>\n\n\n\n
If the Bootstrap<\/a>(or any other CSS framework as Foundations)<\/a> is used, then it needs to be imported to the project. That\u2019s all to it. For more details and advanced options, check out the official django-crispy-forms documentation<\/a>.<\/p>\n\n\n\nHow Django crispy forms layout saves the day<\/strong><\/h2>\n\n\n\n<\/figure>\n\n\n\nDjango-crispy-forms can define another strong class: Layout. This class is an excellent help for rendering the fields of a form. It opens access so that fields can be ordered and wrapped in structures. Then HTML is added, and various classes are set, etc. All of this is an excellent asset at hand for a busy programmer. <\/p>\n\n\n\n
Now the developer doesn\u2019t have to write a custom form template \u2014 no need for programmatic layouts any longer. The programmer can attach the layout to a helper. Layouts are optionally used, but the bottom line here is that they are the best stuff offered by django-crispy-forms. So they shouldn\u2019t be overlooked. <\/p>\n\n\n\n
Layout objects are the building bricks for Layout. They are the DNA of the form building process.<\/p>\n\n\n\n
Feel free to dig deeper into it by reading about Universal layout objects<\/a>. It\u2019s important to remember that a different template is generated by various components which have a different purpose.<\/p>\n\n\n\nFor instance, let\u2019s imagine a developer wants to have a couple of different layouts for their form. How would this form class look like in real life? NB: Some layout objects are tied to a particular template.<\/p>\n\n\n\n
Imagine ButtonHolder is for uni_formtemplate_pack, while FormActions is for bootstrap template pack. Here are some django crispy forms layout examples: <\/p>\n\n\n\n
from crispy_forms.helper import FormHelper<\/em><\/p>\n\n\n\nfrom crispy_forms.layout import Layout, Fieldset, ButtonHolder, Submit<\/em><\/p>\n\n\n\nclass ExampleForm(forms.Form):<\/em><\/p>\n\n\n\n […]<\/em><\/p>\n\n\n\n def __init__(self, *args, **kwargs):<\/em><\/p>\n\n\n\n self.helper = FormHelper()<\/em><\/p>\n\n\n\n self.helper.layout = Layout(<\/em><\/p>\n\n\n\n Fieldset(<\/em><\/p>\n\n\n\n ‘first arg is the legend of the fieldset’,<\/em><\/p>\n\n\n\n ‘like_platform’,<\/em><\/p>\n\n\n\n ‘favorite_watch’,<\/em><\/p>\n\n\n\n ‘favorite_price’,<\/em><\/p>\n\n\n\n ‘favorite_restaurant’,<\/em><\/p>\n\n\n\n ‘notes’<\/em><\/p>\n\n\n\n ),<\/em><\/p>\n\n\n\n ButtonHolder(<\/em><\/p>\n\n\n\n Submit(‘submit’, ‘Submit’, css_class=’button white’)<\/em><\/p>\n\n\n\n )<\/em><\/p>\n\n\n\n )<\/em><\/p>\n\n\n\n super(ExampleForm, self).__init__(*args, **kwargs)<\/em><\/p>\n\n\n\nWhile rendering the form, the developers use now:<\/p>\n\n\n\n
{% load crispy_forms_tags %}<\/em><\/p>\n\n\n\n{% crispy example_form %}<\/em><\/p>\n\n\n\nWhat\u2019s next? The fields are included in the fieldset, whose legend will be switched to \u2018first arg is the legend of the fieldset.\u2019 The order of the fields\u2019 will be in this fashion: like_platform, favorite_watch, favorite_price, favorite_restaurant, and notes.<\/p>\n\n\n\n
Then the submit button can be wrapped in a <div class=”buttonHolder”> which Django uni-form turns from ashes to beauty. That button is under the jurisdiction of its own CSS class which is set to button white.<\/p>\n\n\n\n
Now, let\u2019s say the developer wants to explain the notes. In such a case HTML layout object can be used:<\/p>\n\n\n\n
Layout(<\/em><\/p>\n\n\n\n Fieldset(<\/em><\/p>\n\n\n\n ‘Tell us your favorite stuff {{ username }}’,<\/em><\/p>\n\n\n\n ‘like_platform’,<\/em><\/p>\n\n\n\n ‘favorite_watch’,<\/em><\/p>\n\n\n\n ‘favorite_price’,<\/em><\/p>\n\n\n\n ‘favorite_restaurant’,<\/em><\/p>\n\n\n\n HTML(“””<\/em><\/p>\n\n\n\n <p>We use notes to become smarter get better, <strong>please help us {{ username }}<\/strong><\/p><\/em><\/p>\n\n\n\n “””),<\/em><\/p>\n\n\n\n ‘notes’<\/em><\/p>\n\n\n\n )<\/em><\/p>\n\n\n\n)<\/em><\/p>\n\n\n\nThe fieldset legend is \u201ccontext-conscious,\u201d and it can be written as if it were a piece of a template (where the form will be rendered to). The HTML object will tag a message before the notes are provided. It\u2019s also \u201ccontext-aware.\u201d Layout objects such as Fieldset, Div, MultiField, and ButtonHolder can contain other Layout objects within.<\/p>\n\n\n\n
Let\u2019s play a bit further. This time we\u2019ll do a different layout for the same form:<\/p>\n\n\n\n
Layout(<\/em><\/p>\n\n\n\n MultiField(<\/em><\/p>\n\n\n\n ‘Tell us your favorite stuff {{ username }}’,<\/em><\/p>\n\n\n\n Div(<\/em><\/p>\n\n\n\n ‘like_platform’,<\/em><\/p>\n\n\n\n ‘favorite_watch’,<\/em><\/p>\n\n\n\n css_id = ‘special-fields’<\/em><\/p>\n\n\n\n ),<\/em><\/p>\n\n\n\n ‘favorite_price’,<\/em><\/p>\n\n\n\n ‘favorite_restaurant’,<\/em><\/p>\n\n\n\n ‘notes’<\/em><\/p>\n\n\n\n )<\/em><\/p>\n\n\n\n)<\/em><\/p>\n\n\n\nThis time a MultiField has been used which is a layout object. As a rule of thumb, it can be utilized in the same places as Fieldset. The difference here is: all fields can be rendered wrapped in a div. If some potential errors happen in the form submission, then they are displayed in a list farther from the field.<\/p>\n\n\n\n
Welcome to the world of universal layout objects<\/strong><\/h2>\n\n\n\nThe layout objects are found in module crispy_forms.layout, but they are not specific to a template pack. Let\u2019s take them one by one and see their usage examples:<\/p>\n\n\n\n
- Div:<\/strong> It wraps fields in a <div><\/em>:<\/li><\/ul>\n\n\n\n
Div(‘form_field_1’, ‘form_field_2’, ‘form_field_3’, …)<\/em><\/p>\n\n\n\nDISCLAIMER:<\/strong> There is a possibility to set kwargs in all layout objects that will be utilized as HTML attributes. The developer should use css_class<\/em> as class<\/em> is a keyword in Python. For example:<\/p>\n\n\n\nDiv(‘form_field_1’, style=”background: white;”, title=”Explication title”, css_class=”bigdivs”)<\/em><\/p>\n\n\n\n- HTML:<\/strong> It\u2019s quite a powerful layout object. It should be used to render pure HTML code. In essence, it acts as a Django template. HTML has access to the overall context of the page where the form is being rendered.<\/li><\/ul>\n\n\n\n
- Field:<\/strong> A principle layout object. It can be used for setting attributes in a field or rendering a particular field with a custom template. That is how the necessity to override the field\u2019s widget can be avoided. That is the way to pass over a weird attrs<\/em>dictionary:<\/li><\/ul>\n\n\n\n
Field(‘password’, id=”password-field”, css_class=”passwordfields”, title=”Explanation”)<\/em><\/p>\n\n\n\nField(‘slider’, template=”custom-slider.html”)<\/em><\/p>\n\n\n\nThis layout object can be used for an easy Django\u2019s widgets extension.<\/p>\n\n\n\n
- Submit:<\/strong> Used to help to create submit button. There are two parameters. The first one is the name<\/em> attribute of this very button. The second one is the value<\/em> attribute:<\/li><\/ul>\n\n\n\n
Submit(‘search’, ‘SEARCH’)<\/em><\/p>\n\n\n\nSubmit(‘search’, ‘SEARCH’)<\/em><\/p>\n\n\n\nis rendering to:<\/p>\n\n\n\n
<input type=”submit” name=”search” value=”SEARCH” class=”submit submitButton” id=”submit-id-search” \/><\/em><\/p>\n\n\n\n- Hidden:<\/strong> was creating a hidden input:<\/li><\/ul>\n\n\n\n
Hidden(‘name’, ‘value’)<\/em><\/p>\n\n\n\n- Button:<\/strong> for creating a button:<\/li><\/ul>\n\n\n\n
Button(‘name’, ‘value’)<\/em><\/p>\n\n\n\n- Reset:<\/strong> was used to create a reset input:<\/li><\/ul>\n\n\n\n
reset = Reset(‘name’, ‘value’)<\/em><\/p>\n\n\n\n- Fieldset:<\/strong> It wraps fields in a <fieldset><\/em>. The first attribute is the command line for the fieldset legend. As indicated earlier, it acts as a Django template:<\/li><\/ul>\n\n\n\n
Fieldset(“Text for the legend {{ username }}”,<\/em><\/p>\n\n\n\n ‘form_field_1’,<\/em><\/p>\n\n\n\n ‘form_field_2’<\/em><\/p>\n\n\n\n)<\/em><\/p>\n\n\n\nWe\u2019ve just scratched the surface of django-crispy-forms capacities. Of course, more things can be done with their help. For example, django views can switch on “helper.” It can also be overwritten.<\/p>\n\n\n\n
Django is also helpful if you want to submit class for button creation: <button type=”submit” class=”btn btn-primary”>Sign in<\/button>. Moreover, developers can create their own templates for specific fields within a form.\\<\/p>\n\n\n\n
Final thoughts<\/strong><\/h2>\n\n\n\n<\/figure>\n\n\n\nIf you\u2019re curious to delve deeper into the complexities of django crispy, feel free to digest its official documentation<\/a>. Additionally, you can watch this video<\/a> for a better grasp of this topic. <\/p>\n\n\n\n
<\/figure>\n\n\n\nDjango DRY (fun word for crispy) forms can help to build reusable programmatic layouts. Here the developer has full control of the rendered HTML without the necessity to write HTML in templates. All this can happen without breaking the standard way of doing things in Django, so it plays nice with any other form application.<\/p>\n\n\n\n
Django-crispy-forms is built to support Python 2.7\/Python 3.3+ and Django 1.8\/Django 1.10+<\/p>\n\n\n\n
The application basically gives such options:<\/p>\n\n\n\n
- A filter called |crispy | that will render neat div based forms. You can imagine it as the built-in methods: as_table, as_ul and as_p. The output cannot be tuned up, but it can be easily launched to life.<\/li>
- A tag named {% crispy %} will render a form which is tailored to developer\u2019s configuration and particular layout setup. This gives computer gurus lots of \u201csuper-powers\u201d without much hassle, helping them to save loads of time.<\/li><\/ul>\n\n\n\n
The boons of Django-crispy-forms<\/strong><\/h2>\n\n\n\n
Django-crispy-forms helps developers bring some style to input forms\u2019 properties (i.e., method, CSS classes or \u201csend button\u201d) on the backend. The good news: these forms don\u2019t have to be re-written in the template. In this way, the plain Django forms become more readable. It is also easier to render them. The programmer can even restrict them to one life of code.<\/p>\n\n\n\n
More significantly, Django-crispy-forms improves the look of the forms. They add CSS classes to all the buttons, individual fields so that an entire form looks gorgeous. <\/p>\n\n\n\n
Installing Django-crispy-forms is a piece of cake<\/strong><\/h2>\n\n\n\n
Developers need to follow a standard procedure to install django-crispy-forms. They need a pack manager \u201cpip\u201d or \u201ceasy_install.\u201d Then, they add the installed App \u2018cryspy_forms\u201d to the INSTALLED_APPS list.<\/p>\n\n\n\n
If the Bootstrap<\/a>(or any other CSS framework as Foundations)<\/a> is used, then it needs to be imported to the project. That\u2019s all to it. For more details and advanced options, check out the official django-crispy-forms documentation<\/a>.<\/p>\n\n\n\n
How Django crispy forms layout saves the day<\/strong><\/h2>\n\n\n\n
<\/figure>\n\n\n\nDjango-crispy-forms can define another strong class: Layout. This class is an excellent help for rendering the fields of a form. It opens access so that fields can be ordered and wrapped in structures. Then HTML is added, and various classes are set, etc. All of this is an excellent asset at hand for a busy programmer. <\/p>\n\n\n\n
Now the developer doesn\u2019t have to write a custom form template \u2014 no need for programmatic layouts any longer. The programmer can attach the layout to a helper. Layouts are optionally used, but the bottom line here is that they are the best stuff offered by django-crispy-forms. So they shouldn\u2019t be overlooked. <\/p>\n\n\n\n
Layout objects are the building bricks for Layout. They are the DNA of the form building process.<\/p>\n\n\n\n
Feel free to dig deeper into it by reading about Universal layout objects<\/a>. It\u2019s important to remember that a different template is generated by various components which have a different purpose.<\/p>\n\n\n\n
For instance, let\u2019s imagine a developer wants to have a couple of different layouts for their form. How would this form class look like in real life? NB: Some layout objects are tied to a particular template.<\/p>\n\n\n\n
Imagine ButtonHolder is for uni_formtemplate_pack, while FormActions is for bootstrap template pack. Here are some django crispy forms layout examples: <\/p>\n\n\n\n
from crispy_forms.helper import FormHelper<\/em><\/p>\n\n\n\n
from crispy_forms.layout import Layout, Fieldset, ButtonHolder, Submit<\/em><\/p>\n\n\n\n
class ExampleForm(forms.Form):<\/em><\/p>\n\n\n\n
[…]<\/em><\/p>\n\n\n\n
def __init__(self, *args, **kwargs):<\/em><\/p>\n\n\n\n
self.helper = FormHelper()<\/em><\/p>\n\n\n\n
self.helper.layout = Layout(<\/em><\/p>\n\n\n\n
Fieldset(<\/em><\/p>\n\n\n\n
‘first arg is the legend of the fieldset’,<\/em><\/p>\n\n\n\n
‘like_platform’,<\/em><\/p>\n\n\n\n
‘favorite_watch’,<\/em><\/p>\n\n\n\n
‘favorite_price’,<\/em><\/p>\n\n\n\n
‘favorite_restaurant’,<\/em><\/p>\n\n\n\n
‘notes’<\/em><\/p>\n\n\n\n
),<\/em><\/p>\n\n\n\n
ButtonHolder(<\/em><\/p>\n\n\n\n
Submit(‘submit’, ‘Submit’, css_class=’button white’)<\/em><\/p>\n\n\n\n
)<\/em><\/p>\n\n\n\n
)<\/em><\/p>\n\n\n\n
super(ExampleForm, self).__init__(*args, **kwargs)<\/em><\/p>\n\n\n\n
While rendering the form, the developers use now:<\/p>\n\n\n\n
{% load crispy_forms_tags %}<\/em><\/p>\n\n\n\n
{% crispy example_form %}<\/em><\/p>\n\n\n\n
What\u2019s next? The fields are included in the fieldset, whose legend will be switched to \u2018first arg is the legend of the fieldset.\u2019 The order of the fields\u2019 will be in this fashion: like_platform, favorite_watch, favorite_price, favorite_restaurant, and notes.<\/p>\n\n\n\n
Then the submit button can be wrapped in a <div class=”buttonHolder”> which Django uni-form turns from ashes to beauty. That button is under the jurisdiction of its own CSS class which is set to button white.<\/p>\n\n\n\n
Now, let\u2019s say the developer wants to explain the notes. In such a case HTML layout object can be used:<\/p>\n\n\n\n
Layout(<\/em><\/p>\n\n\n\n
Fieldset(<\/em><\/p>\n\n\n\n
‘Tell us your favorite stuff {{ username }}’,<\/em><\/p>\n\n\n\n
‘like_platform’,<\/em><\/p>\n\n\n\n
‘favorite_watch’,<\/em><\/p>\n\n\n\n
‘favorite_price’,<\/em><\/p>\n\n\n\n
‘favorite_restaurant’,<\/em><\/p>\n\n\n\n
HTML(“””<\/em><\/p>\n\n\n\n
<p>We use notes to become smarter get better, <strong>please help us {{ username }}<\/strong><\/p><\/em><\/p>\n\n\n\n
“””),<\/em><\/p>\n\n\n\n
‘notes’<\/em><\/p>\n\n\n\n
)<\/em><\/p>\n\n\n\n
)<\/em><\/p>\n\n\n\n
The fieldset legend is \u201ccontext-conscious,\u201d and it can be written as if it were a piece of a template (where the form will be rendered to). The HTML object will tag a message before the notes are provided. It\u2019s also \u201ccontext-aware.\u201d Layout objects such as Fieldset, Div, MultiField, and ButtonHolder can contain other Layout objects within.<\/p>\n\n\n\n
Let\u2019s play a bit further. This time we\u2019ll do a different layout for the same form:<\/p>\n\n\n\n
Layout(<\/em><\/p>\n\n\n\n
MultiField(<\/em><\/p>\n\n\n\n
‘Tell us your favorite stuff {{ username }}’,<\/em><\/p>\n\n\n\n
Div(<\/em><\/p>\n\n\n\n
‘like_platform’,<\/em><\/p>\n\n\n\n
‘favorite_watch’,<\/em><\/p>\n\n\n\n
css_id = ‘special-fields’<\/em><\/p>\n\n\n\n
),<\/em><\/p>\n\n\n\n
‘favorite_price’,<\/em><\/p>\n\n\n\n
‘favorite_restaurant’,<\/em><\/p>\n\n\n\n
‘notes’<\/em><\/p>\n\n\n\n
)<\/em><\/p>\n\n\n\n
)<\/em><\/p>\n\n\n\n
This time a MultiField has been used which is a layout object. As a rule of thumb, it can be utilized in the same places as Fieldset. The difference here is: all fields can be rendered wrapped in a div. If some potential errors happen in the form submission, then they are displayed in a list farther from the field.<\/p>\n\n\n\n
Welcome to the world of universal layout objects<\/strong><\/h2>\n\n\n\n
The layout objects are found in module crispy_forms.layout, but they are not specific to a template pack. Let\u2019s take them one by one and see their usage examples:<\/p>\n\n\n\n
- Div:<\/strong> It wraps fields in a <div><\/em>:<\/li><\/ul>\n\n\n\n
Div(‘form_field_1’, ‘form_field_2’, ‘form_field_3’, …)<\/em><\/p>\n\n\n\n
DISCLAIMER:<\/strong> There is a possibility to set kwargs in all layout objects that will be utilized as HTML attributes. The developer should use css_class<\/em> as class<\/em> is a keyword in Python. For example:<\/p>\n\n\n\n
Div(‘form_field_1’, style=”background: white;”, title=”Explication title”, css_class=”bigdivs”)<\/em><\/p>\n\n\n\n
- HTML:<\/strong> It\u2019s quite a powerful layout object. It should be used to render pure HTML code. In essence, it acts as a Django template. HTML has access to the overall context of the page where the form is being rendered.<\/li><\/ul>\n\n\n\n
- Field:<\/strong> A principle layout object. It can be used for setting attributes in a field or rendering a particular field with a custom template. That is how the necessity to override the field\u2019s widget can be avoided. That is the way to pass over a weird attrs<\/em>dictionary:<\/li><\/ul>\n\n\n\n
Field(‘password’, id=”password-field”, css_class=”passwordfields”, title=”Explanation”)<\/em><\/p>\n\n\n\n
Field(‘slider’, template=”custom-slider.html”)<\/em><\/p>\n\n\n\n
This layout object can be used for an easy Django\u2019s widgets extension.<\/p>\n\n\n\n
- Submit:<\/strong> Used to help to create submit button. There are two parameters. The first one is the name<\/em> attribute of this very button. The second one is the value<\/em> attribute:<\/li><\/ul>\n\n\n\n
Submit(‘search’, ‘SEARCH’)<\/em><\/p>\n\n\n\n
Submit(‘search’, ‘SEARCH’)<\/em><\/p>\n\n\n\n
is rendering to:<\/p>\n\n\n\n
<input type=”submit” name=”search” value=”SEARCH” class=”submit submitButton” id=”submit-id-search” \/><\/em><\/p>\n\n\n\n
- Hidden:<\/strong> was creating a hidden input:<\/li><\/ul>\n\n\n\n
Hidden(‘name’, ‘value’)<\/em><\/p>\n\n\n\n
- Button:<\/strong> for creating a button:<\/li><\/ul>\n\n\n\n
Button(‘name’, ‘value’)<\/em><\/p>\n\n\n\n
- Reset:<\/strong> was used to create a reset input:<\/li><\/ul>\n\n\n\n
reset = Reset(‘name’, ‘value’)<\/em><\/p>\n\n\n\n
- Fieldset:<\/strong> It wraps fields in a <fieldset><\/em>. The first attribute is the command line for the fieldset legend. As indicated earlier, it acts as a Django template:<\/li><\/ul>\n\n\n\n
Fieldset(“Text for the legend {{ username }}”,<\/em><\/p>\n\n\n\n
‘form_field_1’,<\/em><\/p>\n\n\n\n
‘form_field_2’<\/em><\/p>\n\n\n\n
)<\/em><\/p>\n\n\n\n
We\u2019ve just scratched the surface of django-crispy-forms capacities. Of course, more things can be done with their help. For example, django views can switch on “helper.” It can also be overwritten.<\/p>\n\n\n\n
Django is also helpful if you want to submit class for button creation: <button type=”submit” class=”btn btn-primary”>Sign in<\/button>. Moreover, developers can create their own templates for specific fields within a form.\\<\/p>\n\n\n\n
Final thoughts<\/strong><\/h2>\n\n\n\n
<\/figure>\n\n\n\nIf you\u2019re curious to delve deeper into the complexities of django crispy, feel free to digest its official documentation<\/a>. Additionally, you can watch this video<\/a> for a better grasp of this topic. <\/p>\n\n\n\n
- Fieldset:<\/strong> It wraps fields in a <fieldset><\/em>. The first attribute is the command line for the fieldset legend. As indicated earlier, it acts as a Django template:<\/li><\/ul>\n\n\n\n
- Reset:<\/strong> was used to create a reset input:<\/li><\/ul>\n\n\n\n
- Button:<\/strong> for creating a button:<\/li><\/ul>\n\n\n\n
- Hidden:<\/strong> was creating a hidden input:<\/li><\/ul>\n\n\n\n
- Submit:<\/strong> Used to help to create submit button. There are two parameters. The first one is the name<\/em> attribute of this very button. The second one is the value<\/em> attribute:<\/li><\/ul>\n\n\n\n
- Field:<\/strong> A principle layout object. It can be used for setting attributes in a field or rendering a particular field with a custom template. That is how the necessity to override the field\u2019s widget can be avoided. That is the way to pass over a weird attrs<\/em>dictionary:<\/li><\/ul>\n\n\n\n
- HTML:<\/strong> It\u2019s quite a powerful layout object. It should be used to render pure HTML code. In essence, it acts as a Django template. HTML has access to the overall context of the page where the form is being rendered.<\/li><\/ul>\n\n\n\n
- Div:<\/strong> It wraps fields in a <div><\/em>:<\/li><\/ul>\n\n\n\n