31–40 of 88 posts
Looks clean and works fine, but it needs optimization. Clicking "Type" in the "schema builder" example takes 1~2 seconds to open the popover in the landing page(macbook pro m4). I think its because there are lots of heavy components, but still it's too slow.
the root page is a bit slow with all the viewers, in practice you probably wont have that many in your app on one page
How does it compare to https://news.ycombinator.com/item?id=48436863 ?
you are welcome to try it with your own documents and see, but its just one example we wanted to show. for the blocks that use the react-docx library, you can always copy the code and use a different method to render the docx file/thumbnails
Is this a known issue?
Earlier quoted context omitted.
we'll try to make it more clear on the landing/introduction page!
_Try_ to? Are you serious? We're not taking ambiguity due to phrasing, we're talking straight up not mentioning it on either the front page, on the show all page or even on the page the components button takes you to. Not even on this forum thread. There's barely any text on the front page to change and there are even multiple places you can mention React. You could mention it in the title, e.g. "Open source _React_…
These should really be web components. Leaving out every framework other than React is really bad for the web.
How is your PDF coverage? They are notoriously difficult things to render, with endless edge cases. Mozilla’s PSD.js is the status quo here, so what do you do better than them?
We aren’t not trying to reinvent that engine, rather just provide a building block for people to plug in their design system to its controls