Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upload via the USB Web API instead of using rmapi #142

Open
wittmeis opened this issue Aug 2, 2023 · 3 comments
Open

Upload via the USB Web API instead of using rmapi #142

wittmeis opened this issue Aug 2, 2023 · 3 comments

Comments

@wittmeis
Copy link

wittmeis commented Aug 2, 2023

Hi, very nice project!!!

I also use the RM2 a lot for reading and annotating scientific papers and since I do not want to use the subscription or the RM cloud I was so far uploading the PDFs to the RM using the USB web interface. However, that involves a lot of manual steps (downloading of the paper, resizing using ghostscript, etc.) that you automated already.

Hence, I was wondering whether you could consider to also support an upload of the paper using the USB web API protocol instead of rmapi. There is already a Python library for downloading files from the RM2 using the USB web API here and I already created another issue in the rmWebUiTools repo and asked whether the API could be extended to support the uploading of documents. If this would be added I could maybe contribute a PR that extends paper2remarkable and lets the user choose between rmapi and rmWebUiTools.

What do you think?

@GjjvdBurg
Copy link
Owner

Hi @wittmeis, thanks for opening this issue! I think that's a worthwhile addition to the project. I don't have too much time to commit to this package, but if you open a PR with the functionality (or even to discuss it while developing), I will certainly take a look!

@sachiniyer
Copy link
Contributor

I've tried to write support for this issue in #155.

I though it would be better to avoid the dependency on the package mentioned, as development was looking a little slow.

@sachiniyer
Copy link
Contributor

#155 is now merged, so maybe this issue can be closed now @GjjvdBurg or @wittmeis

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants