You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 24, 2023. It is now read-only.
🤝 Thanks to [Maciej Wach](https://github.com/wachu91) for inventing the name, testing and motivation.
9
9
10
10
---
11
11
12
-
🎉 **After about a year of the last version, I'm happy and excited to inform, that new `v1.0` version is coming soon! Some features I planed in version `v0.4` were for me impossible to realise and I got stuck in it completely. Version [`2.6 of Vue.js`](https://github.com/vuejs/vue/releases/tag/v2.6.0) opened new slots opportunities and now I can return to developing the plugin. I've learned a lot for that time so I also decided to refactor all code – it should be now cleaner and better optimised. Stay tuned!**
12
+
🎉 **After about a year from the last version, I'm happy and excited to inform, that new `v1.0` version is coming soon! Some features I planed in version `v0.4` were for me impossible to realise and I got stuck in it completely. Version [`2.6 of Vue.js`](https://github.com/vuejs/vue/releases/tag/v2.6.0) opened new slots opportunities and now I can return to developing the plugin. I've learned a lot for that time so I also decided to refactor all code – it should be now cleaner and better optimised. Stay tuned!**
13
13
14
14
---
15
15
16
16
## Important – update from version < `0.3`
17
17
18
-
**In version `0.3.0`, I removed all styles that are responsible for the appearance of navigation elements** (like dots color and shape, arrows position, etc.). I think most people use their own styles and default styles are completely redundant. If you want to check out these defaults styles, you can find them [here](https://github.com/lukaszflorczak/vue-agile/blob/master/src/Agile.vue#L488).
18
+
**In version `0.3.0`, I removed all styles that are responsible for the appearance of the navigation elements** (like dots color and shape, arrows position, etc.). I think most people use their own styles and default styles are completely redundant. If you want to check out these defaults styles, you can find them [here](https://github.com/lukaszflorczak/vue-agile/blob/master/src/Agile.vue#L488).
19
19
20
-
**Additionally dots and arrows have been moved from the `.agile__list` to the main `.agile` container.** The layout is the same as in Slick and id should allow for better and more comfortable positioning of these elements.
20
+
**Additionally dots and arrows have been moved from the `.agile__list` to the main `.agile` container.** The layout is the same as in Slick and should allow for and easier time positioning these elements.
21
21
22
22
## Installation
23
23
@@ -88,7 +88,7 @@ Every first-level child of `<agile>` is a new slide.
88
88
89
89
## Responsive
90
90
91
-
To customize responsiveness, I recommend defining desired breakpoint and passing a settings object with the options to modify inside **options**.
91
+
To customize responsiveness, I recommend defining your desired breakpoints and passing a settings object with your modification options inside **options**.
92
92
93
93
### Example
94
94
@@ -128,12 +128,12 @@ data () {
128
128
129
129
## Arrows
130
130
131
-
By default carousel contains SVG arrows. You can change them using CSS or `prevArrow` & `nextArrow` parameters.
131
+
By default a carousel contains SVG arrows. You can change them by using CSS or with the`prevArrow` & `nextArrow` parameters.
132
132
133
133
There are two important things:
134
134
135
-
1.You should put your SVG/HTML code in one line, without new line chars etc.
136
-
2. You should define arrows code as variables in`data()`.
135
+
1.Your SVG/HTML code should all be one line (no linebreaks, line chars, etc.)
136
+
2. You should define each of your arrows' code as variables within`data()`.
If you have dynamically loaded slides, use `v-if` to show carousel when slides will be ready. Using `v-if` is also recommended in other situations if you want to hide/show the slideshow.
158
+
If you have slides being dynamically loaded, use `v-if` to show the carousel after the slides are ready. Using `v-if` is also recommended in other situations if you want to hide/show the slideshow.
159
159
160
-
If for some reason you need to use `v-show`, it's also possible, but you have to use an additional parameter `show` with the same value as for the`v-show`.
160
+
It is also possible to use `v-show`, but you have to use the additional parameter `show` with the same value as what's in`v-show`.
161
161
162
162
### Example
163
163
```html
@@ -176,7 +176,7 @@ toggleAgile () {
176
176
177
177
## SSR Support
178
178
179
-
The component uses browser specific attributes (like `window` and `document`). It is necessary, so probably the only option is to run vue-agile only on the client-side. It was tested on [nuxt v1.0.0-rc7](https://github.com/nuxt/nuxt.js/releases/tag/v1.0.0-rc7) and works fine.
179
+
The component uses browser specific attributes (like `window` and `document`). Unfortunately, it is necessary -- so as of now, the only option is to run vue-agile solely on the client-side. It was tested on [nuxt v1.0.0-rc7](https://github.com/nuxt/nuxt.js/releases/tag/v1.0.0-rc7) and works fine.
0 commit comments