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

Blueprint – A React UI toolkit for the web

blueprintjs.com

Post reply on HN
Print view View original

111–120 of 214 posts

Re: Blueprint – A React UI toolkit for the web

#111

Post by crudbug »

ReactJS enlightened web developers with Component based functional/thinking/development model, which brought some order in front-end UI development. And it has been one of the best things with community behind it.

Having worked with both Desktop UI (Swing/GTK) and Server based UI toolkits (JSF), the value of ReactJS is a standard Component Life cycle.

I would propose having a ReactUI component specification with a standard version. The current specification [0] is not decoupled from implementation. The separate spec and implementation numbering will enable multiple implementations - ReactJS from Facebook being one.

I am thinking similar to Reactive-Streams [0] specification and Reactive Extensions [2] which have multiple implementations.

[0] https://facebook.github.io/react/docs/react-component.html

[1] http://www.reactive-streams.org

[2] https://github.com/ReactiveX

Re: Blueprint – A React UI toolkit for the web

#112

Post by AgentME »

renke1 wrote: post #35

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

I tried to do something like that with react-menu-list[0]. Its components come with minimal styling, and it's recommend for users to create wrapper components which pass some default props to add their own application's CSS classnames / styling.

[0] https://github.com/StreakYC/react-menu-list

Re: Blueprint – A React UI toolkit for the web

#114

Post by nine_k »

foo303 wrote: post #54

Not 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)

I used to think that games ate the forefront at the GUI, and mainstream will emulate their approaches.

I didn't think that the same is going to the machine performance requirements, though. I still hope the web,will remain usable without maxing out a dual GPU setup.

Re: Blueprint – A React UI toolkit for the web

#115

Post by kinkdr »

jasonkillian wrote: post #105
boubiyeah wrote: post #99

Earlier quoted context omitted.

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?

We're aware of this: https://github.com/palantir/blueprint/issues/39 Feel free to make a PR to improve things boubiyeah, we just haven't gotten to this issue yet.

> Feel free to make a PR to improve things boubiyeah

What kind of answer is this?

I don't think "boubiyeah" is working for you, nor has signed up for contributing to your project.

When you publish something to a public forum, even if you it is an open-source project, you open yourself to criticism(actually criticism is a great tool to help you improve your project), so my suggestion would be to be open and positive about the feedback, even if it is not all back-patting.

PS: You have done great work on the toolkit, thank you for making it open source.

Re: Blueprint – A React UI toolkit for the web

#116

Post by mlitwin »

mwww wrote: post #94
ethanbond wrote: post #44

Earlier quoted context omitted.

I'm a designer at Palantir (also write some code), and yes, it's used pretty much everywhere.

Could you please show us a few screenshots? Thanks!

You can see some designs here https://dribbble.com/palantir

Re: Blueprint – A React UI toolkit for the web

#118

Post by Fifer82 »

xliiv wrote: post #30
k__ wrote: post #13

I wish web based UI-toolkit creators would focus on WebComponents. They can easily be used as leaf-elements in almost any framework.

+1 for web components and Polymer https://beta.webcomponents.org/

A lot of people go on about Polymer, but no one actually uses it?

Re: Blueprint – A React UI toolkit for the web

#119

Post by colllectorof »

boubiyeah wrote: post #99
foo303 wrote: post #54

Not 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?

Oh, but it's an app, not a website. There is absolutely no way to display static documentation and a few widgets without 4MB of code. None. It's just impossible. Get along with the times, dude.

Re: Blueprint – A React UI toolkit for the web

#120

Post by adidahiya »

foo303 wrote: post #54

Not 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)

Hi folks, I'm one of the developers of this project -- we hear your perf concerns loud and clear and are tracking the issues :)

As mentioned elsewhere in this thread, this page was released a little too early while we were still playing around with animations in the header. I've gone ahead and disabled them for now, so you should see leaner CPU utilization now. Thanks for your comments.

Post reply on HN