NAME
Mojolicious::Plugin::BootstrapHelpers - Type less bootstrap
VERSION
Version 0.0206, released 2019-06-24.
SYNOPSIS
# Mojolicious
$self->plugin('BootstrapHelpers');
# ::Lite
plugin 'BootstrapHelpers';
# Meanwhile, somewhere in a template...
%= formgroup 'Email', text_field => ['email'], large, cols => { small => [3, 9] }
# ...that renders into
<div class="form-group form-group-lg">
<label class="control-label col-sm-3" for="email">Email</label>
<div class="col-sm-9">
<input class="form-control" id="email" name="email" type="text">
</div>
</div>
STATUS
Relatively stable. This distribution will not be updated to support Bootstrap 4. There might be a separate distribution for that.
All examples are tested.
DESCRIPTION
Mojolicious::Plugin::BootstrapHelpers is a convenience plugin that reduces some bootstrap complexity by introducing several tag helpers specifically for Bootstrap 3.
The goal is not to have tag helpers for everything, but for common use cases.
All examples below (and more, see tests) is expected to work.
How to use Bootstrap
If you don't know what Bootstrap is, see http://www.getbootstrap.com/ for possible usages.
You might want to use Mojolicious::Plugin::Bootstrap3 in your templates.
To get going quickly by using the official CDN you can use the following helpers:
# CSS
%= bootstrap
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.4.1/css/bootstrap.min.css">
# or (if you want to use the theme)
%= bootstrap 'theme'
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.4.1/css/bootstrap.min.css">
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.4.1/css/bootstrap-theme.min.css">
# And the javascript
%= bootstrap 'js'
<script src="//maxcdn.bootstrapcdn.com/bootstrap/3.4.1/js/bootstrap.min.js"></script>
# Or just:
%= bootstrap 'all'
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.4.1/css/bootstrap.min.css">
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.4.1/css/bootstrap-theme.min.css">
<script src="//maxcdn.bootstrapcdn.com/bootstrap/3.4.1/js/bootstrap.min.js"></script>
It is also possible to automatically include jQuery (2.*)
%= bootstrap 'jsq'
<script src="//code.jquery.com/jquery-2.2.4.min.js"></script>
<script src="//maxcdn.bootstrapcdn.com/bootstrap/3.4.1/js/bootstrap.min.js"></script>
%= bootstrap 'allq'
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.4.1/css/bootstrap.min.css">
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.4.1/css/bootstrap-theme.min.css">
<script src="//code.jquery.com/jquery-2.2.4.min.js"></script>
<script src="//maxcdn.bootstrapcdn.com/bootstrap/3.4.1/js/bootstrap.min.js"></script>
Shortcuts
There are several shortcuts for applying context and size classes that automatically expands to the correct class depending on which tag it is applied to. For instance, if you apply the info
shortcut to a panel, it becomes panel-info
, but when applied to a button it becomes btn-info
.
You can use them in two different ways, but internally they are the same. These to lines are exactly identical:
# 'standalone shortcut'
%= button 'Push me', primary
# 'longform shortcut'
%= button 'Push me', __primary => 1
For sizes, you can only use the longform (xsmall
, small
, medium
and large
). They are shortened to the Bootstrap type classes.
The following shortcuts are available:
xsmall default striped caret right
small primary bordered
medium success hover
large info condensed
warning responsive
danger
Add two leading underscores if you don't want to use the standalone form.
See below for usage. Important: You can't follow a standalone shortcut with a fat comma (=>
). The fat comma auto-quotes the string on the left, and then it breaks.
If a shortcut you try to apply isn't available in that context, it is silently not applied.
The standalone form is recommended for readability, but it does setup several helpers in your templates. You can turn off this style, see init_shortcuts.
Syntax convention
In the syntax sections below the following conventions are used:
name A specific string
$name Any string
%name One or more key-value pairs, written as:
key => 'value', key2 => 'value2'
or, if you use standalone shortcuts:
primary, large
$key => [...] Both of these are array references where the ordering of strings
key => [...] are significant, for example:
key => [ $thing, $thing2, %hash ]
$key => {...} Both of these are hash references where the ordering of pairs are
key => {...} are insignificant, for example:
key => { key2 => $value, key3 => 'othervalue' }
(...) Anything between parenthesis is optional. The parenthesis is not part of the
actual syntax
|...| Two pipes is a reference to another specification. For instance, button toolbars contain
button groups that contain buttons. Using this syntax makes the important parts clearer.
The pipes are not part of the actual syntax.
Ordering between two hashes that follows each other is also not significant.
About %has
The following applies to all %has
hashes below:
They refer to any html attributes and/or shortcuts to apply to the current element.
When helpers are nested, all occurrencies are change to tag-specific names, such as
%panel_has
.This hash is always optional. It is not marked so in the definitions below in order to reduce clutter.
Depending on context either the leading or following comma is optional together with the hash. It is usually obvious.
Sometimes on nested helpers (such as tables in panels just below),
%has
is the only thing that can be applied to the other element. In this casepanel => { %panel_has }
. It follows from above that in those cases this entire expression is also optional. Such cases are also not marked as optional in syntax definitions and are not mentioned in syntax description, unless they need further comment.
From this definition:
%= table ($title,) %table_has, panel => { %panel_has }, begin
$body
% end
Both of these are legal:
# since both panel => { %panel_has } and %table_has are hashes, their ordering is not significant.
%= table 'Heading Table', panel => { success }, condensed, id => 'the-table', begin
<tr><td>A Table Cell</td></tr>
% end
%= table begin
<tr><td>A Table Cell</td></tr>
% end
References
All other |references|
are also helpers, so |link|
and |item|
needs special mention.
|link|
|link|
creates an <a>
tag.
|link|
Is exactly the same as
$link_text, [ $url ], %link_has
$link_text
Mandatory. The text on the link.
$url
Mandatory. It sets the href
on the link. url_for is used to create the link.
%link_has
Which shortcuts are available varies depending on context.
|item|
|item|
is used in the various submenus/dropdowns. One |item|
creates one <li>
tag.
|item|
Is exactly the same as
[ |link| ]
# or
$header_text
# or
[]
So, a submenu item can be one of three things:
- 1. A link, in which case you create a
|link|
in an array reference. - 2. A
.dropdown-header
, in which case you give it a'string'
which then is turned into the text of the header. - 3. A
.divider
, in which case you give it an empty array reference.
See "Dropdowns", "Button groups" and "Navbars" for examples.
EXAMPLES
All examples below, and more, are included in html files in /examples
. They are also available on github:
HELPERS
Badges
Syntax
%= badge $text, %has
$text
Mandatory. If it is undef
no output is produced.
Available shortcuts
right
applies .pull-right
.
Examples
A basic badge:<%= badge '3' %>
<span class="badge">3</span></a>
A right aligned badge with a data attribute:
<%= badge '4', data => { custom => 'yes' }, right %>
<span class="badge pull-right" data-custom="yes">4</span>
Buttons
Syntax
%= button $button_text(, [$url]), %has
%= submit_button $text, %has
$button_text
Mandatory. The text on the button.
[$url]
Optional array reference. It is handed off to url_for, so with it this is basically link_to with Bootstrap classes.
Not available for submit_button
.
Available shortcuts
default
primary
success
info
warning
danger
link
applies the various .btn-*
classes.
large
small
xsmall
applies .btn-lg
.btn-sm
.btn-xs
respectively.
active
block
applies the .active
and .block
classes.
disabled
applies the .disabled
class if the generated element is an <a>
. On a <button>
it applies the disabled="disabled"
attribute.
Examples
An ordinary button, with applied shortcuts:%= button 'The example 5' => large, warning
<button class="btn btn-lg btn-warning" type="button">The example 5</button>
With a url the button turns into a link:
%= button 'The example 1' => ['http://www.example.com/'], small
<a class="btn btn-default btn-sm" href="http://www.example.com/">The example 1</a>
A submit button for use in forms. It overrides the build-in submit_button helper:
%= submit_button 'Save 2', primary
<button class="btn btn-primary" type="submit">Save 2</button>
%= button 'Loop', active
<button class="active btn btn-default" type="button">Loop</button>
%= button 'Loop', block
<button class="block btn btn-default" type="button">Loop</button>
Button groups
Syntax
There are two different syntaxes. One for single-button groups and one for multi-button groups. The difference is that single-button groups can't change anything concerning the buttongroup (e.g. it can't be justified
). If you need to do that there is nothing wrong with having a multi-button group with just one button.
# multi button
<%= buttongroup %has,
buttons => [
[ |button|,
(items => [ |item| ])
]
]
%>
# single button
<%= buttongroup [ |button|,
(items => [ |item| ])
]
%>
buttons => []
The single-button style is a shortcut for the buttons
array reference. It takes ordinary buttons, with two differences: The items
array reference, and it is unnecessary to give a button with items
a url.
items => [...]
Giving a button an items
array reference consisting of one or many |item|
creates a dropdown like submenu. Read more under "item".
Examples
A basic button group:<%= buttongroup
buttons => [
['Button 1'],
['Button 2'],
['Button 3'],
]
%>
<div class="btn-group">
<button class="btn btn-default" type="button">Button 1</button>
<button class="btn btn-default" type="button">Button 2</button>
<button class="btn btn-default" type="button">Button 3</button>
</div>
Nested button group. Note that the small
shortcut is only necessary once. The same classes are automatically applied to the nested .btn-group
:
<%= buttongroup small,
buttons => [
['Button 1'],
['Dropdown 1', caret, items => [
['Item 1', ['item1'] ],
['Item 2', ['item2'] ],
[],
['Item 3', ['item3'] ],
] ],
['Button 2'],
['Button 3'],
],
%>
<div class="btn-group btn-group-sm">
<button class="btn btn-default" type="button">Button 1</button>
<div class="btn-group btn-group-sm">
<button class="btn btn-default dropdown-toggle" type="button" data-toggle="dropdown">Dropdown 1 <span class="caret"></span>
</button>
<ul class="dropdown-menu">
<li><a class="menuitem" href="item1" tabindex="-1">Item 1</a></li>
<li><a class="menuitem" href="item2" tabindex="-1">Item 2</a></li>
<li class="divider"></li>
<li><a class="menuitem" href="item3" tabindex="-1">Item 3</a></li>
</ul>
</div>
<button class="btn btn-default" type="button">Button 2</button>
<button class="btn btn-default" type="button">Button 3</button>
</div>
Nested button group, with the vertical
shortcut:
<%= buttongroup vertical,
buttons => [
['Button 1'],
['Dropdown 1', caret, items => [
['Item 1', ['item1'] ],
['Item 2', ['item2'] ],
[],
['Item 3', ['item3'] ],
] ],
['Button 2'],
['Button 3'],
],
%>
<div class="btn-group-vertical">
<button class="btn btn-default" type="button">Button 1</button>
<div class="btn-group">
<button class="btn btn-default dropdown-toggle" type="button" data-toggle="dropdown">Dropdown 1 <span class="caret"></span>
</button>
<ul class="dropdown-menu">
<li><a class="menuitem" href="item1" tabindex="-1">Item 1</a></li>
<li><a class="menuitem" href="item2" tabindex="-1">Item 2</a></li>
<li class="divider"></li>
<li><a class="menuitem" href="item3" tabindex="-1">Item 3</a></li>
</ul>
</div>
<button class="btn btn-default" type="button">Button 2</button>
<button class="btn btn-default" type="button">Button 3</button>
</div>
Mix links and dropup
menus in justified
button groups:
<%= buttongroup justified,
buttons => [
['Link 1', ['http://www.example.com/'] ],
['Link 2', ['http://www.example.com/'] ],
['Dropup 1', caret, dropup, items => [
['Item 1', ['item1'] ],
['Item 2', ['item2'] ],
[],
['Item 3', ['item3'] ],
] ],
]
%>
<div class="btn-group btn-group-justified">
<a class="btn btn-default" href="http://www.example.com/">Link 1</a>
<a class="btn btn-default" href="http://www.example.com/">Link 2</a>
<div class="btn-group dropup">
<button class="btn btn-default dropdown-toggle" type="button" data-toggle="dropdown">Dropup 1 <span class="caret"></span>
</button>
<ul class="dropdown-menu">
<li><a class="menuitem" href="item1" tabindex="-1">Item 1</a></li>
<li><a class="menuitem" href="item2" tabindex="-1">Item 2</a></li>
<li class="divider"></li>
<li><a class="menuitem" href="item3" tabindex="-1">Item 3</a></li>
</ul>
</div>
</div>
Split button dropdowns uses the same syntax as any other multi-button dropdown. Set the caret
button title to undef
:
<%= buttongroup
buttons => [
['Link 1', ['http://www.example.com/'] ],
[undef, caret, items => [
['Item 1', ['item1'] ],
['Item 2', ['item2'] ],
[],
['Item 3', ['item3'] ],
] ],
]
%>
<div class="btn-group">
<a class="btn btn-default" href="http://www.example.com/">Link 1</a>
<div class="btn-group">
<button class="btn btn-default dropdown-toggle" type="button" data-toggle="dropdown"><span class="caret"></span>
</button>
<ul class="dropdown-menu">
<li><a class="menuitem" href="item1" tabindex="-1">Item 1</a></li>
<li><a class="menuitem" href="item2" tabindex="-1">Item 2</a></li>
<li class="divider"></li>
<li><a class="menuitem" href="item3" tabindex="-1">Item 3</a></li>
</ul>
</div>
</div>
Using the simpler single-button button group dropdown syntax:
<%= buttongroup ['Default', caret, items => [
['Item 1', ['item1'] ],
['Item 2', ['item2'] ],
[],
['Item 3', ['item3'] ],
] ]
%>
<%= buttongroup ['Big danger', caret, large, danger, items => [
['Item 1', ['item1'] ],
['Item 2', ['item2'] ],
[],
['Item 3', ['item3'] ],
] ]
%>
<div class="btn-group">
<button class="btn btn-default dropdown-toggle" type="button" data-toggle="dropdown">Default <span class="caret"></span>
</button>
<ul class="dropdown-menu">
<li><a class="menuitem" href="item1" tabindex="-1">Item 1</a></li>
<li><a class="menuitem" href="item2" tabindex="-1">Item 2</a></li>
<li class="divider"></li>
<li><a class="menuitem" href="item3" tabindex="-1">Item 3</a></li>
</ul>
</div>
<div class="btn-group">
<button class="btn btn-danger btn-lg dropdown-toggle" type="button" data-toggle="dropdown">Big danger <span class="caret"></span>
</button>
<ul class="dropdown-menu">
<li><a class="menuitem" href="item1" tabindex="-1">Item 1</a></li>
<li><a class="menuitem" href="item2" tabindex="-1">Item 2</a></li>
<li class="divider"></li>
<li><a class="menuitem" href="item3" tabindex="-1">Item 3</a></li>
</ul>
</div>
Button toolbars
Syntax
<%= toolbar %toolbar_has,
groups => [
{ |button_group| }
]
%>
groups => [ { |button_group| } ]
A mandatory array reference of button groups.
Examples
<%= toolbar id => 'my-toolbar',
groups => [
{ buttons => [
['Button 1'],
['Button 2'],
['Button 3'],
],
},
{ buttons => [
['Button 4', primary],
['Button 5'],
['Button 6'],
],
},
]
%>
<div class="btn-toolbar" id="my-toolbar">
<div class="btn-group">
<button class="btn btn-default" type="button">Button 1</button>
<button class="btn btn-default" type="button">Button 2</button>
<button class="btn btn-default" type="button">Button 3</button>
</div>
<div class="btn-group">
<button class="btn btn-primary" type="button">Button 4</button>
<button class="btn btn-default" type="button">Button 5</button>
<button class="btn btn-default" type="button">Button 6</button>
</div>
</div>
Context menus
Context menus are a slight variation on dropdowns, where the button or other thing that opens the menu isn't part of the menu, such as menus that opens on right click. The context menu is created without the <div class="dropdown"></div> wrapper, so for it to show up at the right place its position must be set using either CSS or Javascript.
Syntax
<%= context_menu %has, items => [ |item| ] %>
items
Mandatory array reference consisting of one or many |item|
. Read more under "item".
Examples
<%= context_menu id => 'my-context-menu', items => [
['Item 1', ['item1'] ],
['Item 2', ['item2'] ],
[],
['Item 3', ['item3'] ]
] %>
</div>
<ul class="dropdown-menu" id="my-context-menu">
<li><a class="menuitem" href="item1" tabindex="-1">Item 1</a></li>
<li><a class="menuitem" href="item2" tabindex="-1">Item 2</a></li>
<li class="divider"></li>
<li><a class="menuitem" href="item3" tabindex="-1">Item 3</a></li>
</ul>
Dropdowns
Syntax
<%= dropdown %has,
[ |button|, items => [ |item| ]
]
[ |button| ]
Mandatory array reference. It takes an ordinary button, with two differences: The items
array reference, and it is unnecessary to give a button with items
a url.
items
Mandatory array reference consisting of one or many |item|
. Read more under "item".
Available shortcuts
caret
adds a <span class="caret"></span<>
element on the button.
Examples
By default,tabindex
is set to -1
:
<div class="text-right">
<%= dropdown
['Dropdown 1', id => 'a_custom_id', right, items => [
['Item 1', ['item1'] ],
['Item 2', ['item2'] ],
[],
['Item 3', ['item3'] ]
] ] %>
</div>
<div class="text-right">
<div class="dropdown">
<button class="btn btn-default dropdown-toggle" type="button" id="a_custom_id" data-toggle="dropdown">Dropdown 1</button>
<ul class="dropdown-menu dropdown-menu-right">
<li><a class="menuitem" href="item1" tabindex="-1">Item 1</a></li>
<li><a class="menuitem" href="item2" tabindex="-1">Item 2</a></li>
<li class="divider"></li>
<li><a class="menuitem" href="item3" tabindex="-1">Item 3</a></li>
</ul>
</div>
</div>
...but it can be overridden:
<%= dropdown
['Dropdown 2', caret, large, primary, items => [
['Item 1', ['item1'], data => { attr => 2 } ],
['Item 2', ['item2'], disabled, data => { attr => 4 } ],
[],
['Item 3', ['item3'], data => { attr => 7 } ],
[],
['Item 4', ['item4'], tabindex => 4 ],
'This is a header',
['Item 5', ['item5'] ],
] ] %>
<div class="dropdown">
<button class="btn btn-lg btn-primary dropdown-toggle" type="button" data-toggle="dropdown">Dropdown 2 <span class="caret"></span></button>
<ul class="dropdown-menu">
<li><a class="menuitem" href="item1" tabindex="-1" data-attr="2">Item 1</a></li>
<li class="disabled"><a class="menuitem" href="item2" tabindex="-1" data-attr="4">Item 2</a></li>
<li class="divider"></li>
<li><a class="menuitem" href="item3" tabindex="-1" data-attr="7">Item 3</a></li>
<li class="divider"></li>
<li><a class="menuitem" href="item4" tabindex="4">Item 4</a></li>
<li class="dropdown-header">This is a header</li>
<li><a class="menuitem" href="item5" tabindex="-1">Item 5</a></li>
</ul>
</div>
Form groups
Syntax
<%= formgroup ($labeltext,)
%formgroup_has,
(cols => { $size => [ $label_columns, $input_columns ], (...) })
$fieldtype => [
$input_name,
($input_value,)
%input_has,
]
%>
# The $labeltext can also be given in the body
%= formgroup <as above>, begin
$labeltext
% end
$labeltext
Optional. It is either the first argument, or placed in the body. It creates a label
element before the input
.
cols
Optional. It is only used when the form
is a .form-horizontal
. You can defined the widths for one or more or all of the sizes. See examples.
$size
Mandatory. It is one of xsmall
, small
, medium
or large
. $size
takes a two item array reference.
$label_columns
Mandatory. The number of columns that should be used by the label for that size of screen. Applies .col-$size-$label_columns
on the label.
$input_columns
Mandatory. The number of columns that should be used by the input for that size of screen. Applies .col-$size-$input_columns
around the input.
$fieldtype
Mandatory. Is one of text_field
, password_field
, datetime_field
, date_field
, month_field
, time_field
, week_field
, number_field
, email_field
, url_field
, search_field
, tel_field
, color_field
.
There can be only one $fieldtype
per formgroup
.
$name
Mandatory. It sets both the id
and name
of the input field. If the $name
contains dashes then those are translated into underscores when setting the name
. If id
exists in %input_has
then that is used for the id
instead.
$input_value
Optional. If you prefer you can set value
in %input_has
instead. (But don't do both for the same field.)
Examples
The first item in the array ref is used for bothid
and name
. Except...
%= formgroup 'Text test 1', text_field => ['test_text']
<div class="form-group">
<label class="control-label" for="test_text">Text test 1</label>
<input class="form-control" id="test_text" name="test_text" type="text" />
</div>
...if the input name (the first item in the text_field array ref) contains dashes -- those are replaced (in the name
) to underscores:
%= formgroup 'Text test 4', text_field => ['test-text', large]
<div class="form-group">
<label class="control-label" for="test-text">Text test 4</label>
<input class="form-control input-lg" id="test-text" name="test_text" type="text" />
</div>
An input with a value:
%= formgroup 'Text test 5', text_field => ['test_text', '200' ]
<div class="form-group">
<label class="control-label" for="test_text">Text test 5</label>
<input class="form-control" id="test_text" name="test_text" type="text" value="200" />
</div>
Note the difference with the earlier example. Here large
is outside the text_field
array reference, and therefore .form-group-lg
is applied to the form group:
<form class="form-horizontal">
%= formgroup 'Text test 6', text_field => ['test_text'], large, cols => { small => [2, 10] }
</form>
<form class="form-horizontal">
<div class="form-group form-group-lg">
<label class="control-label col-sm-2" for="test_text">Text test 6</label>
<div class="col-sm-10">
<input class="form-control" id="test_text" name="test_text" type="text">
</div>
</div>
</form>
A formgroup used in a .form-horizontal
form
:
(Note that in this context, medium
and large
are not shortcuts, but ordinary hash keys.)
%= formgroup 'Text test 8', text_field => ['test_text'], cols => { medium => [2, 10], small => [4, 8] }
<div class="form-group">
<label class="control-label col-md-2 col-sm-4" for="test_text">Text test 8</label>
<div class="col-md-10 col-sm-8">
<input class="form-control" id="test_text" name="test_text" type="text" />
</div>
</div>
Icons
This helper needs to be activated separately, see options below.
Syntax
%= icon $icon_name
$icon_name
Mandatory. The specific icon you wish to create. Possible values depends on your icon pack.
Examples
<%= icon 'copyright-mark' %>
%= icon 'sort-by-attributes-alt'
<span class="glyphicon glyphicon-copyright-mark"></span>
<span class="glyphicon glyphicon-sort-by-attributes-alt"></span>
Input groups
Syntax
<%= input %has,
(prepend => ...,)
input => { |input_field| },
(append => ...)
%>
input => { }
Mandatory hash reference. The content is handed off to input_tag in Mojolicious::Plugin::TagHelpers.
prepend
and append
Both are optional, but input groups don't make sense if neither is present. They take the same arguments, but there are a few to choose from:
prepend => $string
prepend => { check_box => [ |check_box| ] }
Creates a checkbox by giving its content to check_box in Mojolicious::Plugin::TagHelpers.
prepend => { radio_button => [ |radio_button| ] }
Creates a radiobutton by giving its content to radio_button in Mojolicious::Plugin::TagHelpers.
prepend => { buttongroup => { |buttongroup| }
Creates a single button buttongroup. See button groups for details.
prepend => { buttongroup => [ |buttongroup| ]
Creates a multi button buttongroup. See button groups for details.
Examples
An input group with a checkbox:<%= input input => { text_field => ['username'] },
prepend => { check_box => ['agreed'] }
%>
<div class="input-group">
<span class="input-group-addon"><input name="agreed" type="checkbox" /></span>
<input class="form-control" id="username" type="text" name="username" />
</div>
A large
input group with a radio button prepended and a string appended:
<%= input large,
prepend => { radio_button => ['yes'] },
input => { text_field => ['username'] },
append => '@'
%>
<div class="input-group input-group-lg">
<span class="input-group-addon"><input name="yes" type="radio" /></span>
<input class="form-control" id="username" type="text" name="username" />
<span class="input-group-addon">@</span>
</div>
An input group with a button:
<%= input input => { text_field => ['username'] },
append => { button => ['Click me!'] },
%>
<div class="input-group">
<input class="form-control" id="username" type="text" name="username" />
<span class="input-group-btn"><button class="btn btn-default" type="button">Click me!</button></span>
</div>
An input group with a button dropdown appended. Note that right
is manually applied:
<%= input input => { text_field => ['username'] },
append => { buttongroup => [['The button', caret, right, items => [
['Item 1', ['item1'] ],
['Item 2', ['item2'] ],
[],
['Item 3', ['item3'] ],
] ] ]
}
%>
<div class="input-group">
<input class="form-control" id="username" type="text" name="username" />
<div class="input-group-btn">
<button class="btn btn-default dropdown-toggle" type="button" data-toggle="dropdown">The button <span class="caret"></span>
</button>
<ul class="dropdown-menu dropdown-menu-right">
<li><a class="menuitem" href="item1" tabindex="-1">Item 1</a></li>
<li><a class="menuitem" href="item2" tabindex="-1">Item 2</a></li>
<li class="divider"></li>
<li><a class="menuitem" href="item3" tabindex="-1">Item 3</a></li>
</ul>
</div>
</div>
An input group with a split button dropdown prepended:
<%= input input => { text_field => ['username'] },
prepend => { buttongroup => [
buttons => [
['Link 1', ['http://www.example.com/'] ],
[undef, caret, items => [
['Item 1', ['item1'] ],
['Item 2', ['item2'] ],
[],
['Item 3', ['item3'] ],
],
],
],
],
},
%>
<div class="input-group">
<div class="input-group-btn">
<a class="btn btn-default" href="http://www.example.com/">Link 1</a>
<div class="btn-group">
<button class="btn btn-default dropdown-toggle" type="button" data-toggle="dropdown"><span class="caret"></span>
</button>
<ul class="dropdown-menu">
<li><a class="menuitem" href="item1" tabindex="-1">Item 1</a></li>
<li><a class="menuitem" href="item2" tabindex="-1">Item 2</a></li>
<li class="divider"></li>
<li><a class="menuitem" href="item3" tabindex="-1">Item 3</a></li>
</ul>
</div>
</div>
<input class="form-control" id="username" type="text" name="username" />
</div>
Navs
Syntax
<%= nav %has,
$type => [ |link|,
(items => [ |item| ])
]
%>
Navs
are syntactically similar to button groups.
$type => [...]
Mandatory. $type
is either pills
or tabs
(or items
if the nav
is in a navbar) and applies the adequate class to the surrounding ul
.
Examples
A simple pills navigation:<%= nav pills => [
['Item 1', ['#'] ],
['Item 2', ['#'], active ],
['Item 3', ['#'] ],
['Item 4', ['#'], disabled ],
]
%>
<ul class="nav nav-pills">
<li><a href="#">Item 1</a></li>
<li class="active"><a href="#">Item 2</a></li>
<li><a href="#">Item 3</a></li>
<li class="disabled"><a href="#">Item 4</a></li>
</ul>
A tab navigation with a menu:
<%= nav justified, id => 'my-nav', tabs => [
['Item 1', ['#'] ],
['Item 2', ['#'], active ],
['Item 3', ['#'] ],
['Dropdown', ['#'], caret, items => [
['There are...', ['#'] ],
['...three...', ['#'] ],
[],
['...choices', ['#'] ],
],
],
]
%>
<ul class="nav nav-justified nav-tabs" id="my-nav">
<li><a href="#">Item 1</a></li>
<li class="active"><a href="#">Item 2</a></li>
<li><a href="#">Item 3</a></li>
<li class="dropdown">
<a class="dropdown-toggle" data-toggle="dropdown" href="#">Dropdown <span class="caret"></span></a>
<ul class="dropdown-menu">
<li><a href="#">There are...</a></li>
<li><a href="#">...three...</a></li>
<li class="divider"></li>
<li><a href="#">...choices</a></li>
</ul>
</li>
</ul>
Navbars
Syntax
navbar (inverse,) (container => 'normal',) header => [ |link|, %navbar_has ],
form => [
[ [ $url ], %form_has ],
[
formgroup => [ |formgroup| ],
input => [ |input| ],
button => [ |button| ],
submit_button => [ |submit_button| ],
]
],
button => [ |button| ],
nav => [ |nav| ]
p => [ $text, %p_has ]
Navbars
are complex structures. They take the following arguments:
inverse
The inverse
shortcut is placed outside the %navbar_has
. It applies the .navbar-inverse
class.
container
Default: fluid
Allowed values: fluid
, normal
Sets the class on the container inside the navbar.
header => [ |link|, %navbar_has ]
header
creates a navbar-header
. There can be only one header
.
|link|
Creates the brand
. Set the link text to undef
if you don't want a brand.
%navbar_has
Can take the following extra arguments:
The hamburger
shortcut creates the menu button for collapsed navbars.
toggler => $collapse_id
This sets the id
on the collapsing part of the navbar. Set it if you need to reference that part of the navbar, otherwise an id will be generated.
The following arguments can appear any number of times, and is rendered in order.
button => [ |button| ]
Creates a button.
nav => [ |nav| ]
Creates a nav. Use items
if you need to create submenus.
p => [ $text, %p_has ]
Creates a <p>$text</p>
tag.
form => [...]
Creates a form
, by leveraging form_for in Mojolicious::Plugin::TagHelpers.
[ [ $url ], %form_has ]
Mandatory array reference. This sets up the form
tag.
[...]
Mandatory array reference. The second argument to form
can take different types (any number of times, rendered in order):
formgroup => [ |formgroup| ]
input => [ |input| ]
button => [ |button| ]
submit_button => [ |submit_button| ]
Creates form groups, input groups, buttons and submit_buttons
Examples
A simple navbar with a couple of links and a submenu:<%= navbar header => ['The brand', ['#'], hamburger, toggler => 'bs-example-navbar-collapse-2'],
nav => [ items => [
['Link', ['#'] ],
['Another link', ['#'], active ],
['Menu', ['#'], caret, items => [
['Choice 1', ['#'] ],
['Choice 2', ['#'] ],
[],
['Choice 3', ['#'] ],
] ],
]
]
%>
<nav class="navbar navbar-default">
<div class="container-fluid">
<div class="navbar-header">
<button class="collapsed navbar-toggle" data-target="#bs-example-navbar-collapse-2" data-toggle="collapse" type="button">
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
<a class="navbar-brand" href="#">The brand</a>
</div>
<div class="collapse navbar-collapse" id="bs-example-navbar-collapse-2">
<ul class="nav navbar-nav">
<li><a href="#">Link</a></li>
<li class="active"><a href="#">Another link</a></li>
<li class="dropdown">
<a class="dropdown-toggle" data-toggle="dropdown" href="#">Menu <span class="caret"></span></a>
<ul class="dropdown-menu">
<li><a href="#">Choice 1</a></li>
<li><a href="#">Choice 2</a></li>
<li class="divider"></li>
<li><a href="#">Choice 3</a></li>
</ul>
</li>
</ul>
</div>
</div>
</nav>
This is (almost) identical to the Bootstrap documentation example. The differences should be: The form
has an action and the input
has an id
and a name
:
<%= navbar header => ['Brand', ['#'], hamburger, toggler => 'collapse-4124'],
nav => [ items => [
['Link', ['#'], active ],
['Link', ['#'] ],
['Dropdown', ['#'], caret, items => [
['Action', ['#'] ],
['Another action', ['#'] ],
['Something else here', ['#'] ],
[],
['Separated link', ['#'] ],
[],
['One more separated link', ['#'] ],
] ] ],
],
form => [
[['/login'], method => 'post', left],
[
formgroup => [
text_field => ['the-search', placeholder => 'Search' ],
],
submit_button => ['Submit'],
]
],
nav => [
right,
items => [
['Link', ['#'] ],
['Dropdown', ['#'], caret, items => [
['Action', ['#'] ],
['Another action', ['#'] ],
['Something else here', ['#'] ],
[],
['Separated link', ['#'] ],
],
]
],
]
%>
<nav class="navbar navbar-default">
<div class="container-fluid">
<div class="navbar-header">
<button type="button" class="collapsed navbar-toggle" data-toggle="collapse" data-target="#collapse-4124">
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
<a class="navbar-brand" href="#">Brand</a>
</div>
<div class="collapse navbar-collapse" id="collapse-4124">
<ul class="nav navbar-nav">
<li class="active"><a href="#">Link</a></li>
<li><a href="#">Link</a></li>
<li class="dropdown">
<a class="dropdown-toggle" data-toggle="dropdown" href="#">Dropdown <span class="caret"></span></a>
<ul class="dropdown-menu">
<li><a href="#">Action</a></li>
<li><a href="#">Another action</a></li>
<li><a href="#">Something else here</a></li>
<li class="divider"></li>
<li><a href="#">Separated link</a></li>
<li class="divider"></li>
<li><a href="#">One more separated link</a></li>
</ul>
</li>
</ul>
<form action="/login" class="navbar-form navbar-left" method="post">
<div class="form-group">
<input class="form-control" id="the-search" name="the_search" placeholder="Search" type="text" />
</div>
<button class="btn btn-default" type="submit">Submit</button>
</form>
<ul class="nav navbar-nav navbar-right">
<li><a href="#">Link</a></li>
<li class="dropdown">
<a class="dropdown-toggle" data-toggle="dropdown" href="#">Dropdown <span class="caret"></span></a>
<ul class="dropdown-menu">
<li><a href="#">Action</a></li>
<li><a href="#">Another action</a></li>
<li><a href="#">Something else here</a></li>
<li class="divider"></li>
<li><a href="#">Separated link</a></li>
</ul>
</li>
</ul>
</div>
</div>
</nav>
Panels
Syntax
%= panel ($title, %has, begin
$body
% end)
$title
Usually mandatory, but can be omitted if there are no other arguments to the panel
. Otherwise, if you don't want a title, set it undef
.
$body
Optional (but panels are not much use without it). The html inside the panel
.
Examples
The class is set to.panel-default
, by default:
%= panel
<div class="panel panel-default">
<div class="panel-body">
</div>
</div>
If you want a panel without title, set the title to undef
:
%= panel undef ,=> begin
<p>A short text.</p>
% end
<div class="panel panel-default">
<div class="panel-body">
<p>A short text.</p>
</div>
</div>
A success
panel with a header:
%= panel 'Panel 5', success, begin
<p>A short text.</p>
% end
<div class="panel panel-success">
<div class="panel-heading">
<h3 class="panel-title">Panel 5</h3>
</div>
<div class="panel-body">
<p>A short text.</p>
</div>
</div>
Tables
Syntax
%= table ($title,) %table_has, panel => { %panel_has }, begin
$body
% end
$title
Optional. If set the table will be wrapped in a panel, and the table replaces the body in the panel.
$body
Mandatory. thead
, td
and so on.
panel => { %panel_has }
Optional if the table has a $title
, otherwise without use.
Examples
A basic table:<%= table begin %>
<thead>
<tr>
<th>th 1</th>
<th>th 2</th>
</thead>
<tbody>
<tr>
<td>Cell 1</td>
<td>Cell 2</td>
</tr>
<tr>
<td>Cell 1</td>
<td>Cell 2</td>
</tr>
</tbody>
<% end %>
<table class="table">
<thead>
<tr>
<th>th 1</th>
<th>th 2</th>
</thead>
<tbody>
<tr>
<td>Cell 1</td>
<td>Cell 2</td>
</tr>
<tr>
<td>Cell 1</td>
<td>Cell 2</td>
</tr>
</tbody>
</table>
Several classes applied to the table:
%= table hover, striped, condensed, begin
<thead>
<tr>
<th>th 1</th>
<th>th 2</th>
</thead>
<tbody>
<tr>
<td>Cell 1</td>
<td>Cell 2</td>
</tr>
<tr>
<td>Cell 1</td>
<td>Cell 2</td>
</tr>
</tbody>
% end
<table class="table table-condensed table-hover table-striped">
<thead>
<tr>
<th>th 1</th>
<th>th 2</th>
</thead>
<tbody>
<tr>
<td>Cell 1</td>
<td>Cell 2</td>
</tr>
<tr>
<td>Cell 1</td>
<td>Cell 2</td>
</tr>
</tbody>
</table>
A condensed
table with an id
wrapped in a success
panel:
%= table 'Heading Table 4', panel => { success }, condensed, id => 'the-table', begin
<thead>
<tr>
<th>th 1</th>
<th>th 2</th>
</thead>
<tbody>
<tr>
<td>Cell 1</td>
<td>Cell 2</td>
</tr>
<tr>
<td>Cell 1</td>
<td>Cell 2</td>
</tr>
</tbody>
% end
<div class="panel panel-success">
<div class="panel-heading">
<h3 class="panel-title">Heading Table 4</h3>
</div>
<table class="table table-condensed" id="the-table">
<thead>
<tr>
<th>th 1</th>
<th>th 2</th>
</thead>
<tbody>
<tr>
<td>Cell 1</td>
<td>Cell 2</td>
</tr>
<tr>
<td>Cell 1</td>
<td>Cell 2</td>
</tr>
</tbody>
</table>
</div>
OPTIONS
Some options are available:
$app->plugin('BootstrapHelpers', {
tag_prefix => 'bs',
shortcut_prefix => 'set',
init_shortcuts => 1,
icons => {
class => 'glyphicon'
formatter => 'glyphicon-%s',
},
});
tag_prefix
Default: undef
If you want to you change the name of the tag helpers, by applying a prefix. These are not aliases; by setting a prefix the original names are no longer available. The following rules are used:
If the option is missing, or is
undef
, there is no prefix.If the option is set to the empty string, the prefix is
_
. That is,panel
is now used as_panel
.If the option is set to any other string, the prefix is that string. If you set
tag_prefix => 'bs'
, thenpanel
is now used asbspanel
.
shortcut_prefix
Default: undef
This is similar to tag_prefix
, but is instead applied to the standalone shortcuts. The same rules applies.
init_shortcuts
Default: 1
If you don't want the standalone shortcuts setup at all, set this option to a defined but false value.
All functionality is available, but instead of warning
you must now write __warning => 1
.
With standalone form turned off, sizes are still only supported in long form: __xsmall
, __small
, __medium
and __large
. The Bootstrap abbreviations (xs
- lg
) are not available.
icons
Default: not set
By setting these keys you activate the icon
helper. You can pick any icon pack that sets one main class and one subclass to create an icon.
class
This is the main icon class. If you use the glyphicon pack, this should be set to 'glyphicon'.
formatter
This creates the specific icon class. If you use the glyphicon pack, this should be set to 'glyphicon-%s', where the '%s' will be replaced by the icon name you give the icon
helper.
SOURCE
https://github.com/Csson/p5-mojolicious-plugin-bootstraphelpers
HOMEPAGE
https://metacpan.org/release/Mojolicious-Plugin-BootstrapHelpers
AUTHOR
Erik Carlsson <info@code301.com>
LICENSE
This software is copyright (c) 2016 by Erik Carlsson.
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.
Bootstrap itself is (c) Twitter. See their license information.
Mojolicious::Plugin::BootstrapHelpers is third party software, and is not endorsed by Twitter.