51–57 of 57 posts
Your company ( brimdata ) looks really good and your work on the Zed client app is impressive.
Thanks! We are prepping some blog content for after we get the next release out. You'll be seeing some more posts about zed on here soon.
Good efforts! Here's some quick feedback: My first thought - how React Arborist is different from Ant Tree? https://ant.design/components/tree/ React Arborist dependencies looks sane https://github.com/brimdata/react-arborist/blob/main/package... "memoize-one": "^6.0.0", "react-dnd": "^14.0.3", "react-dnd-html5-backend": "^14.0.1", "react-window": "^1.8.6" However I was never a fan of react-dnd. Extremely hard to rea…
Earlier quoted context omitted.
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.
Good efforts! Here's some quick feedback: My first thought - how React Arborist is different from Ant Tree? https://ant.design/components/tree/ React Arborist dependencies looks sane https://github.com/brimdata/react-arborist/blob/main/package... "memoize-one": "^6.0.0", "react-dnd": "^14.0.3", "react-dnd-html5-backend": "^14.0.1", "react-window": "^1.8.6" However I was never a fan of react-dnd. Extremely hard to rea…
I agree that the hard-coded DefaultCursor styles need to be configurable. I'll soon update. You'll be able to pass in your own component to render the DropCursor (blue line indicating the new position of the node you're dragging).
Does it miss Delete functionality for folders/files (I see rename) or I just dont see it?
I was thinking of making a generic tree manager class to provide basic functions (move, rename, add, delete) for managing the tree data structure in the parent component. Maybe I'll call it "Arborist"!
Great 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?
Great 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?
Looks like the start of a great component! It's amazing to me how there is not a really good tree component that already exists, considering how ubiquitous the tree is in user interfaces.