Yet Another PWA JNC Client

Tube

By the way, is there a way to prevent more than two columns on desktop screen sizes?

Screenshot of the reader, first pages of Another Step's first volume's first part

I can usually manage with a different window size, but it would be nice if there was a setting you could tick that would make it limit to two columns, no matter screen size. Extra points if the two columns used the extra screen real estate to be wider, but not even necessary. I'd rather have a maximum of two columns at once, even if they would be no wider than they are here with four.

Iseguy

@Tube They've said in the past that it's tuned so the pages have an A4 aspect ratio, which I'm sure works great for their screens. Personally, I would aim for a certain number of Em's per column so the number of columns goes down as the font size goes up and the words per line stays roughly constant.

Crimson Wise

It's the images in particular the problem. If I don't keep the aspect ratio they start clipping. And fixing that becomes a pain I hadn't have much interest to solve since doesn't apply much to me (I read from my phone/tablet, so it's usually a single column).

That said, I do have control on the number of columns so I have added a setting for that, although it will keep the aspect ratio. It's in the Reader settings once the app upgrades for you.

(And with this update the app goes from fully static to serverless since I needed to proxy image requests to work around CORS for caching...)

Iseguy

@Crimson-Wise said in Yet Another PWA JNC Client:

If I don't keep the aspect ratio they start clipping.

The trick is to explicitly set the CSS height of the .rr-image-wrapper to the height of the viewport. You would have to script it to update every time the layout changes, if that's possible in your framework of choice.

rr-image-wrapper

sorvani

Could you change part 1 to show part 1 of X for currently streaming series that have not released all parts? Or simply put it on part 1 of all series?

I can never recall without going to the series page how many parts a series is going to have, but I noticed that the part count is in the json data you show under the "info button"

    },
    "owned": true,
    "noEbook": false,
    "totalParts": 12

Crimson Wise

@sorvani tried at some point but I wasn't satisfied with how it fitted, so I ended up with the below.

I can never recall without going to the series page how many parts a series is going to have

I assume you're referring to the series page in the JNC's official website.

In my app you can find it in the Volume info panel: click in the three dots below the volume cover -> Information -> Parts.

sorvani

@Crimson-Wise said in Yet Another PWA JNC Client:

@sorvani tried at some point but I wasn't satisfied with how it fitted, so I ended up with the below.

I can never recall without going to the series page how many parts a series is going to have

I assume you're referring to the series page in the JNC's official website.

In my app you can find it in the Volume info panel: click in the three dots below the volume cover -> Information -> Parts.

Honestly I meant either. Your app does have easy ways to get there, no complaints about that. But seeing it once in the primary view would be great.

Crimson Wise

But seeing it once in the primary view would be great.

Yeah, I get the point. I do think the interface is a bit noisy though so I've been trying to avoid adding too much... that said,

Speaking of clutter, although unrelated and pretty much the reason for most of my updates this year, feature announcement: I have added offline support to the app. Anywhere you can read parts there is a fab button in the corner to enter what I call "download mode" - any parts selected will be then downloaded, and can be read from the new Offline tab even if there is no internet access.

Offline example

There are some restrictions though, up to 20 parts can be downloaded, and are removed after 2 weeks.

Finally, I'm calling the whole thing "experimental" since there are glitches here and there, in particular when it comes to keeping track of progress, that I'll be sorting out as I'm able.

Crimson Wise

Preemptively, in case the app is dead after the maintenance, I’ll look at it on the weekend.

pcj

@Crimson-Wise said in Yet Another PWA JNC Client:

Preemptively, in case the app is dead after the maintenance, I’ll look at it on the weekend.

And indeed it will be. I'm told on Discord that /app/v1 went away and you need to use /app/v2 now

Nitrousoxide

@Crimson-Wise said in Yet Another PWA JNC Client:

Preemptively, in case the app is dead after the maintenance, I’ll look at it on the weekend.

Now that the site's back up, I can confirm that it's, indeed, broken.

Looking forward to when you get a chance to update it!

Crimson Wise

First attempt:

APIs changed from an v1 endpoint to v2, but seem largely the same.
All resources have an id now, plus the old legacyId. Events no longer have an ID though.
Parts don't seem to have an expiration set in them, which I need. The website is showing it, so it has to be somewhere.
Future parts are also listed in the responses, even if they aren't yet live nor content available to read.
Thumbnails are now using a different endpoint, and no longer coming from Cloudfront, at least not directly. Images in the parts still do.
My domains are no longer allowed via CORS, unfortunately. I guess I can pass all requests through my proxy to work around it, as I already do that with Cloudfront images.
Progress percentages aren't available but we knew that already.

Will continue tomorrow.

sorvani

@Crimson-Wise said in Yet Another PWA JNC Client:

Future parts are also returned in the responses, even if they aren't yet live.

that's gotta be a big oops

Crimson Wise

@sorvani no content is returned for them to read, they are just listed which the old API didn't do.

sorvani

@Crimson-Wise said in Yet Another PWA JNC Client:

@sorvani no content is returned for them to read, they are just listed which the old API didn't do.

Ah, thanks for the clarification.

chocolatkey

@Crimson-Wise If you'd like, I can re-add the domain(s). Please confirm what they are.
Why do pass the imgs through a proxy though?

Crimson Wise

@chocolatkey Thanks! If you don't mind could you please add these two domains?

jnc-reader.wscr.dev
jnc-reader-dev.wscr.dev

As for the proxy, it's because I need to work around CORS for the Cloudfront images.

In general it isn't needed as the browser relaxes CORS rules for images and some other stuff, but if the image request goes through a Service Worker (which I need to support part downloads for offline reading) then I don't get that benefit, hence having a a simple Cloudflare Worker to proxy those requests.

sorvani

@Crimson-Wise Had any time to devote to this? I miss using your reader.

chocolatkey

@Crimson-Wise I've added them. The cloudfront images will slowly be disappearing, but are definitely still around at the mometn

Kyouri

Hope it's working again soon. This is the only way I read novels from here since I find the app too inconvenient to use. ^^;