ClayMemory VS react-pdf

I absolutely agree with the general sentiment. Last year, I wrote my Master Thesis on how to easier create cards from PDFs (my introduction is basically this post :D). It really is a joke that a software has access to the pdf but we need to extract text (manually) from it to study it. My approach was a bit more classical: I tried to integrate new creation tools with a PDF reader (My prototype: https://github.com/LuccaHellriegel/ClayMemory). There is one "deck"-equivalent per pdf-page, an automatic-copying mechanism and context-menu for easier card creation and an origin-system, that links the position of extraction with the new card. Still a prototype (I have a laundry list of possible imporvements), but the prototype and my user study showed that there is so much potential here in making creation easier.

23.react-pdf

23. react-pdf

There are actually two npm packages called "react-pdf": one is for displaying PDFs and one is for generating PDFs. Today we are focusing on the one to generate PDFs: https://github.com/wojtekmaj/react-pdf.

Not sure if that would work for youck, I used react-pdf to format the size and text required within the document before printing.

I am trying to load a PDF from my src/assets folder, following the example from here I have the following code:

Then I suddenly had an idea. Im sure React/client side has a JS library! And indeed, both react-pdf and a few satellite libraries had exactly what I needed.

Hmm, that's tricky. Maybe mocking the PDF return can help here: https://github.com/wojtekmaj/react-pdf/issues/564?

My project stick with IE, so I using [email protected], I find out the example for doing this codesandbox but it was been limited, by using 5.1 and upper.

I don't know.

For people who want a React wrappers around pdf.js, there are open source alternatives such as react-pdf: https://github.com/wojtekmaj/react-pdf