jameskerr

The text plugin alone seems like it could be a whole standalone product. Offline first seems to be getting more and more interest. Pretty cool. Dropbox + git for non-tech users. I dig that idea.

A funny title and concept: "branded javascript objects". But looks like a pretty handy JS library.

I have a Hugo blog and I wish the experience for writing on my phone was better. I need a git client and a markdown editor to publish. Not streamlined, but it’s free.

I agree that it would make sense for substack to provide a good way to write from your phone.

I love anything that gets me off Google products. I’m using plausible analytics now too. This looks cool!

Thank you. This is helpful.

https://zed.brimdata.io

Reinventing data storage

Fully typed, no schemas.

I think it’s easy to change a few duplicated instances. It just depends on how often they change. Once a year? Easy. Once a week? Not fun.

Convincing. Maybe I’ll try it for a while. Any tools you prefer or is it built in to the browser?

Classic

Wow, brutal! “And all the stones carried by one horse, Bassey.”

All Ive ever wanted was to convert mp4 to gif.

Giant turbines out in the ocean with regular gales and storms. That must be a massive challenge to construct.

Yes, you're right. I will update.

To simply share some JavaScript you've got to consider JS runtimes, module formats, and package.json interpretations. Was it easier when cross-browser compatibility was the big headache?

Features

  Drag and drop sorting
  Open/close folders
  Inline renaming
  Virtualized rendering
  Custom styling

  Keyboard navigation
  Aria attributes
  Tree filtering
  Selection synchronization
  More callbacks (onScroll, onActivate, onSelect)
  Controlled or uncontrolled trees

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.

This is a controlled component, so all mutation of the tree data structure will need to happen in the tree's parent component. Add a function in your node renderer (maybe after clicking a trash icon), that deletes the node from the tree state. The component will re-renderer and your node will be gone.

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"!

Ant tree looks like a great tree library and is certainly more mature than react-arborist. However, react-arborist supports renaming a node, has a slightly different drag and drop feel, and leaves all styling up to the user. Not just the title, icon, and expand buttons.

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

The library I used for virtualization does this. https://react-window.vercel.app I just followed Brian's pattern. I think it looks nice.

I agree. If you want things to perform on the web, you've got to virtualize the rows. Many web libraries don't.

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.

I felt this same pain and it was one of main motivations to make this library.

Dang it, I can see how the title was deceptive. This is headless component, leaving the markup and styling completely up to the user. Many of the tree components I looked at before building this didn't let me do exactly what I wanted with the style like this one does. However, I was thinking of shipping a default "<Item>" component that comes with some default styling to get people up and running quickly. I've just made an issue for this.

Thank you for bringing this up. It's I who apologize for being ignorant of these expected keyboard interactions. I'll make an issue in the repo to address this.

You're welcome. I created it for an electron app myself. I needed a sidebar like you see in VSCode.

Oh sorry, it is MIT. I'll update the repo.

Yeah, this is not quite the tree-table component. Unless your table only needs one or two columns!

This has been great feedback. To summarize, I heard people use inheritance because its the API of a chosen framework and in rare cases when it proves convenient like UI Elements.

I also remembered that unit test suites are an instance when I've enjoyed inheritance.

But it sounds like most people here do not use inheritance in the business logic of their apps/systems. Composition and dependency injection do the job of sharing code without sacrificing comprehensibility.

Thanks everyone! This all matches my experience as well. I just wanted to make sure I wasn't missing something life-changing!

Location: Orange County, CA

Remote: Preferred

Willing to relocate: Yes

Technologies: Ruby, Rails, AngularJS, PostgreSQL

Resume: https://drive.google.com/file/d/0B3auQ5JSPucmYTM3aVdmRFRpSTg...

email: jkerr838@gmail.com