This look exceptional ! It's full featured (datepicker, tree) and professional looking. It's also seems to by typescripted. But the slider needs work on touchscreen.
Blueprint – A React UI toolkit for the web
91–100 of 214 posts
Re: Blueprint – A React UI toolkit for the web
#92Earlier quoted context omitted.
Styling is still "unsolved" with react IMO. Inline styles feel wrong, CSS alone isn't encapsulated enough to work with components correctly, CSS modules are TOO encapsulated which makes global styles and themes a royal pain, and adding another layer ala SASS or LESS feels like more of a "patch" vs a real solution. And none of them really solve style inheritance in any way that I'd call elegant. I end up using SASS an…
React is supposed to be the "next big thing" and yet styling is still an unsolved problem. I'm amazed by the state of our tooling in front end web development.
I know it's fun to scoff at "those front end guys" and act like you know all the answers, but if you do know the "one true solution" to this please tell us.
It's "unsolved" in the sense that all the current solutions feel wrong (but work great), and if that's the biggest problem front-end development currently has, then it's in a pretty damn good place.
Re: Blueprint – A React UI toolkit for the web
#93Earlier quoted context omitted.
Styling is still "unsolved" with react IMO. Inline styles feel wrong, CSS alone isn't encapsulated enough to work with components correctly, CSS modules are TOO encapsulated which makes global styles and themes a royal pain, and adding another layer ala SASS or LESS feels like more of a "patch" vs a real solution. And none of them really solve style inheritance in any way that I'd call elegant. I end up using SASS an…
I saw this[1] recently by one of the guys from material-ui[2]. They're going to move to JSS. [1] https://github.com/oliviertassinari/a-journey-toward-better-... [2] http://www.material-ui.com/
I really like material-ui but am constantly bummed about their use of inline styles.
Each component has multiple style props, lest you resort to "div > div > div:nth-child(2)" in your own CSS.
Each "style" prop now has to be diffed by React too.
Doing things like hover on mouse/touch events seems like it will never be as efficient as using ":hover".
And when doing universal rendering, the amount of markup you send is huge. And you have to disable the browser-prefixing of style props.
Having said all that, the material-ui library is still great.
Re: Blueprint – A React UI toolkit for the web
#94Re: Blueprint – A React UI toolkit for the web
#95This is very slick. It's similar to my own project http://cx.codaxy.com/docs/widgets/date-fields , however, it seems that they went one step further.
Impressive work.
Re: Blueprint – A React UI toolkit for the web
#96Re: Blueprint – A React UI toolkit for the web
#97Re: Blueprint – A React UI toolkit for the web
#98This is very slick. It's similar to my own project http://cx.codaxy.com/docs/widgets/date-fields , however, it seems that they went one step further.
Impressive work. [0] http://cx.codaxy.com
Thanks. Here are a few more links for things implemented with Cx:
http://cx.codaxy.com/fiddle/?f=vwyHzOO1
http://cx.codaxy.com/starter/dashboards/sales
Re: Blueprint – A React UI toolkit for the web
#99Not to sound like a bummer here, but I'm not sure what kind of computer is needed to open this webpage. Simply scrolling up and down that website causes my computer to almost freeze. Firefox 49.0 user here. I would profile it, but I'm afraid of having to restart the computer as a result. Edit: It looks amazing. (Still the performance issue is reproducible easily)
And the doc has 4.2MB of minified javascript. Jesus christ.
Tooks 9 seconds to load the page.
All credibility gone. Why would I use components made by people who don't see performance problems?
Re: Blueprint – A React UI toolkit for the web
#100This looks really nice. However, what I really want for React is a style-agnostic component library that basically extends the regular set of HTML elements, but comes with no "visual" styling (other than really basic styling like the browser's default styling for , and the like). Only styling that is necessary for the component to function should be included. Of course, optional themes would be fine. Also, non-visual…
Styling is still "unsolved" with react IMO. Inline styles feel wrong, CSS alone isn't encapsulated enough to work with components correctly, CSS modules are TOO encapsulated which makes global styles and themes a royal pain, and adding another layer ala SASS or LESS feels like more of a "patch" vs a real solution. And none of them really solve style inheritance in any way that I'd call elegant. I end up using SASS an…
Yep... Settled for CSS modules for now; Works well enough.