201–210 of 214 posts
One question: I couldn't find advanced form components, and specifically dropdown/multiselects. (a bit like this: https://selectize.github.io/selectize.js/, or this: http://wenzhixin.net.cn/p/multiple-select/docs/#the-basics1)
Do you plan to implement this kind of components?
Is this page written in Blueprint? It makes my Firefox consume 100% CPU.
I see a few comments bringing up mobile. There's already many mobile-friendly UI frameworks; not everything has to be mobile-first. Yes, in many cases it makes sense to go for a mobile-first approach, especially with consumer-facing applications. Mobile is huge and apparently it's still continuing to grow. At the same time, there's many legitimate cases in which you want to optimize for desktop. For example: consider…
For internal projects/webpages (similar to Google Data Studio as mentioned), where you would expect the user to only be using it on a desktop, having no mobile support is fine. But for external projects/webpages in 2016, where atleast 1/3 of usage can come from mobile devices, having a lack of mobile support is a complete, 100% nonstarter. And there are plenty of competing React UI frameworks with mobile support alre…
Citation needed.
In all honesty though, good quality UI frameworks with good mobile support are on the top of my "#want" list.
Ah, memories. http://blueprintcss.org/
Earlier quoted context omitted.
I know everyone has their own favorite method, but one that I'm extremely satisfied with is using webpack > sass-loader > extract-text[1] to `include Styles from './MyComponent.scss'` in each component file, and then it all gets bundled up into a single css file per target (also great for eliminating dead CSS!). I use "layouts" at the root of my react hierarchy (under stores and routers and whatnot) and put my global…
I've done the same thing. An issue I run into is it's easy to end up with lots of the same media query littered over the place, which can harm performance and feels quite messy.
Earlier quoted context omitted.
I still can't imagine tying yourself to a system that precludes mobile. That seems like a terribly bad idea at this point.
For certain applications, you're right that's an awful idea. For others, it's an equally bad idea to limit your toolbox based on an irrelevant criterion.
Earlier quoted context omitted.
That might be so, but the rest of the world cares deeply about mobile, even to the point of caring about mobile first. You should get onboard.
Maybe you should realize not all software are made to be used on 5inch devices, considering Palantir's tools, data exploration and other data intensive sites, it does not make sense to focus on mobile, because your target audience will not use them. Instead of me getting onboard, you should realize generalizing all use cases would not work in real life.
1). Mobile is not just about 5" devices. It's also about tablets, and even about working well on larger iOS devices like the iPad Pro 12.9".
2). Data tools can be fantastically useful on mobile when adapted to make best use of the form factor. Lots of the data exploration/analysis tools out there have nice solutions.
3). Your target audience would use them. I'll bet you money it would take less than a day to sketch a few mobile scenarios, based on your own software, that a focus group of your users would rate as "very useful".
Earlier quoted context omitted.
For internal projects/webpages (similar to Google Data Studio as mentioned), where you would expect the user to only be using it on a desktop, having no mobile support is fine. But for external projects/webpages in 2016, where atleast 1/3 of usage can come from mobile devices, having a lack of mobile support is a complete, 100% nonstarter. And there are plenty of competing React UI frameworks with mobile support alre…
> And there are plenty of competing React UI frameworks with mobile support already. Citation needed. In all honesty though, good quality UI frameworks with good mobile support are on the top of my "#want" list.