Explain comic

[moshpirit]

trafficstars

Internal view of the explanation instead of a browser requirement.

[tom-anders]

It uses chrome custom tabs, which has some advantages over an internal solution.

[moshpirit]

Which ones? I only want to read the explanation text, that's all.

[tom-anders]

It supports preloading the explanations and is faster than Android's webview. Just displaying the explanation text would involve a lot of html-parsing and would probably be slower.

[moshpirit]

I think it worth it, it's way more comfortable having the explanation already in the same app. In fact, to me it seems like opening the browser and loading the website may require more time than just loading the text on the app, which could be also done in the background while we're reading the comic, stored in the cache and deleted when we close the app.

[tom-anders]

I'll do some testing when I have time.

[moshpirit]

Thanks a lot, peaceful and gentleman T-Rex.

[moshpirit]

I.e. what I'm asking is a pop-up for the explanation just like we have for transcription.

Again, thanks a lot!

[moshpirit]

Hello! I don't want to put you in a hurry but I'd like to know how is it going, did the tests go well? :-)

[PeterHindes]

If you could get someone from the NewPipeExtractor team interested they have plenty of experience with web parsing.

[FineFindus]

It should be possible to get the data via the MediaWiki API as JSON, but it's in a Markup language and needs to be parsed first. Sadly, I'm not experienced enough in Kotlin to implement it.