I thought it was going to be a sortable tree-table like MacOS 8. I saw a tree like this in Java Applets in 1994.
[deleted]
React Arborist – A full-featured tree component for React
41–50 of 57 posts
Re: React Arborist – A full-featured tree component for React
#42This is a great survey of the many ways trees can be used in UX: https://medium.com/@hagan.rivers/interaction-design-for-tree... My favorite is the Tree Table
FWIW I am working on such a table library for React [0] which has a great tree plug-in. So you can use it either as tree table or tree list (if just having one column).
Re: React Arborist – A full-featured tree component for React
#43Does it miss Delete functionality for folders/files (I see rename) or I just dont see it?
Re: React Arborist – A full-featured tree component for React
#44Earlier quoted context omitted.
The significant majority of accessibility issues found by those sorts of large-range studies are comparatively minor, and often completely spurious. I have been decidedly unimpressed with every such study that I have delved into the results of. (I know you’re arguing against someone claiming 100% accessibility coverage as a requirement, but I wanted to point out that figures like 98.8% are grossly inflated and quite…
Those minor or spurious issues may well disable a disabled person even more. That said, the entire accessibility scene is fundamentally broken on the technical side and full of snake oil salesmen on the business side. Anxiously waiting for WCAG to finish an actual standard, and for vendors to actually implement it.
I’m well familiar with the issues of accessibility, and I use the words “minor” and “spurious” deliberately. Most especially, when I say “spurious”, I mean false positives.
Re: React Arborist – A full-featured tree component for React
#45Great component, thank you for sharing. I was working on a similar component called `react-monaco-tree`, which is waay immature right now. I took `https://github.com/BlueMagnificent/monaco-tree` as the base. Are there any list of all these 'file-tree' components for React?
Re: React Arborist – A full-featured tree component for React
#46Earlier quoted context omitted.
no need to apologize, I forget it all the time. Rather, I should thank you for making it MIT. Now I can use it if I want to create an electron app with react that can deal with the file system very good.
You're welcome. I created it for an electron app myself. I needed a sidebar like you see in VSCode.
Have you seen https://github.com/BlueMagnificent/monaco-tree?
Re: React Arborist – A full-featured tree component for React
#47Earlier quoted context omitted.
Those minor or spurious issues may well disable a disabled person even more. That said, the entire accessibility scene is fundamentally broken on the technical side and full of snake oil salesmen on the business side. Anxiously waiting for WCAG to finish an actual standard, and for vendors to actually implement it.
I’m well familiar with the issues of accessibility, and I use the words “minor” and “spurious” deliberately. Most especially, when I say “spurious”, I mean false positives.
I have yet to see a false positive. It might appear that way to someone only testing on a single platform, a single browser and a single reader, macOS + Chrome + VoiceOver for some reason being the usual combo even though VO doesn’t work right with Chrome.
Typically devs will also ignore reader shortcuts and instead use tab navigation, which is not how screen reader users do things because it bypasses screen reader navigation altogether.
Do you know for a fact that the ”false” positives weren’t actual problems for someone using NVDA or JAWS shortcuts to navigate on Firefox on Windows, or some other combination of reader + navigation + browser + OS?
Everything is broken and nobody can test or fix everything.
Re: React Arborist – A full-featured tree component for React
#48[deleted]
Re: React Arborist – A full-featured tree component for React
#49Earlier quoted context omitted.
> without 100% accessibility coverage If that's the standard for open-source projects, it's a wonder any FE components get used
It is a legal requirement to provide equal access to all features and information for people who use accessibility features. Any non-trivial deviation from this must be declared in an accessibility statement, or the site owner risks legal action and large fines. 100% is not hyperbole, even though ”not exist” is.
As someone who has led WCAG remediation projects, I can firmly assure that it is hyperbole.
100% “accessible” is meaningless: full adherence to what standard? 2.1 AA? That’s an incredibly high bar, and would require constant vigilance and expensive audits on a rotating basis. Much of the guidelines are up for interpretation and can’t easily be expressed in a binary pass/fail besides.
Re: React Arborist – A full-featured tree component for React
#50There's a lack of performant, beautiful, extensible packages to visualize large JSON trees. It'd be nice to see a demo of that.
I totally agree. Firefox's default JSON viewer (an example[0] if u wanna try it with Firefox) is one of the most well-done tools I've come across at solving JSON trees. I wish I could get this as a component to play with in web design [0] https://old.reddit.com/r/zerowaste.json
I tracked down the source of Firefox Devtools' JSON viewer.
https://github.com/mozilla/gecko-dev/tree/master/devtools/cl...
It's based on React, but also uses require.js for its dependencies from other parts of Devtools, like TreeView - so it looks tough to separate into an independent component.