417KB minified :|
Has potential for optimization.
A React implementation of Spectrum, Adobe’s design system
21–30 of 74 posts
Re: A React implementation of Spectrum, Adobe’s design system
#22One of the things that I always find missing in these libraries/collections is a date/time picker. I know these are available via many separate projects, but it's nice if one picks a collection like that, that all inputs are homogeneous.
That's only an "issue" of all that "modern" stuff. Many, many years ago I've used Dojo[1] and it's component lib Dijit. It had all that complex widgets in the toolbox. With all the "advantage" stuff like ARIA and internalization. Or you could use Ext, if you could pay it. But than all this "modern 'component' stuff" came form nowhere and you've been back to stone age, where you didn't have even the most basic compone…
That’s how I feel about all of this Javascript stuff after coming from Rails. You mean I have to do [insert basically anything] all on my own, from scratch? But Rails gave me all of that out of the box!
Re: A React implementation of Spectrum, Adobe’s design system
#23One of the things that I always find missing in these libraries/collections is a date/time picker. I know these are available via many separate projects, but it's nice if one picks a collection like that, that all inputs are homogeneous.
Our date picker is in progress right now actually. Should be available relatively soon. Date pickers are one of the most complicated components, especially due to internationalization/accessibility requirements.
Will it have moment.js as dependency like react-dates?
Do you also plan to make a DateRangePicker and a TimePicker?
Re: A React implementation of Spectrum, Adobe’s design system
#24Earlier quoted context omitted.
Our date picker is in progress right now actually. Should be available relatively soon. Date pickers are one of the most complicated components, especially due to internationalization/accessibility requirements.
Will it have moment.js as dependency like react-dates? Do you also plan to make a DateRangePicker and a TimePicker?
No, moment is not a dependency. We're using the native Intl.DateTimeFormat APIs that are built into browsers now. This makes sure we support internationalization properly, but without the giant locale data needing to be downloaded.
And yes, we have a DateRangePicker and TimePicker as well.
Re: A React implementation of Spectrum, Adobe’s design system
#25hey everyone. I work on React Spectrum. Happy to answer any questions. :) I'd also point to our introductory post where we discuss the architecture. I think the most interesting thing is that you can reuse most of the behavior, accessibility, etc. without our design in your own component library using our hooks. https://react-spectrum.adobe.com/blog/introducing-react-spec...
Can you give a few sentences of why someone would want to use this?
Re: A React implementation of Spectrum, Adobe’s design system
#26hey everyone. I work on React Spectrum. Happy to answer any questions. :) I'd also point to our introductory post where we discuss the architecture. I think the most interesting thing is that you can reuse most of the behavior, accessibility, etc. without our design in your own component library using our hooks. https://react-spectrum.adobe.com/blog/introducing-react-spec...
Nice work. Questions: 1) What is the minified size of the library 2) Is there a kitchen sink app to review all features together?
Re: A React implementation of Spectrum, Adobe’s design system
#27hey everyone. I work on React Spectrum. Happy to answer any questions. :) I'd also point to our introductory post where we discuss the architecture. I think the most interesting thing is that you can reuse most of the behavior, accessibility, etc. without our design in your own component library using our hooks. https://react-spectrum.adobe.com/blog/introducing-react-spec...
Can you give a few sentences of why someone would want to use this?
I think it's more likely that people will want to use the React Aria and React Stately libraries that underpin this than React Spectrum itself, unless you're wanting to match the Adobe look and feel for some reason (e.g. plugin developers). React Aria and React Stately provide Hooks that give you a lot of the behavior, accessibility, internationalization, etc. features out of the box, but let you completely customize the styling and rendering in your own components. Here's an example I made of using the hooks with Tailwind CSS to build completely custom components with full accessibility in a very small amount of code: https://codesandbox.io/s/tailwind-react-aria-3ngmw.
Re: A React implementation of Spectrum, Adobe’s design system
#28Why is there never a simple screenshot of anything? I just wanted to see and example of what Spectrum usually looks like
Re: A React implementation of Spectrum, Adobe’s design system
#29Why is there never a simple screenshot of anything? I just wanted to see and example of what Spectrum usually looks like
[deleted]
Re: A React implementation of Spectrum, Adobe’s design system
#30hey everyone. I work on React Spectrum. Happy to answer any questions. :) I'd also point to our introductory post where we discuss the architecture. I think the most interesting thing is that you can reuse most of the behavior, accessibility, etc. without our design in your own component library using our hooks. https://react-spectrum.adobe.com/blog/introducing-react-spec...
Nice work. Questions: 1) What is the minified size of the library 2) Is there a kitchen sink app to review all features together?
1. Depends on how many components you use! Each component is a separate package, so you pay for only what you use. We also offer a monopackage containing all components, but it is fully tree shakeable so it should be equivalent to using the individual packages if you have a good build setup.
2. We're working on building some example apps, but for now, the docs are the best example. You can also try out the storybook that we use for development if you clone the repo locally.