WxRead WebAutoReader
1.3.0正式版发布
Use Weidu automatic reader to help you free up your productivity (hands) , do whatever you need to do, and still get the book coins!
It has been a year and a half since the last update, during which time I received a lot of feedback, messages and reminders. The new version is under development, please wait for the good news. I think it will not be a problem to release a new official version in the next month. Now, for the convenience of sorting, let me summarize a few questions based on the feedback collected so far:
Serious: Most users have reported the probabilistic failure problem of automatic reading, but I hung up for a long time and found that the number of recurrences was very low.
General: Many people don’t read the instructions on the home page and come to ask how to use it?
Another one that has been mentioned a lot: Some netizens are still using the first version launched from the bookmarks bar. They hope that I will continue to maintain it. I can only say that it is better to give up. There are too many restrictions. To solve these problems, I still want to use it from the bookmarks bar. The way the bookmarks bar is launched is unrealistic
Not considered: Only one person proposed to add the Text2Speech function. To put it bluntly, it is to listen to books. I found that the official has launched this function. Please bind a shortcut key.
Repeatedly:
Next, let’s talk about the current plans for the new version:
We gave up using Electron.js as a Webview shell because we just built a WeChat reading webpage. Using Electron.js is overkill and the most important thing is that the generated package is too big.
According to the plan, the new solution will use PyQt5 as the underlying support. The project has been launched and is in the technical verification stage.
The current thorny issue is that the interaction strategy between Python and JS in PyQt5 is poor. Consider using WebSocket for communication between the two parties. Friends who have experience in QWebEngineView can share their experience.
Finally, development is not easy. You guys can reward me with a little bit of silver and order a takeaway and a meal~
Thank you ❤️❤️❤️ Everyone is welcome to use your little hands and continue to leave messages and discuss!
＞Many of the traces behind me are pits that I have stepped on. The wheels will just keep building. Fortunately, I left this dividing line.
df982khrMethod one:
Drag the link to the bookmarks bar and click here to get it.
Method two:
微信读书自动阅读器, and change the URL to javascript:步骤2的复制内容;微信读书自动阅读器in the bookmark bar, start the reading program, and hang up;2020.02.17
2020.02.18
2020.02.22
2020.03.27
2020.05.07
2020.08.04
A new Windows client has been added. The new version uses Electron technology to fully upgrade the Weidu reader. Now you can use Weidu to do:
This is my first time using Electron to make PC software. I hope you can give me some feedback and suggestions.
2020.08.05
2020.08.07
My balls hurt!
Of course not!
In fact, it was because I saw the existence of a 132-hour bug in the WeChat Reading Week reading rankings, and then I checked on the Internet and found that someone on Zhihu asked this question. After verifying it, I answered it easily. You can check it out at See my answer here: How is WeChat reading time calculated?
The main reason is that the current hang-up method is too cumbersome, so I wrote this program.
Why do I say that the current method is inadequate? Let me introduce to you how to implement it: download an Android emulator, install WeChat Reading in the emulator, establish a communication bridge between the emulator and Python script through ADB, open WeChat Reading and select a book, and run the Python script , and finally the script realizes micro-reading UI automation to achieve the purpose of simulating robot reading, that is, hanging up.
This doesn't seem like a problem at first glance, right? But no. In fact, first of all it involves a lot of concepts:
These steps are too cumbersome and complicated for ordinary users, and they may even fall into ** if they don't pay attention. I clearly followed the instructions for use, so why doesn't it work? ** Honey dilemma, I believe that only programmers and a very small number of enthusiasts can toss these things.
And there are many restrictions, for example: ADB needs to be connected for debugging, Python needs to install dependencies, the simulator needs to set a long screen time, and it will pause after reading a book, and the user has no idea when it will pause. , and the deployment of different PC platforms is slightly different, etc. Many of these things are simply what developers do. You can't leave the developed things to the end users!
So the above problems can all be attributed to one point: due to the difficulty of deployment, its audience scope must be very small . This is its biggest failure, and it is also the fundamental reason why I personally feel that it will not enter the public eye. It is also an inevitable result.
In view of this, I changed another idea to implement it, which is actually a bit of a coincidence, and WeChat Reading just happened to launch the WeChat Reading web version, and the effective time is also calculated! Then, the deployment difficulties mentioned above have been perfectly solved or avoided from now on, because from now on we only need a PC browser!
The next and only problem is how to simulate the user reading to achieve the purpose of hanging up. First of all, it is natural to analyze how the reading habits of the WeChat Reading web version are designed, so that we can arrange how to do the program. I will not go into details about the analysis process here, but directly post the results: the web version is the same as the APP version, and the book is divided into chapters. Yes, turning pages in the APP version will automatically jump to the next chapter. In the web version, there is a下一章chapter button between each chapter. The user must click on下一章to jump;下一章will not appear after reading the book. .
Now that we understand the mechanism of the Weidu web version, it’s JavaScript’s turn to come on the scene. Now we have to use JavaScript to implement:
The principle is very simple and the code is not complicated. The only problem I encountered is: I first used setInterval as a timer. After putting it in the background for a long time, I found that the frequency was wrong. Sometimes it was fast and sometimes it was slow. I searched for the reason. The solution to the browser's power consumption protection mechanism is to use Web Worker, so I implemented it again using Web Worker, and the test was normal. I won’t go into the detailed implementation process. You can just follow the instructions and use it directly. Now we only need 3 steps to easily connect (touch) the machine (fish) while working:
微信读书自动阅读器to start automatic reading;PS: Actually, I also learned how to write Chrome extensions overnight, and then as long as I open the Weidu web version and click on any book, the reading program will automatically start. I originally wanted to send it to the Chrome store, but it cost $ to publish the extension in Chrome. , and I am so lazy that I often get frustrated. If you are willing to contribute a little bit, please scan the QR code below, I will be very grateful.
This repository only provides code, and all responsibilities are borne by the user.
