It's not as interesting if you make them to be a drop-in as the main UI of a client. I tried to port Amethyst's components from a Phone to a Tablet and even that little difference made the ready-made components not that great to be used. It was easier to just redesign/recode them. I can only imagine how off it would look when you consider mouse vs touch UIs.

However, It could be interesting if it had a simpler goal. Users will mention an nevent inside a kind 1 note all the time. That nevent can be anything, any event type. Because of that, there is a strong need to render any event kind inside the kind1 note. And that could be a very powerful base UI library that devs would use before they develop their own custom components.

Reply to this note

Please Login to reply.

Discussion

💯💯💯💯💯

This composability is 90% of the reason behind me writing this component library. My aim is for this library to be able to render all renderable event kinds because of exactly what you mention here.

🤝🤝🤝🤝🤝🤝🤝🤝

Thank you sirs!

That's the insight my brain needed to put the puzzle together.

Seems like a convenient library for something like njump to use then?

Exactly. Thats the goal