Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Element – A Vue 2.0-based component library for developers, designers and PMs

element.eleme.io

Post reply on HN
Print view View original

141–149 of 149 posts

Re: Element – A Vue 2.0-based component library for developers, designers and PMs

#141

Post by pryelluw »

netforay wrote: post #36

I 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…

This is one of the reasons I'm working on Bootparts[1]. I needed components to build websites that were JS agnostic. Its based on Bootstrap 3 and under active development. Check it out and let me know of any feedback you may have. Its fairly new (v0.4) but have a 5 year commitment to it.

https://yelluw.github.io/Bootparts

Re: Element – A Vue 2.0-based component library for developers, designers and PMs

#142

Post by scriptkiddy »

patleeman wrote: post #68

For anyone looking for a lightweight responsive library, Bulma http://bulma.io/ is a great option. It pairs with Vue quite well since it's a CSS only library. Note: I'm not affiliated with them, just using them on my latest project.

I've been using Bulma on my side project. Really nice looking and super easy to use. I like how it doesn't try to do too much.

Re: Element – A Vue 2.0-based component library for developers, designers and PMs

#143

Post by thirdsun »

tracker1 wrote: post #116
thirdsun wrote: post #39

Earlier quoted context omitted.

I'm not OP and I made the experience with Zurb's Foundation but the problem isn't specific to the framework. In my opinion you'll run into issues with these kitchen sink frameworks once you try to do something custom - customizing elements and components feels like fighting the framework at a certain point and once you realize that it's hard to get out. I don't recommend using Bootstrap or any other framework unless…

I find that using the SCSS/Less source for bootstrap is less fighting... the layout/structure is pretty easy to use internally, for the most part, everything I need for creating additional controls starts from variables and utilities.

But you would break all that once it comes to updating the framework, wouldn't you? With Foundation it was either that or constantly overriding framework defaults. Once you took a look at the rules in the browser inspector / dev tools you saw many of them leading to conflicts and it felt very messy despite end results working out.

Re: Element – A Vue 2.0-based component library for developers, designers and PMs

#144

Post by netforay »

Touche wrote: post #64
netforay wrote: post #52

Earlier quoted context omitted.

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…

I don't understand your point. Can Vue update ` `? If so it should be able to update any custom element.

Yes, that is what I thought. Until I started using some more wired Polymer components. Not all components get problems though.

Re: Element – A Vue 2.0-based component library for developers, designers and PMs

#145

Post by simooooo »

lima wrote: post #45
simooooo wrote: post #5

Earlier quoted context omitted.

I've been using Vue for a similar purpose this last week or two and I've found it very simple and easy to follow. I'd recommend that.

What component library to use?

Currently I'm not using one, building my own context menu, graph and grid components as a way of testing out vue, and to see if I can do it. Reasonably straight forward so far

Re: Element – A Vue 2.0-based component library for developers, designers and PMs

#146

Post by tracker1 »

thirdsun wrote: post #143
tracker1 wrote: post #116

Earlier quoted context omitted.

I find that using the SCSS/Less source for bootstrap is less fighting... the layout/structure is pretty easy to use internally, for the most part, everything I need for creating additional controls starts from variables and utilities.

But you would break all that once it comes to updating the framework, wouldn't you? With Foundation it was either that or constantly overriding framework defaults. Once you took a look at the rules in the browser inspector / dev tools you saw many of them leading to conflicts and it felt very messy despite end results working out.

I usually copy the variables/utils to my project (often just the variables)... when updating minor/point version updates, it's usually a quick diff against the framework version to see what's been added/changed. Major versions are usually close to a rewrite of the rendering templates/components, so that's the case regardless.

I have my own bootstrap.scss, with my own variables/utils... the rest point to the framework versions... It's pretty easy to do and works out really well imho. Of course, I often only change a few colors, and tweak some of the font defaults.

Re: Element – A Vue 2.0-based component library for developers, designers and PMs

#147

Post by progx »

aczerepinski wrote: post #53
lima wrote: post #2

Question 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. If you're new to the front end, it makes sense to choose the most popular tool that has way more documentation, blog posts, stack overflow answers, etc than anything else.

But most of the posts or stack overflow entries are obsolete and confuses more than it helps, you always have to look for the version or the date (if they are mentioned)

Re: Element – A Vue 2.0-based component library for developers, designers and PMs

#148

Post by ergo14 »

netforay wrote: post #140
ergo14 wrote: post #91

Earlier quoted context omitted.

Interesting - the benchmarks prove otherwise - it is as fast as other new solutions. So i think you never actually used it in production at any scale. If angular 1.5 was OK for thousands of devs over recent years then Polymer that is comparable to ng2 or react is more then enough. Not to mention that for a world without polymer - some of biggest enterprises in the world are betting on it (and I don't mean just google…

We did use in production. And it sucks to support it. Problems.. * Dynamic components wont work with Vue. Lists etc. * Loading individual html files for each component. Could not figure out how to bundle the components with Webpack. If you still want to use it, use it without Vue or React.

Well, people use them with angular 1/2 and aurelia so im quite sure it should work with vue/react.

I did bundle my components into single file - even throwing in sass compilation so I think the problem is elsewhere ;-)

Re: Element – A Vue 2.0-based component library for developers, designers and PMs

#149

Post by duval »

yesdocs wrote: post #105
brlewis wrote: post #12

Earlier quoted context omitted.

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.

This comment bears no resemblence to the experience of those of us running mithril in production
Post reply on HN