Form Helpers
Opal comes with a selection of templatetags that can help you with the repetitive task of generating Bootstrap and Opal compatible markup for your forms.
{% checkbox ... %}
Generates a checkbox
Keywords:
fielda string of the models api name '.' field which infers attributes for the model, for more information see Inference from subrecord fieldslabelThe Label with which to describe this fieldmodelThe model which we are editing (This is a string that references an in-scope Angular variable)disabledIf this exists, we use this as the expression for the ng-disabled directiveelement_nameIf this exists this is an Angular expression that is set to the 'name' attribute of the html element
{% datepicker ... %}
Generates a datepicker
Keywords:
fielda string of the models api name '.' field which infers attributes for the model, for more information see Inference from subrecord fieldslabelThe Label with which to describe this fieldmodelThe model which we are editing (This is a string that references an in-scope Angular variable)showA string that contains an Angular expression for the ng-show directivehideA string that contains an Angular expression for the ng-hide directiverequiredLabel to show when we're requiredmindateAngular Javascript expression to return the minimum possible dateelement_nameIf this exists this is an Angular expression that is set to the 'name' attribute of the html element
{% datetimepicker ... %}
Generates a date time fields, a date field on one line and a time field on another
Keywords:
fielda string of the models api name '.' field which infers attributes for the model, for more information see Inference from subrecord fieldsdate_labelThe Label with which to describe the date field (defaults to 'Date')time_labelThe Label with which to describe the date field (defaults to 'Time')modelThe model which we are editing (This is a string that references an in-scope Angular variable)changean Angular directive that fires on changeelement_nameIf this exists this is an Angular expression that is set to the 'name' attribute of the html datetime picker element
{% input ... %}
The input template tag generates you a form input that will play nicely with Opal's styling.
Keywords:
fielda string of the models api name '.' field which infers attributes for the model, for more information see Inference from subrecord fieldslabelThe Label with which to describe this fieldmodelThe model which we are editing (This is a string that references an in-scope Angular variable)showA string that contains an Angular expression for the ng-show directivehideA string that contains an Angular expression for the ng-hide directivelookuplistan Angular expression that evaluates to an array containing the lookuplist valuesrequiredLabel to show when we're requiredenterexpression to evaluate if the user presses return when in this inputmaxlengthmaximum number of characters for this input. Will render the form invalid and display help text if exceeded.element_nameIf this exists this is an Angular expression that is set to the 'name' attribute of the html element
Inputs with units
We also often want to display the unit of a particular field to help our users - consistent styling for this is available by using the unit argument e.g.
{% input label="Weight" model="editing.weight" unit="kg" %}
{% radio ... %}
Generates an inline radio input
Keywords:
fielda string of the models api name '.' field from this it calculates the label, model and will infer the lookuplist if required. For example {% radio field="DogOwner.dog" %}labelThe Label with which to describe this inputmodelThe model which we are editing (This is a string that references an in-scope Angular variable)showA string that contains an Angular expression for the ng-show directivehideA string that contains an Angular expression for the ng-hide directivelookuplistan Angular expression that evaluates to an array containing the radio valueselement_nameIf this exists this is an Angular expression that is set to the 'name' attribute of the html element
{% select ... %}
Generates an inline select input
Keywords:
fielda string of the models api name '.' field from this it calculates the label, model and will infer the lookuplist if required. For example {% select field="DogOwner.dog" %}labelThe Label with which to describe this inputmodelThe model which we are editing (This is a string that references an in-scope Angular variable)showA string that contains an Angular expression for the ng-show directivehideA string that contains an Angular expression for the ng-hide directivelookuplistan Angular expression that evaluates to an array containing the radio valuesotherA boolean parameter that if true, provides a free text option when 'Other' is selectedhelpa template to use as the contents of a help popoverstatican Angular expression that will swap the display to be a static input if it evaluates totrueelement_nameIf this exists this is an Angular expression that is set to the 'name' attribute of the html element*
{% textarea ... %}
Generates an inline textarea input
Keywords:
fielda string of the models api name '.' field from this it calculates the label, model and will infer the lookuplist if required. For example {% textarea field="DogOwner.dog" %}labelThe Label with which to describe this inputmodelThe model which we are editing (This is a string that references an in-scope Angular variable)showA string that contains an Angular expression for the ng-show directivehideA string that contains an Angular expression for the ng-hide directiveelement_nameIf this exists this is an Angular expression that is set to the 'name' attribute of the html element
Inference from subrecord fields
A very common pattern is to render form fields that relate to fields of Subrecords. Template tags will use this to infer useful information. The display name will be set to the verbose_name and the the ng-model will be inferred.
If its required, it will set as a required field. If its a CharField with a max length it will set a validation rule accordingly.
If the field is a free text or foreign key we will infer the lookup list.
Alternatively if the field has choices attatched to it we will infer the choices into the field.
{% input field="Allergies.drug" %}
Note unlike the traditional choices implementation only the last value of the choices is used and saved to the database
Colours = (
('P', 'Purple'),
('R', 'Red'),
)
What is displayed to the user and saved to the database is 'Purple' or 'Red' respectively.
All inferences can be overridden by declarations in the template tag. For Example
{% input field="Allergies.drug" label="Something else" %}
Will render the input with a different label.
{% static ... %}
Generates a bootstrap Static div (for displaying data from fields as uneditable but formatted nicely with appropriate styles).
Takes one positional argument, a string representing the subrecord field path.
{% static "Demographics.name" %}
<!-- Renders as -->
<div class="form-group">
<label class="control-label col-sm-3">
Name
</label>
<p class="form-control-static col-sm-8">
[[ editing.demographics.name ]]
</p>
</div>
{% icon "icon-name" %}
Renders a Bootstrap style Icon tag.
If the icon starts with fa or glyphicon then we will insert the preceding fa.
{% icon "fa-user-md" %}
<i class="fa fa-user-md"></i>
{% icon "cusom-icon"}
<i class="custom-icon"></i>