A new *unofficial* reader application for j-novel.club (**now also for Android**)
-
@_08 Thanks for the feedback, I think most of those should be easily fixable (or an option, like how many pages to progress on two page view) once I have some time to work on it.
Out of curiosity, did you use the Windows binary or build it from source?
-
@jaquobus Binaries on Win7.
Sometimes on startup process takes ~5M of RAM, does seemingly nothing for a few minutes and starts normally afterwards.
Some more issues:- /updateReadCompletion is posted even if you aren't logged in
- One of the most frequent actions during reading would be page flipping so you'd want to make that one to be comfortable to use. Right now it can only be done with small on-screen buttons and left/right arrows (and latter doesn't even work at first). At the very least you should add other obvious keys like up, down, pgUp, pgDn, space and that leads to another bug...
- Go to serie->volume->part, hit space repeatedly. Among other things, computational complexity seems to rise each time.
- Navigating between parts in the reader can also take you to an unavailable part.
- Wide images get cropped (most notably in Ragnarok Part1 and Rokujouma V5P3).
-
@_08 Thanks again for the valuable bug reports/feature requests.
By the way, I've enabled BitBucket's issue tracker feature (https://bitbucket.org/fkosmale/jnovel/issues), so anyone who stumbles upon a bug, please use that one in the future. It allows anonymous reports, no need for anyone to create yet another account.
-
News: Now available for Android (see top post for details).
You can't spell Keikaku without Kei – Vote for Sagrada Reset!
-
@jaquobus Looking pretty good, a little unresponsive but easier to read on than than the official app.
-
@sniper_samurai
Thanks for the feedback, and glad that you like the reading experience. About the unresponsiveness: Could you share how much RAM your device has? And is only the actual part reader somewhat unresponsive, or also the menu navigation? -
@jaquobus My device has 6GB of ram. Reading is fine, it's menu navigation. I'm finding I need to press a title a couple of times before getting access to the parts from series overview. Latest release also takes a couple of presses unless you use the open part button.
You might also need to have android hide software buttons on the reader or adjust the reader side if software buttons are present. This one is really just cosmetic and doesn't detract from the reading experience.
-
@jaquobus Good Job!
I know it's for tablets but I installed in my smartphone (Xiaomi Redmi Note 4) and some issues:
- Blurry cover images.
- The "smooth animation" is very slow.
-
@zchronos Huh, I thought the covers were too small for anyone to notice that they are blurred – so much for that. Basically I'm using a faster, but blurry resize. I guess I should just use the "good" resize.
For the animation: is only the menu transition animation slow, or also the part reader? If it's the former, your and sniper_samurai's comment probably indicate that I block the UI thread somewhere.
You can't spell Keikaku without Kei – Vote for Sagrada Reset!
-
For the android version, can I run it from external memory as well as download books to external/sdchip memory? This’d be a huge “selling” point for me...
Ugh, I’ve only got like 500-1100 mb free...
iOS version when????
, -
@thomask Uhm, technically it would be easy (well, relatively) for me to add a "temporarily download part for offline reading" functionality. However, this would definitely require an ACK from @Sam-Pinansky, as this is something which is currently not officially supported.
The issue with iOS is that I have neither a Mac to build the app, nor some iDevice to test it. In theory, it should be pretty easy to port though for someone who has those.
-
The cover image can be a little bigger? Would be enough if it were the same size as the Official App.
For the animation, in the "reader" the effect when moving to the other page is slow (I think it's the duration of the effect).
If you want to skip several pages it takes a lot time. -
@jaquobus said in A new *unofficial* reader application for j-novel.club (**now also for Android**):
@zchronos Huh, I thought the covers were too small for anyone to notice that they are blurred – so much for that. Basically I'm using a faster, but blurry resize. I guess I should just use the "good" resize.
As someone who thinks that you better use larger version of thumbnails on HDPI devices I believe you're doing it wrong.
For the animation: is only the menu transition animation slow, or also the part reader?
Everything is, I would say? In the menu going to "Latest Releases" is done at much lower fps than everything else. The reader seems to suffer from all 3 possible problems: high input delay (even pressing a button is slow), low fps, low animation speed. First two may be tricky to fix, but you should make flipping animation speed faster at least. It sometimes also lag for about a second when page is few dozens of pixels away from destination.
Some or all of problems above may or may not be a consequence of having to render on a 2560x1600 screen.Going "Last Releases"->Part->back to "Last Releases" keeps populating the list with duplicate "first page" parts (and second page won't ever be get then).
Edit: You should use cloudfront for images now.
The download functionality is not implemented yet.
Since it's apparently is something you will get into: you can request /api/users/id/ownedBooks?filter={"fields":["id":true]} instead of requesting the whole volume's data like web app does. Took me a while to realize that.never mind, I thought you had that download button on a general volume page. -
@jaquobus said in A new *unofficial* reader application for j-novel.club (**now also for Android**):
@thomask Uhm, technically it would be easy (well, relatively) for me to add a "temporarily download part for offline reading" functionality. However, this would definitely require an ACK from @Sam-Pinansky, as this is something which is currently not officially supported.
The issue with iOS is that I have neither a Mac to build the app, nor some iDevice to test it. In theory, it should be pretty easy to port though for someone who has those.
Hmm... I’m gonna look into it. I have a iPad, and an app that at least let’s me “test” locally on it. That said, I don’t have a Mac for testing or coding. Neither do I have the developer accounton apples store...
It might be worth it tho... at $99 a pop per year it becomes expensive.As for the download function, I can understand. I notice however that when I’m not on wifi, the amount of data used whe “pagination” is occurring isn’t far off of what I use when I download a manga using manga rock or alternative.
And that happens “every pagination”, especially if you need to switch between apps and it’s unable to “save state”.
I’ll look into trying to run it at least once on the iPad for feedback purposes.
-
As someone who thinks that you better use larger version of thumbnails on HDPI devices I believe you're doing it wrong
It clearly shows that it was initially developed for a low DPI Linux desktop ;-)
high input delay (even pressing a button is slow), low fps, low animation speed.
Hm, the last one is of course easy to fix, and also @zchronos mentioned that it is too slow. Low fps is probably caused by your screen size, that won't be that easy to fix. High input delay means I'm doing something wrong, I'm just not sure what exactly.
And thanks for the hint about cloudflare, I totally missed that the images are nowadays hosted there - whoa, they load significantly faster now!
-
@jaquobus said in A new *unofficial* reader application for j-novel.club (**now also for Android**):
And thanks for the hint about cloudflare, I totally missed that the images are nowadays hosted there - whoa, they load significantly faster now!
Fun fact: I'm pretty far away from S3, but
cloudflarecloudfront hates me and works even slower sometimes.Forgot to mention: dark mode should have darker background (not #444444 or whatever android has by default) unless I really misunderstand it's intention. Though that won't be very useful if controls stay white.
Screen may flicker at startup because it goes white -> dark for a fraction of second (if it's default on the device) -> white interface again. That's pretty annoying.It clearly shows that it was initially developed for a low DPI Linux desktop ;-)
Inserts are upscaled with freaking nearest neighbor. Don't do that.
-
So, I've released a new version, 0.2.0 for Android. It
- ensures that insert images are rendered correctly on High-DPI displays,
- changes the list behaviour on smartphones: single tapping now opens an entry; tablets (or large phones) still use the double tapping behaviour, so you can view the additional info before opening a series/volume,
- sacrifices app startup time to load all screens initially, which should make switching between them smoother,
- has shorter animations, which is probably good for snappines,
- hides the menu bar on Android in the part reader,
- uses the CloudFlare URL, so images probably load faster,
- is less racy when fetching more latest released parts,
- uses larger images by default in the menu, and uses a better looking scaling method
Initial part loading is still much slower that I'd like, and the same holds for jumping multiple pages forwards/backwards. I try to solve this at some point, however it's fast enough™ for me on my tablet, so my motivation for doing so is not too high, and neither is the time I have available for further development in the near future. For anyone who still likes to try it – enjoy!
-
Oh well, with all the new novels out there to read, I thought I might as well release a new version of the app, too. It mostly fixes two stupid things:
- It doesn't re-render the whole part when changing a page, but only the pages which will be displayed
- Put the HTTP cache in the cache directory on Android
-
@Jaquobus Being a big Qt fan that never had the time to get into QML/Quick, I finally had time to play around with your code. The renderer is somewhat buggy, but nothing that couldn't be improved with some work. Was playing around with themes, icons etc. and also added a blur effect when the reader is busy repaginating.
Going to try and add vertical mode in
-
@chocolatkey Have fun. I currently lack the time to develop features myself, but I can still answer questions, or merge features. The icons do look nice.
