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

Add integration of raycast and wox #149

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

Zeqiang-Lai
Copy link

@Zeqiang-Lai Zeqiang-Lai commented May 14, 2022

Add integration of raycast and wox, so that we can use any screenshot app to capture latex image and pass it to latexOCR server via pix2tex.api.

BTW:
It seems that current pypi package doesn't include pix2tex.api due to the lack of __init__.py

Example usage of Raycast on macOS:

raycast

@Zeqiang-Lai Zeqiang-Lai changed the title Add __init__.py to include api into package Add integration of raycast and wox May 14, 2022
@lukas-blecher
Copy link
Owner

Hi, thanks for your contribution!

I'll look at it in more detail when I find the time. Right now I'm not sure what the added value is.
I'm guessing you are running the API on a remote server?
Not sure about supporting multiple solutions for the different operating systems. And what about linux?

@lukas-blecher lukas-blecher added the enhancement New feature or request label May 15, 2022
@Zeqiang-Lai
Copy link
Author

There is a cross-platform launcher that supports Linux, i.e., cerebro. We can write a plugin for it, so that we can achieve the same thing for Linux.

The main target users are those who have Raycast or Wox already installed, otherwise they could use the Python GUI directly without installing additional software.

The integration is suitable for those who:

  1. Fail to install QT dependency to launch Python GUI, like me.
  2. Don't want to mess up their environment with a lot of torch things.
  3. Have a powerful accessible GPU machine, but often use a laptop and want LatexOCR run faster.

Install all the dependencies on the use's macOS or Windows machine might be difficult and error-pruning. For my case, I have a GPU server that installed all the torch things, so I don't want to install them on my mac again.

Nevertheless, user can still run the API on their local machine, but they don't need to deal with QT things this time.

@lukas-blecher
Copy link
Owner

Ok, I like the idea.
Though, I'd prefer it if the API url is read from some settings file.

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

Successfully merging this pull request may close these issues.

2 participants