I read through Flask-WTF extremely simplified wiki, and couldn't understand much about what I can do with it. I am under the impression that the <form>
section of the html now can only look like
<form method="post">
{{ form.hidden_tag() }}
{{ form.name }}
<input type="submit">
</form>
But I really want to style my using materialized such as:
<div class="row">
<div class="input-field col s6">
<i class="material-icons prefix">account_circle</i>
<input value="FN" id="first_name" type="text" class="validate">
<label class="active" for="first_name">First Name</label>
</div>
<div class="input-field col s6">
<input value="LN" id="last_name" type="text" class="validate">
<label class="active" for="last_name">Last Name</label>
</div>
</div>
Where can I fit {{ form.first_name }}
and {{ form.last_name }}
into?
EDIT: Let me elaborate on my answer a bit more:
For example, I want something like Materialized datepicker
(a good pop up calendar that lets user to choose the date), this should be in the <input class='datepicker' length="50">
, but now that I am replacing the whole <input>
line with {{ form.date }}
... I lost that privilege to edit the class and what not.
WTForms are really useful it does a lot of heavy lifting for you when it comes to data validation on top of the CSRF protection . Another useful thing is the use combined with Jinja2 where you need to write less code to render the form. Note: Jinja2 is one of the most used template engines for Python.
WTForms fields can be called with attributes that will be set on the input they render. Pass the attributes you need for styling, JavaScript functionality, etc. to the fields, rather than just referencing the fields. The labels behave the same way, and can be accessed with field.label
.
for
, value
, type
, id
, and name
do not need to be passed, as they are handled automatically. There are some rules for handling special cases of attributes. If an attribute name is a Python keyword such as class
, append an underscore: class_
. Dashes are not valid Python names, so underscores between words are converted to dashes; data_toggle
becomes data-toggle
.
{{ form.first_name(class_='validate') }}
{{ form.first_name.label(class_='active') }}
{{ form.begins(class_='datepicker', length=50) }}
Note that neither of the linked methods need to be called directly, those docs just describe the behavior when calling the fields.
In WTForms 2.1 I use extra_classes
, like the line below:
1. The first way
{{ f.render_form_field(form.first_name, extra_classes='ourClasses') }}
or maybe in your case just like this:
{{ form.first_name, extra_classes='ourClasses' }}
We can also use the render_kw
attribute on our form field like the second way below:
2. The second way
style={'class': 'ourClasses', 'style': 'width:50%; other_css_style;'}
first_name = StringField('First name',
validators=[InputRequired(),Length(1, 64)],
render_kw=style)
But I would prefer to use the first way.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With