Besides the already mentioned UIs I am also watching https://vuetifyjs.com , looks promising.
Element – A Vue 2.0-based component library for developers, designers and PMs
101–110 of 149 posts
Re: Element – A Vue 2.0-based component library for developers, designers and PMs
#102Earlier quoted context omitted.
I agree that it depends on your project, but I've used all the frameworks you listed and Vue.js stands out to me. The documentation is top notch, the ecosystem is flourishing, and using the framework feels intuitive. Drop one script into your project and you have a fully reactive front-end at your disposal (or you can use a more complex build system like Webpack). I'd suggest reading the official 2.0 guide here: http…
Let us dispel the notion that webpack is 'complex'. webpack works extremely hard to make its documentation [1] and overall tool easy to read and use. The community is ever-growing and it has one of the most helpful and enthusiastic maintainers I've ever seen a JavaScript OSS project have. Ever. (Look at you Larkin!) From egghead.io to online documentation, you will see that while webpack has a lot to it, it is easy t…
Quick FYI: that link is the old-old Webpack 1.x docs.
The current Webpack docs, which have been completely re-written and are _vastly_ better, are at https://webpack.js.org/ .
Re: Element – A Vue 2.0-based component library for developers, designers and PMs
#103Earlier quoted context omitted.
Polymer is built for the world without Vue.js or React. They are slow and heavy weight compared to very very optimized DOM operations done by Vue.js or React. I think the time for Polymer is gone, and it is better to forget that it exists.
I mean, custom elements just shipped in Chrome a few months ago and are shipping in Safari soon. Firefox is in active development. So a bit too soon to say a technology's time has passed when it hasn't really had a chance up until this point.
Chrome has had Custom Elements since v33, almost 3 years ago. Maybe you're thinking of the latest (v1) iteration of the spec? http://caniuse.com/#feat=custom-elements
Re: Element – A Vue 2.0-based component library for developers, designers and PMs
#104Question for HN: I'm a systems developer and want to play a bit with frontend development (writing frontends for custom tools I built). What framework + feature-complete component library is recommended in 2017? React? Vue? Polymer? Plain JS with intercooler.js? I feel a bit overwhelmed.
React is actually not that easy to pick up. Tons of ways to do things, messy data management, complex lifecycle hooks. vue or riot would be a good choice to play and develop something quickly I think.
I finally spent the time to learn it recently, and it's really only hard if you make it hard on yourself. Plain old react without redux is pretty dang simple, actually.
Re: Element – A Vue 2.0-based component library for developers, designers and PMs
#105Question for HN: I'm a systems developer and want to play a bit with frontend development (writing frontends for custom tools I built). What framework + feature-complete component library is recommended in 2017? React? Vue? Polymer? Plain JS with intercooler.js? I feel a bit overwhelmed.
Mithril is a very non-overwhelming framework. You can find a number of pre-built components for it at https://github.com/lhorie/mithril.js/wiki/Components but I bet you'll end up building your own. How familiar are you with JavaScript? HTML?
I've found Mithril to be a giant pile of crap. Buggy on most browsers and incredibly painful to use. Run, don't walk from this platform.
Re: Element – A Vue 2.0-based component library for developers, designers and PMs
#106Earlier quoted context omitted.
Can I use Polymer components with Vue.js?
No you can not. Telling from experience. Here is the reason.. Vue is optimized to create/update your DOM elements based on data. Polymer does create a DOM node and internally implement lot os JS to create their own shadow DOM. Each Polyer component can have different life cycle (for Example and Table Component can actually creat TR,TD elements after some time of creating your Custom Table Polymer component). And Vue…
Thanks. It sounds like it would get easier with Polymer 2.0?
Re: Element – A Vue 2.0-based component library for developers, designers and PMs
#107Question for HN: I'm a systems developer and want to play a bit with frontend development (writing frontends for custom tools I built). What framework + feature-complete component library is recommended in 2017? React? Vue? Polymer? Plain JS with intercooler.js? I feel a bit overwhelmed.
All the options you mention are perfectly viable, and none of them is 'strictly better' than the other. This thread will be filled with people telling you to use one of them because reason X, or not use one because reason Y. It's like arguing which brand of beer is the best, there's no definitive answer to a question like that. This thread will be filled with choice-supportive biased comments, and their arguments might not apply to you at all. It comes down to personal requirements and taste.
Really like Javascript over HTML? React is probably for you.
Don't care about details and just want things to work? Vue could be nice.
Prefer sticking as close as possible to the W3C specifications? You will like Polymer.
Telling you want you should use is like telling you what things you should value. Again, all the options are great. All of them have mature tooling, and will 'just work' if you buy in to their way of doing things. Just try them and figure out which one you like.
Re: Element – A Vue 2.0-based component library for developers, designers and PMs
#108I tried using Element on my current project and, like other commenters, found it to lack enough responsive utilities to make it useful. Then I stumbled upon Quasar ( http://quasar-framework.org/ ). It's responsive, supports Cordova and Electron, and it looks good. I rarely switch frameworks mid-project, but this was well worth the effort.
Looks really good. I usually judge a library by it's data table. This one seems surprisingly featured.
Re: Element – A Vue 2.0-based component library for developers, designers and PMs
#109Question for HN: I'm a systems developer and want to play a bit with frontend development (writing frontends for custom tools I built). What framework + feature-complete component library is recommended in 2017? React? Vue? Polymer? Plain JS with intercooler.js? I feel a bit overwhelmed.
If you can stomach a little build tool complexity (a one-time cost), React + MobX is basically a better, simpler Vue.
Re: Element – A Vue 2.0-based component library for developers, designers and PMs
#110I have actually tried to use this to build an enterprise application. Here is what we found. * Most of the components they provide are very basic and does not actually require them to provide it. Couple of lines of wrapper on any CSS framework like bootstrap can make half of those components. * Most of the advanced components like DataGrid, DropDown Menus, etc are aither not available or buggy. You will get better su…
I've never used Element, but I share your sentiment. For a library like Vue which doesn't yet (!) have the adoption of React, I tend to avoid 3rd party component libraries especially if they are full of fluff like footer/header components.
I looked at using Vue 2 with bootstrap 4 this past weekend and it seems most Vue+bootstrap integrations are for Vue 1.x while the Vue 2.x bootstrap libraries are incomplete. Instead I just included bootstrap's CSS and for the most part things just work. For things that require JS like modals I found the official bootstrap JS code was very easy to read and had a Vue modal component up and running pretty quickly. I wish the bootstrap docs were a bit clearer as to where JS is used to enhance components. The foundation docs in comparison have the tiny "JS" badge next to all the JS enhanced components, but I'd like to see something more along the lines of "JavaScript is required to disable the body element's scrollbar and to dynamically add the modal backdrop to the DOM".
One thing I find tiring in the JS ecosystem is the constant rewriting of vanilla JS libraries so they play nicely with virtual-dom based libraries and all of the framework specific component libraries which too often play a major role in determining our tech stack. It all just seems like a massive wasted effort.