I've used element-ui in a couple of projects and I like it a lot.
You can save bandwidth by importing just the needed elements, it has nice docs and changing the theme is almost easy :)
A lot of the larger frameworks have their own datagrid offerings. If you have a webpack setup, importing individual components should help keep the weight down.
There is also this standalone component, but it's at Vue 2.1 and the author hasn't been responding to issues.
I've been happy with the one included with Element. http://element.eleme.io/2.0/#/en-US/component/date-picker
Not sure if its able to be installed as an individual component outside of the framework though.
I've found that https://github.com/jackmellis/vuenit is extremely useful when trying to mock dependencies in a vue component.
But to your question... if you use the element libraries $notify you'll need to mock that http://element.eleme.io/#/en-US/component/notification
You might need to mock the vue-router if doing some page redirection ($router)
Modern and jQuery sounds like an oxymoron (not intended to be rude here)
Maybe you could find something already done in Vue.js, React et al. Have a look at Element UI and do the learning curve.
First, this certainly doesn't have anything to do with Laravel, and isn't a bug with VueJS.
Following their docs, they are using a string in the format YYYY-MM-DD
. There might be a bug with that component, because when you look at their example using default-value
, the calendar opens up with the correct year and month, but no date is highlighted.
Is that what you see happening with yours?
To debug, try adding <pre>ends_at: {{ ends_at }}</pre>
to your template, as well as a line for your default date).
Also, Don't mix {{ }}
syntax with bound props.
But we would like better integration with Vue, wouldn't we ? I'm starting using Element-ui - awesome set of widgets. More complete than Bootstrap 3, compared to BS 4 I don't know.
I use feathersjs.https://feathersjs.com It has cli to generate services and a js client which means you dont have to write the api calls. For frontend vuejs with http://element.eleme.io/#/en-US/component/button and some dashboard templates like this https://github.com/cristijora/vue-paper-dashboard These options helped me build prototypes with auth and a couple of pages under a day. Its a really good combo. Another alternative is loopback for your api but loopback is somehow bigger and harder to grasp.
I suggest using the mounted method. As mentioned by others, you can display a spinner until it's loaded. Check out Element ( http://element.eleme.io/1.4/#/en-US/component/loading ). For this package, you can just add a v-loading="isLoading" on the body where the data would be loaded. Then change that value to false when the data is fetched.
No I'm talking about how it's so similar to this. The other library that I saw was similar was the iview project but they seem to directly link to the Ant design page so I'll assume that was intentional
I just started playing with element-ui to get a management system and wanted to do a sidebar like Level 3 categories template? What did you use to get the basics up for element-ui?
I think you don't understand the "progressive" principle that Vue is based on. Its author made it pretty clear. If you want to make a prototype or write some small script for your page - you can do it with Vue. If you want to use modern tooling, ES6/7 and compile your code in a bundle - you can do it with Vue. And if you need not just a view library, but a whole ecosystem with a data store, router and other features - Vue is also a great choice.
It's not hard, it has no "magic". Vue components are straight objects that can be written without any compiler or other tool. Include Vue in your HTML page and write whatever you want without any implicit steps.
Vue components support both inheritance and composition (mixins). You can freely customise them if you want without monkey patching.
Templates vs. JSX is a matter of personal preference. I don't like JSX, that what I call "odd". UI should be declarative and described in a standard HTML, not in some weird language that cannot be read by designers. But that's just my opinion, and in Vue 2.x you can use both - they just compile into a render function.
As for lack of components, it's questionable. Chinese folks have written a lot of amazing stuff. But it's rather obscure for the international community, since in China they don't bother to make English documentation. Here are some great examples: