Proxtop is an experimental attempt to create a desktop client for the popular german anime site proxer.me.
This is considered experimental because there's no official API in place so this app parses the site itself to provide the content. Thus, the application might be less responsive as expected or even unusable. Another problem with this route is that UI changes may break this application entirely.
(You can find more screenshots in the "screenshots" directory)
These goals are features/use cases that I want this app to provide to the user. All of them should be implemented until I consider this experiment 'done'.
- Use your existing proxer.me account
- View watchlist
- Watch proxer HD streams
- Update watchlist
- Watch streams with favorite video player (prefered: MPV)
- Get notifications on new watchlist releases
- Read & Write messages
- Have a somewhat nice looking UI
Goals that I would like to implement afterwards, if I have interest in continuing. These might never be included.
- Browse animes and search
- Add same functionalities for mangas
- Forum notifications
- Electron
- Angularjs
- It is not a complete frontend/replacement for proxer.me, it is just an alternative frontend for doing the most common tasks on the site, such as watching anime.
- It is so far not officially supported and thus just a community/personal effort.
You can find the latest packaged/stable releases under Releases in the repository. There you can download the right archive for your platform. Extract it and run the Proxtop executable inside the directory. I currently provide packaged releases for Windows (32bit + 64bit), OSX and Debian, while also providing a general Linux archive. Arch Linux users can find the PKGBUILD files at my pkbuild repo for both stable and latest versions.
To run this application from source you first need an API key from proxer. See the thread for details.
First get all required dependencies (requires NPM to be installed):
npm ci
Run tests via:
npm test
Run the application via:
PROXER_API_KEY=your_proxer_api_key npm run start
# Or
PROXER_API_KEY=your_proxer_api_key ./run.sh
Or if you want to build the application:
npm run clean
PROXER_API_KEY=your_proxer_api_key npm run dist
# And if you want to package it:
PROXER_API_KEY=your_proxer_api_key npm run build:windows
Proxtop is running inside Electron using TypeScript/JavaScript and is split in two halves: the "backend" and the "frontend". The backend is doing all the heavy lifting, e.g. doing API requests, caching data and checking for new releases. On the other hand, the frontend is mostly for displaying the information it receives from the backend and taking in user interaction, it shouldn't do many logic on its own.
These two communicate using the IPC provided by electron which is essentially events with a JSON payload.
The source is split accordingly, under src/main is the backend and under src/renderer is the frontend code.
As with this split, the application also needs to be debugged separately. The frontend can be debugged by pressing Ctrl+Shift+I while the app is
running to bring up Chrome Dev Tools which allows for client side debugging. While this is straight forward, it has one downside: Making a change
in the code requires you yo restart the application. Since this is not ideal, you can instead start the application in the following way. This
requires two consoles/shells as it requires two commands to be running concurrently.
In the first shell, run the following:
npm run webpack
Then in the second shell, you need to run this:
npm run debug
The first command starts webpack and tell it to watch for changes. Any time you now change a file, you can just reload the app (Ctrl+R) to reload
the changes. Sadly, the backend doesn't support that, so for backend changes an app restart is still necessary.
Additionally to webpack watching for files, the second command instructs electron to open a debug port at 5858 which can be used by your
IDE/editor to attach and debug the backend process. Once you're attached you can set breakpoints and debug along.
This seems like a hard and terrible way to do it!
You might say that and you wouldn't be wrong. However, until the API is out, which might take forever, I still want something like this app to exist and that I can use. Even if it will end up in a state where only myself could use it, as long as it is there. Also, I've done some small parts this way in the past and those still work, so I don't really have a problem doing it this way.
Why do you need an app on desktop if you have the browser?
This is a reasonable question, so let me tell you this:
- In the browser the page is fixed, meaning the layout, menu and style are not really modifiable by me. If I don't like the style or if I want to make certain workflows faster, how would I do that? I don't want to end up with millions of lines of injected js code to change the site and get totally thrown off once the design changes. I'll probably end up with the same thing here, but in a separate app it's far easier to manage than a hacky script that ends up getting injected.
- I cannot easily embed the content of the web page into other things, like a video player. There's no nice way for example to open the video in my local media player. Why would I want this? Better video controls, less memory footprint (some of the player are just ... ugh, shitty. Do you remember flash?) and brings more flexibility.
- I can easily add new functionality without, again, fiddling with content scripts or maybe even doing things totally different.
TL;DR: Convenience, because I like to do things differently.
Doesn't this hurt the page creators?!
Page load: Page load is a concern, as this is a hobby website and thus only limited resources are available. However, this is not really a concern as this app does similar/identical requests to the page as if a user would do the same steps. However, with convenience features like watchlist notification, this might be less true, as it has to check in the background if new ones are available which would cause more page loads to happen. I do believe however this is no big concern as by default these requests do not happen often.
Advertisements: There are three cases
- You donate to the creators already, which results in no ads on the site, thus no difference.
- You have an adblocker installed so you there's no difference either.
- You have no adblocker installed and would normally see ads. This is the only case ad revenue would be missed.
I hate ads myself, so I don't see this app getting ads to increase revenue for the creators being a thing. Just donate; makes everyone happier.
This application is licensed under the MIT license. See the LICENSE file in this repository for more information.
The Proxtop Logo is licensed under the Creative Commons BY-NC-SA 4.0. You can find more details and the full license text at http://creativecommons.org/licenses/by-nc-sa/4.0/ .