bulmajs-rails 0.3.3 → 0.11.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/.gitignore +13 -13
- data/.rspec +3 -3
- data/.travis.yml +5 -5
- data/CODE_OF_CONDUCT.md +74 -74
- data/Gemfile +6 -6
- data/Gemfile.lock +17 -17
- data/LICENSE.txt +21 -21
- data/README.md +128 -128
- data/Rakefile +6 -6
- data/bin/console +14 -14
- data/bin/setup +8 -8
- data/bulmajs-rails.gemspec +25 -25
- data/lib/bulmajs-rails.rb +4 -4
- data/vendor/assets/javascripts/bulma.js +289 -301
- metadata +12 -12
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 3175bb810d02cf93363e6d5d9fc23b0b1e74e343a1a46d82300a3a7dc931923d
|
|
4
|
+
data.tar.gz: 74c74d92d009368452c6bc20a2ccfee20feafaa667b49c4d636068da2b9bcb55
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: dce78273d376f8c483069d75e5bc0414e1f475c108b5353d7a26bae7653a19e709f082a834d551d409e2b59d3fec9f8ac68ed8955080c30b84c56715056f9dc5
|
|
7
|
+
data.tar.gz: e9725bc6fdd5ae9241f8c1cfba8ceae2051c3d04faeda2abeec89e249c3ce9e15b11e4bc97732e85b89c685ddc04b62636fb2892c11f2d1212cd668e284262ef
|
data/.gitignore
CHANGED
|
@@ -1,13 +1,13 @@
|
|
|
1
|
-
/.bundle/
|
|
2
|
-
/.yardoc
|
|
3
|
-
/_yardoc/
|
|
4
|
-
/coverage/
|
|
5
|
-
/doc/
|
|
6
|
-
/pkg/
|
|
7
|
-
/spec/reports/
|
|
8
|
-
/tmp/
|
|
9
|
-
/BulmaJS/
|
|
10
|
-
|
|
11
|
-
# rspec failure tracking
|
|
12
|
-
.rspec_status
|
|
13
|
-
*.gem
|
|
1
|
+
/.bundle/
|
|
2
|
+
/.yardoc
|
|
3
|
+
/_yardoc/
|
|
4
|
+
/coverage/
|
|
5
|
+
/doc/
|
|
6
|
+
/pkg/
|
|
7
|
+
/spec/reports/
|
|
8
|
+
/tmp/
|
|
9
|
+
/BulmaJS/
|
|
10
|
+
|
|
11
|
+
# rspec failure tracking
|
|
12
|
+
.rspec_status
|
|
13
|
+
*.gem
|
data/.rspec
CHANGED
|
@@ -1,3 +1,3 @@
|
|
|
1
|
-
--format documentation
|
|
2
|
-
--color
|
|
3
|
-
--require spec_helper
|
|
1
|
+
--format documentation
|
|
2
|
+
--color
|
|
3
|
+
--require spec_helper
|
data/.travis.yml
CHANGED
|
@@ -1,5 +1,5 @@
|
|
|
1
|
-
sudo: false
|
|
2
|
-
language: ruby
|
|
3
|
-
rvm:
|
|
4
|
-
- 2.5.1
|
|
5
|
-
before_install: gem install bundler -v 1.16.1
|
|
1
|
+
sudo: false
|
|
2
|
+
language: ruby
|
|
3
|
+
rvm:
|
|
4
|
+
- 2.5.1
|
|
5
|
+
before_install: gem install bundler -v 1.16.1
|
data/CODE_OF_CONDUCT.md
CHANGED
|
@@ -1,74 +1,74 @@
|
|
|
1
|
-
# Contributor Covenant Code of Conduct
|
|
2
|
-
|
|
3
|
-
## Our Pledge
|
|
4
|
-
|
|
5
|
-
In the interest of fostering an open and welcoming environment, we as
|
|
6
|
-
contributors and maintainers pledge to making participation in our project and
|
|
7
|
-
our community a harassment-free experience for everyone, regardless of age, body
|
|
8
|
-
size, disability, ethnicity, gender identity and expression, level of experience,
|
|
9
|
-
nationality, personal appearance, race, religion, or sexual identity and
|
|
10
|
-
orientation.
|
|
11
|
-
|
|
12
|
-
## Our Standards
|
|
13
|
-
|
|
14
|
-
Examples of behavior that contributes to creating a positive environment
|
|
15
|
-
include:
|
|
16
|
-
|
|
17
|
-
* Using welcoming and inclusive language
|
|
18
|
-
* Being respectful of differing viewpoints and experiences
|
|
19
|
-
* Gracefully accepting constructive criticism
|
|
20
|
-
* Focusing on what is best for the community
|
|
21
|
-
* Showing empathy towards other community members
|
|
22
|
-
|
|
23
|
-
Examples of unacceptable behavior by participants include:
|
|
24
|
-
|
|
25
|
-
* The use of sexualized language or imagery and unwelcome sexual attention or
|
|
26
|
-
advances
|
|
27
|
-
* Trolling, insulting/derogatory comments, and personal or political attacks
|
|
28
|
-
* Public or private harassment
|
|
29
|
-
* Publishing others' private information, such as a physical or electronic
|
|
30
|
-
address, without explicit permission
|
|
31
|
-
* Other conduct which could reasonably be considered inappropriate in a
|
|
32
|
-
professional setting
|
|
33
|
-
|
|
34
|
-
## Our Responsibilities
|
|
35
|
-
|
|
36
|
-
Project maintainers are responsible for clarifying the standards of acceptable
|
|
37
|
-
behavior and are expected to take appropriate and fair corrective action in
|
|
38
|
-
response to any instances of unacceptable behavior.
|
|
39
|
-
|
|
40
|
-
Project maintainers have the right and responsibility to remove, edit, or
|
|
41
|
-
reject comments, commits, code, wiki edits, issues, and other contributions
|
|
42
|
-
that are not aligned to this Code of Conduct, or to ban temporarily or
|
|
43
|
-
permanently any contributor for other behaviors that they deem inappropriate,
|
|
44
|
-
threatening, offensive, or harmful.
|
|
45
|
-
|
|
46
|
-
## Scope
|
|
47
|
-
|
|
48
|
-
This Code of Conduct applies both within project spaces and in public spaces
|
|
49
|
-
when an individual is representing the project or its community. Examples of
|
|
50
|
-
representing a project or community include using an official project e-mail
|
|
51
|
-
address, posting via an official social media account, or acting as an appointed
|
|
52
|
-
representative at an online or offline event. Representation of a project may be
|
|
53
|
-
further defined and clarified by project maintainers.
|
|
54
|
-
|
|
55
|
-
## Enforcement
|
|
56
|
-
|
|
57
|
-
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
|
58
|
-
reported by contacting the project team at theeomm@outlook.com. All
|
|
59
|
-
complaints will be reviewed and investigated and will result in a response that
|
|
60
|
-
is deemed necessary and appropriate to the circumstances. The project team is
|
|
61
|
-
obligated to maintain confidentiality with regard to the reporter of an incident.
|
|
62
|
-
Further details of specific enforcement policies may be posted separately.
|
|
63
|
-
|
|
64
|
-
Project maintainers who do not follow or enforce the Code of Conduct in good
|
|
65
|
-
faith may face temporary or permanent repercussions as determined by other
|
|
66
|
-
members of the project's leadership.
|
|
67
|
-
|
|
68
|
-
## Attribution
|
|
69
|
-
|
|
70
|
-
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
|
|
71
|
-
available at [http://contributor-covenant.org/version/1/4][version]
|
|
72
|
-
|
|
73
|
-
[homepage]: http://contributor-covenant.org
|
|
74
|
-
[version]: http://contributor-covenant.org/version/1/4/
|
|
1
|
+
# Contributor Covenant Code of Conduct
|
|
2
|
+
|
|
3
|
+
## Our Pledge
|
|
4
|
+
|
|
5
|
+
In the interest of fostering an open and welcoming environment, we as
|
|
6
|
+
contributors and maintainers pledge to making participation in our project and
|
|
7
|
+
our community a harassment-free experience for everyone, regardless of age, body
|
|
8
|
+
size, disability, ethnicity, gender identity and expression, level of experience,
|
|
9
|
+
nationality, personal appearance, race, religion, or sexual identity and
|
|
10
|
+
orientation.
|
|
11
|
+
|
|
12
|
+
## Our Standards
|
|
13
|
+
|
|
14
|
+
Examples of behavior that contributes to creating a positive environment
|
|
15
|
+
include:
|
|
16
|
+
|
|
17
|
+
* Using welcoming and inclusive language
|
|
18
|
+
* Being respectful of differing viewpoints and experiences
|
|
19
|
+
* Gracefully accepting constructive criticism
|
|
20
|
+
* Focusing on what is best for the community
|
|
21
|
+
* Showing empathy towards other community members
|
|
22
|
+
|
|
23
|
+
Examples of unacceptable behavior by participants include:
|
|
24
|
+
|
|
25
|
+
* The use of sexualized language or imagery and unwelcome sexual attention or
|
|
26
|
+
advances
|
|
27
|
+
* Trolling, insulting/derogatory comments, and personal or political attacks
|
|
28
|
+
* Public or private harassment
|
|
29
|
+
* Publishing others' private information, such as a physical or electronic
|
|
30
|
+
address, without explicit permission
|
|
31
|
+
* Other conduct which could reasonably be considered inappropriate in a
|
|
32
|
+
professional setting
|
|
33
|
+
|
|
34
|
+
## Our Responsibilities
|
|
35
|
+
|
|
36
|
+
Project maintainers are responsible for clarifying the standards of acceptable
|
|
37
|
+
behavior and are expected to take appropriate and fair corrective action in
|
|
38
|
+
response to any instances of unacceptable behavior.
|
|
39
|
+
|
|
40
|
+
Project maintainers have the right and responsibility to remove, edit, or
|
|
41
|
+
reject comments, commits, code, wiki edits, issues, and other contributions
|
|
42
|
+
that are not aligned to this Code of Conduct, or to ban temporarily or
|
|
43
|
+
permanently any contributor for other behaviors that they deem inappropriate,
|
|
44
|
+
threatening, offensive, or harmful.
|
|
45
|
+
|
|
46
|
+
## Scope
|
|
47
|
+
|
|
48
|
+
This Code of Conduct applies both within project spaces and in public spaces
|
|
49
|
+
when an individual is representing the project or its community. Examples of
|
|
50
|
+
representing a project or community include using an official project e-mail
|
|
51
|
+
address, posting via an official social media account, or acting as an appointed
|
|
52
|
+
representative at an online or offline event. Representation of a project may be
|
|
53
|
+
further defined and clarified by project maintainers.
|
|
54
|
+
|
|
55
|
+
## Enforcement
|
|
56
|
+
|
|
57
|
+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
|
58
|
+
reported by contacting the project team at theeomm@outlook.com. All
|
|
59
|
+
complaints will be reviewed and investigated and will result in a response that
|
|
60
|
+
is deemed necessary and appropriate to the circumstances. The project team is
|
|
61
|
+
obligated to maintain confidentiality with regard to the reporter of an incident.
|
|
62
|
+
Further details of specific enforcement policies may be posted separately.
|
|
63
|
+
|
|
64
|
+
Project maintainers who do not follow or enforce the Code of Conduct in good
|
|
65
|
+
faith may face temporary or permanent repercussions as determined by other
|
|
66
|
+
members of the project's leadership.
|
|
67
|
+
|
|
68
|
+
## Attribution
|
|
69
|
+
|
|
70
|
+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
|
|
71
|
+
available at [http://contributor-covenant.org/version/1/4][version]
|
|
72
|
+
|
|
73
|
+
[homepage]: http://contributor-covenant.org
|
|
74
|
+
[version]: http://contributor-covenant.org/version/1/4/
|
data/Gemfile
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
|
-
source "https://rubygems.org"
|
|
2
|
-
|
|
3
|
-
git_source(:github) {|repo_name| "https://github.com/#{repo_name}" }
|
|
4
|
-
|
|
5
|
-
# Specify your gem's dependencies in bulmajs-rails.gemspec
|
|
6
|
-
gemspec
|
|
1
|
+
source "https://rubygems.org"
|
|
2
|
+
|
|
3
|
+
git_source(:github) {|repo_name| "https://github.com/#{repo_name}" }
|
|
4
|
+
|
|
5
|
+
# Specify your gem's dependencies in bulmajs-rails.gemspec
|
|
6
|
+
gemspec
|
data/Gemfile.lock
CHANGED
|
@@ -1,35 +1,35 @@
|
|
|
1
1
|
PATH
|
|
2
2
|
remote: .
|
|
3
3
|
specs:
|
|
4
|
-
bulmajs-rails (0.
|
|
4
|
+
bulmajs-rails (0.11.0)
|
|
5
5
|
|
|
6
6
|
GEM
|
|
7
7
|
remote: https://rubygems.org/
|
|
8
8
|
specs:
|
|
9
9
|
diff-lcs (1.3)
|
|
10
|
-
rake (
|
|
11
|
-
rspec (3.
|
|
12
|
-
rspec-core (~> 3.
|
|
13
|
-
rspec-expectations (~> 3.
|
|
14
|
-
rspec-mocks (~> 3.
|
|
15
|
-
rspec-core (3.
|
|
16
|
-
rspec-support (~> 3.
|
|
17
|
-
rspec-expectations (3.
|
|
10
|
+
rake (13.0.0)
|
|
11
|
+
rspec (3.8.0)
|
|
12
|
+
rspec-core (~> 3.8.0)
|
|
13
|
+
rspec-expectations (~> 3.8.0)
|
|
14
|
+
rspec-mocks (~> 3.8.0)
|
|
15
|
+
rspec-core (3.8.2)
|
|
16
|
+
rspec-support (~> 3.8.0)
|
|
17
|
+
rspec-expectations (3.8.4)
|
|
18
18
|
diff-lcs (>= 1.2.0, < 2.0)
|
|
19
|
-
rspec-support (~> 3.
|
|
20
|
-
rspec-mocks (3.
|
|
19
|
+
rspec-support (~> 3.8.0)
|
|
20
|
+
rspec-mocks (3.8.1)
|
|
21
21
|
diff-lcs (>= 1.2.0, < 2.0)
|
|
22
|
-
rspec-support (~> 3.
|
|
23
|
-
rspec-support (3.
|
|
22
|
+
rspec-support (~> 3.8.0)
|
|
23
|
+
rspec-support (3.8.2)
|
|
24
24
|
|
|
25
25
|
PLATFORMS
|
|
26
26
|
x64-mingw32
|
|
27
27
|
|
|
28
28
|
DEPENDENCIES
|
|
29
29
|
bulmajs-rails!
|
|
30
|
-
bundler (~> 1.
|
|
31
|
-
rake (~>
|
|
32
|
-
rspec (~> 3.
|
|
30
|
+
bundler (~> 1.17)
|
|
31
|
+
rake (~> 13.0)
|
|
32
|
+
rspec (~> 3.8)
|
|
33
33
|
|
|
34
34
|
BUNDLED WITH
|
|
35
|
-
1.
|
|
35
|
+
1.17.2
|
data/LICENSE.txt
CHANGED
|
@@ -1,21 +1,21 @@
|
|
|
1
|
-
The MIT License (MIT)
|
|
2
|
-
|
|
3
|
-
Copyright (c) 2018 Douglas Harrington Muhone
|
|
4
|
-
|
|
5
|
-
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
-
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
-
in the Software without restriction, including without limitation the rights
|
|
8
|
-
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
-
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
-
furnished to do so, subject to the following conditions:
|
|
11
|
-
|
|
12
|
-
The above copyright notice and this permission notice shall be included in
|
|
13
|
-
all copies or substantial portions of the Software.
|
|
14
|
-
|
|
15
|
-
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
|
-
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
-
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
18
|
-
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
19
|
-
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
20
|
-
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
|
|
21
|
-
THE SOFTWARE.
|
|
1
|
+
The MIT License (MIT)
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2018 Douglas Harrington Muhone
|
|
4
|
+
|
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
+
in the Software without restriction, including without limitation the rights
|
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
+
furnished to do so, subject to the following conditions:
|
|
11
|
+
|
|
12
|
+
The above copyright notice and this permission notice shall be included in
|
|
13
|
+
all copies or substantial portions of the Software.
|
|
14
|
+
|
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
|
|
21
|
+
THE SOFTWARE.
|
data/README.md
CHANGED
|
@@ -1,128 +1,128 @@
|
|
|
1
|
-
# Bulmajs::Rails
|
|
2
|
-
|
|
3
|
-
Bulmajs-rails is the implementation of [BulmaJS](https://github.com/VizuaaLOG/BulmaJS)
|
|
4
|
-
|
|
5
|
-
BulmaJS is an unofficial javascript extension to the awesome [Bulma CSS framework](https://bulma.io)
|
|
6
|
-
|
|
7
|
-
Source: [https://github.com/VizuaaLOG/BulmaJS](https://github.com/VizuaaLOG/BulmaJS)
|
|
8
|
-
|
|
9
|
-
Ruby Gem: [https://rubygems.org/gems/bulmajs-rails](https://rubygems.org/gems/jquery-rails)
|
|
10
|
-
|
|
11
|
-
## Installation
|
|
12
|
-
|
|
13
|
-
Add this line to your application's Gemfile:
|
|
14
|
-
|
|
15
|
-
```ruby
|
|
16
|
-
gem 'bulmajs-rails'
|
|
17
|
-
```
|
|
18
|
-
|
|
19
|
-
And then execute:
|
|
20
|
-
|
|
21
|
-
$ bundle
|
|
22
|
-
|
|
23
|
-
Or install it yourself as:
|
|
24
|
-
|
|
25
|
-
$ gem install bulmajs-rails
|
|
26
|
-
|
|
27
|
-
Now you need to edit your `app/assets/javascripts/application.js` file and add the following line:
|
|
28
|
-
|
|
29
|
-
```javascript
|
|
30
|
-
//= require bulma
|
|
31
|
-
```
|
|
32
|
-
|
|
33
|
-
## Turbolinks is now required for this wrapper.
|
|
34
|
-
|
|
35
|
-
## Usage Examples
|
|
36
|
-
|
|
37
|
-
### Basic Tabs
|
|
38
|
-
|
|
39
|
-
```html
|
|
40
|
-
<div id="tabs-example" data-bulma="tabs">
|
|
41
|
-
<div class="tabs" data-links>
|
|
42
|
-
<ul>
|
|
43
|
-
<li class="is-active">
|
|
44
|
-
<a>Pictures</a>
|
|
45
|
-
</li>
|
|
46
|
-
<li>
|
|
47
|
-
<a>Music</a>
|
|
48
|
-
</li>
|
|
49
|
-
<li>
|
|
50
|
-
<a>Videos</a>
|
|
51
|
-
</li>
|
|
52
|
-
<li>
|
|
53
|
-
<a>Documents</a>
|
|
54
|
-
</li>
|
|
55
|
-
</ul>
|
|
56
|
-
</div>
|
|
57
|
-
|
|
58
|
-
<div class="tabs-content" data-content>
|
|
59
|
-
<ul>
|
|
60
|
-
<li class="is-active">
|
|
61
|
-
<h1>Pictures</h1>
|
|
62
|
-
</li>
|
|
63
|
-
<li>
|
|
64
|
-
<h1>Music</h1>
|
|
65
|
-
</li>
|
|
66
|
-
<li>
|
|
67
|
-
<h1>Videos</h1>
|
|
68
|
-
</li>
|
|
69
|
-
<li>
|
|
70
|
-
<h1>Documents</h1>
|
|
71
|
-
</li>
|
|
72
|
-
</ul>
|
|
73
|
-
</div>
|
|
74
|
-
</div>
|
|
75
|
-
```
|
|
76
|
-
|
|
77
|
-
### Navbar Mobile Toggle
|
|
78
|
-
|
|
79
|
-
All you need to do is add `data-bulma="navbar"` to the main navbar div, and then add `data-trigger` and `data-target="navID"` to the navbar burger
|
|
80
|
-
|
|
81
|
-
```html
|
|
82
|
-
<nav class="navbar" data-bulma="navbar">
|
|
83
|
-
<div class="navbar-brand">
|
|
84
|
-
<!-- Your other HTML here -->
|
|
85
|
-
<div class="navbar-burger burger" data-trigger data-target="navMenuExample">
|
|
86
|
-
<span></span>
|
|
87
|
-
<span></span>
|
|
88
|
-
<span></span>
|
|
89
|
-
</div>
|
|
90
|
-
</div>
|
|
91
|
-
<div id="navMenuExample" class="navbar-menu">
|
|
92
|
-
<!-- Your navbar HTML here -->
|
|
93
|
-
</div>
|
|
94
|
-
</nav>
|
|
95
|
-
```
|
|
96
|
-
|
|
97
|
-
### Filename Updating
|
|
98
|
-
|
|
99
|
-
```html
|
|
100
|
-
<div class="file has-name is-boxed" data-bulma="file">
|
|
101
|
-
<label class="file-label">
|
|
102
|
-
<input class="file-input" type="file" name="resume" multiple>
|
|
103
|
-
<span class="file-cta">
|
|
104
|
-
<span class="file-icon">
|
|
105
|
-
<i class="fa fa-upload"></i>
|
|
106
|
-
</span>
|
|
107
|
-
<span class="file-label">
|
|
108
|
-
Choose a file…
|
|
109
|
-
</span>
|
|
110
|
-
</span>
|
|
111
|
-
<span class="file-name"></span>
|
|
112
|
-
</label>
|
|
113
|
-
</div>
|
|
114
|
-
```
|
|
115
|
-
|
|
116
|
-
More examples and explanation are on available [https://vizuaalog.github.io/BulmaJS](https://vizuaalog.github.io/BulmaJS)
|
|
117
|
-
|
|
118
|
-
## Contributing
|
|
119
|
-
|
|
120
|
-
Bug reports and pull requests are welcome on GitHub at https://github.com/theeomm/bulmajs-rails. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
|
|
121
|
-
|
|
122
|
-
## Special Thanks
|
|
123
|
-
|
|
124
|
-
[Thomas](https://github.com/VizuaaLOG) - Creator of BulmaJS
|
|
125
|
-
|
|
126
|
-
## License
|
|
127
|
-
|
|
128
|
-
The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
|
|
1
|
+
# Bulmajs::Rails
|
|
2
|
+
|
|
3
|
+
Bulmajs-rails is the implementation of [BulmaJS](https://github.com/VizuaaLOG/BulmaJS)
|
|
4
|
+
|
|
5
|
+
BulmaJS is an unofficial javascript extension to the awesome [Bulma CSS framework](https://bulma.io)
|
|
6
|
+
|
|
7
|
+
Source: [https://github.com/VizuaaLOG/BulmaJS](https://github.com/VizuaaLOG/BulmaJS)
|
|
8
|
+
|
|
9
|
+
Ruby Gem: [https://rubygems.org/gems/bulmajs-rails](https://rubygems.org/gems/jquery-rails)
|
|
10
|
+
|
|
11
|
+
## Installation
|
|
12
|
+
|
|
13
|
+
Add this line to your application's Gemfile:
|
|
14
|
+
|
|
15
|
+
```ruby
|
|
16
|
+
gem 'bulmajs-rails'
|
|
17
|
+
```
|
|
18
|
+
|
|
19
|
+
And then execute:
|
|
20
|
+
|
|
21
|
+
$ bundle
|
|
22
|
+
|
|
23
|
+
Or install it yourself as:
|
|
24
|
+
|
|
25
|
+
$ gem install bulmajs-rails
|
|
26
|
+
|
|
27
|
+
Now you need to edit your `app/assets/javascripts/application.js` file and add the following line:
|
|
28
|
+
|
|
29
|
+
```javascript
|
|
30
|
+
//= require bulma
|
|
31
|
+
```
|
|
32
|
+
|
|
33
|
+
## Turbolinks is now required for this wrapper.
|
|
34
|
+
|
|
35
|
+
## Usage Examples
|
|
36
|
+
|
|
37
|
+
### Basic Tabs
|
|
38
|
+
|
|
39
|
+
```html
|
|
40
|
+
<div id="tabs-example" data-bulma="tabs">
|
|
41
|
+
<div class="tabs" data-links>
|
|
42
|
+
<ul>
|
|
43
|
+
<li class="is-active">
|
|
44
|
+
<a>Pictures</a>
|
|
45
|
+
</li>
|
|
46
|
+
<li>
|
|
47
|
+
<a>Music</a>
|
|
48
|
+
</li>
|
|
49
|
+
<li>
|
|
50
|
+
<a>Videos</a>
|
|
51
|
+
</li>
|
|
52
|
+
<li>
|
|
53
|
+
<a>Documents</a>
|
|
54
|
+
</li>
|
|
55
|
+
</ul>
|
|
56
|
+
</div>
|
|
57
|
+
|
|
58
|
+
<div class="tabs-content" data-content>
|
|
59
|
+
<ul>
|
|
60
|
+
<li class="is-active">
|
|
61
|
+
<h1>Pictures</h1>
|
|
62
|
+
</li>
|
|
63
|
+
<li>
|
|
64
|
+
<h1>Music</h1>
|
|
65
|
+
</li>
|
|
66
|
+
<li>
|
|
67
|
+
<h1>Videos</h1>
|
|
68
|
+
</li>
|
|
69
|
+
<li>
|
|
70
|
+
<h1>Documents</h1>
|
|
71
|
+
</li>
|
|
72
|
+
</ul>
|
|
73
|
+
</div>
|
|
74
|
+
</div>
|
|
75
|
+
```
|
|
76
|
+
|
|
77
|
+
### Navbar Mobile Toggle
|
|
78
|
+
|
|
79
|
+
All you need to do is add `data-bulma="navbar"` to the main navbar div, and then add `data-trigger` and `data-target="navID"` to the navbar burger
|
|
80
|
+
|
|
81
|
+
```html
|
|
82
|
+
<nav class="navbar" data-bulma="navbar">
|
|
83
|
+
<div class="navbar-brand">
|
|
84
|
+
<!-- Your other HTML here -->
|
|
85
|
+
<div class="navbar-burger burger" data-trigger data-target="navMenuExample">
|
|
86
|
+
<span></span>
|
|
87
|
+
<span></span>
|
|
88
|
+
<span></span>
|
|
89
|
+
</div>
|
|
90
|
+
</div>
|
|
91
|
+
<div id="navMenuExample" class="navbar-menu">
|
|
92
|
+
<!-- Your navbar HTML here -->
|
|
93
|
+
</div>
|
|
94
|
+
</nav>
|
|
95
|
+
```
|
|
96
|
+
|
|
97
|
+
### Filename Updating
|
|
98
|
+
|
|
99
|
+
```html
|
|
100
|
+
<div class="file has-name is-boxed" data-bulma="file">
|
|
101
|
+
<label class="file-label">
|
|
102
|
+
<input class="file-input" type="file" name="resume" multiple>
|
|
103
|
+
<span class="file-cta">
|
|
104
|
+
<span class="file-icon">
|
|
105
|
+
<i class="fa fa-upload"></i>
|
|
106
|
+
</span>
|
|
107
|
+
<span class="file-label">
|
|
108
|
+
Choose a file…
|
|
109
|
+
</span>
|
|
110
|
+
</span>
|
|
111
|
+
<span class="file-name"></span>
|
|
112
|
+
</label>
|
|
113
|
+
</div>
|
|
114
|
+
```
|
|
115
|
+
|
|
116
|
+
More examples and explanation are on available [https://vizuaalog.github.io/BulmaJS](https://vizuaalog.github.io/BulmaJS)
|
|
117
|
+
|
|
118
|
+
## Contributing
|
|
119
|
+
|
|
120
|
+
Bug reports and pull requests are welcome on GitHub at https://github.com/theeomm/bulmajs-rails. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
|
|
121
|
+
|
|
122
|
+
## Special Thanks
|
|
123
|
+
|
|
124
|
+
[Thomas](https://github.com/VizuaaLOG) - Creator of BulmaJS
|
|
125
|
+
|
|
126
|
+
## License
|
|
127
|
+
|
|
128
|
+
The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
|