Bootstrap 4 forms for Nette framework
MIT License
Please use English in potential issues, let's keep it clean, shall we?
This is a library that lets you use Bootstrap 4 forms in Nette framework.
Rather than being just a renderer, this introduces a custom set of controls (which covers all default controls) and a renderer.
Note that this is an alpha, so it may be buggy. That is where you can help by reporting issues.
The best way is via composer:
composer require czubehead/bootstrap-4-forms
Note that if you simply clone the main branch from this repo, it is not guaranteed to work, use releases instead
Nette\Application\UI\Form
, not Nette\Forms\Form
, so you need theThis package is compatible with any version version of Bootstrap 4 (last tested on v4.0.0-beta.2)
Probably the main class you will be using is Czubehead\BootstrapForms\BootstrapForm
.
It has all the features of this library pre-configured and extends
Nette\Application\UI\Form
functionality by:
Czubehead\BootstrapForms\BootstrapRenderer
or its children (which is default)ajax
class upon rendering) via ajax
(bool) propertyrenderMode
)$form = new BootstrapForm;
$form->renderMode = RenderMode::Vertical;
It will behave pretty much the same as the default Nette form, with the exception of not grouping buttons. That feature would only add unnecessary and deceiving overhead to this library, use grid instead, it will give you much finer control
Enums\RenderMode::VerticalMode
) all controls are below their labelsEnums\RenderMode::SideBySideMode
) controls have their labelsBootstrapRenderer::setColumns($label, $input)
.Enums\RenderMode::Inline
all controls and labels will be in oneEach default control has has been extended bootstrap-enabled controls and
will render itself correctly even without the renderer. You can distinguish
them easily - they all have Input
suffix.
TextInput can have placeholder set ($input->setPlaceholder($val)
). All text-based
inputs (except for TextArea) inherit from this control.
Its format can be set ($input->setFormat($str)
), the default is d.m.yyyy h:mm
(though you must specify it in standard PHP format!).
You may use DateTimeFormats class constants as a list of pretty much all formats:
DateTimeFormat::D_DMY_DOTS_NO_LEAD . ' ' . DateTimeFormat::T_24_NO_LEAD
is the default format for DateTime. See its PhpDoc for further explanation.
Nothing out of ordinary, but it Needs <html lang="xx">
attribute to work.
Has property buttonCaption
, which sets the text on the button on the left.
The right button is set by Bootstrap CSS, which depends <html lang="xx">
.
These can accept nested arrays of options.
[
'sub' => [
1 => 'opt1',
2 => 'opt2'
],
3 => 'opt3',
]
will generate
<optgroup label="sub">
<option value="1">opt1</option>
<option value="2">opt2</option>
</optgroup>
<option value="3">opt3</option>
The renderer is enhanced by the following API:
property | type | meaning |
---|---|---|
mode | int constant | see render mode above in form section |
gridBreakPoint | string / null | Bootstrap grid breakpoint for side-by-side view. Default is 'sm' |
groupHidden | bool | if true, hidden fields will be grouped at the end. If false, hidden fields are placed where they were added. Default is true. |
The library provides a way to programmatically place controls into Bootstrap grid and thus greatly reduces the need for manual rendering.
Simply add a new row like this:
$row = $form->addRow();
$row->addCell(6)
->addText('firstname', 'First name');
$row->addCell(6)
->addText('surname', 'Surname');
And firstname and surname will be beside each other.
getElementPrototype()
on row or cell, you can influence the elements of row / cell\Czubehead\BootstrapForms\Grid\BootstrapCell::COLUMNS_NONE
\Czubehead\BootstrapForms\Grid\BootstrapCell::COLUMNS_AUTO
Why do we use manual rendering? Mostly to just rearrange the inputs, we rarely create a completely different feel. But there is a hefty price for using manual rendering - we have to do almost everything ourselves, even the things the renderer could do for us. Only if there were a way to let the renderer do most of the work...
Assisted manual rendering will render label-input pairs for you using a filter.
This means that it will take care of wrapping things into div.form-group
and validation
messages - the most mundane thing to implement in a template.
First of all, you must implement this yourself, this won't work out of the box! The implementation is quite dirty, but I think the benefits outweigh this cost.
It works like this:
add a new filter to your latte engine, for example:
$this->template->addFilter('formPair', function ($control) {
/** @var BootstrapRenderer $renderer */
$renderer = $control->form->renderer;
$renderer->attachForm($control->form);
return $renderer->renderPair($control);
});
{$form['firstname']|formPair|noescape}
That will result in
<div class="form-group row">
<label for="frm-form-firstname" class="col-sm-3">First name</label>
<div class="col-sm-9">
<input type="text" name="firstname" id="frm-form-firstname" class="form-control">
</div>
</div>