pontifechs / yamr Goto Github PK

Have the app track where you are in a series, so that you can easily come back to it. Not sure the best UX way of resuming your reading vs. going to the chapter list. I believe Mango can only do this from the favorites screen, but I'd like to at least entertain the idea of keeping track of it for all series.

What it says on the tin. Currently it gets put at the top, and looks a little odd.

What it says on the tin. Probably just needs to be a service that FetcherAsync calls into asynchronously. We'll have to see how that works.

Being able to pull the next/prev image over after you scroll to and past the edge. Maybe the tab thing can help with this? Seems like a bit of an abuse of the component though. I'll have to look into it.

Add support for either deleting manga manually or automatically after a certain period of time.

Also might look at handling the case of the use deleting the image files manually. Perhaps set imagePath to null and then fullyParsed to false?

Will probably also want to look at non-persistent reading. Some series I might not really want it to keep on my device for any lengthy period of time.

What it says on the tin.

One Piece looks like it's off by about 10 in the end. 788 vs 798. Not sure where that's coming from.

I'm not sure what's best here. I think by the time it gets to me it should be JSON, but where should that come from? A server somewhere? A flat-file somewhere in the YAMR folder? We'll have to think about it.

This is a big one. I need to do a bunch of research into the dozen or so manga sites/databases I've found so far to see how much I'll be able to do to de-dupe series.

I have a suspicion that none of them will have a strict superset of any other. (Except perhaps mangastream, which shouldn't really count.) Which makes attempting to do this de-dupe on the device a much more questionable proposition. We'll have to see. I'm really not keen on introducing a dependency on a companion web service.

The idea is to save some space while it's not urgently needed. We'll have to see if compressing directories of images actually saves much of anything. It might be that simply using a compressed format is about as good as it's going to get.

Reproduction Steps

• Navigate to the first chapter from browse
• Swipe right (prev.)
• Get the end of series message
• Hit the back button
• Navigate into the first chapter again
• Get the NPE.

Something kind of like Mango. (Loading page 2/53) Don't know where to put it. Top for status, bottom for bar? I'll have a think.

When hitting the back button when reading from a favorited series, the progress doesn't update properly. I imagine the Fragment is getting cached/reused or something.

Search by things like genre, author, alt. title, last updated date, things like that.

It has to do with ordering. I'm going to go in and change the 'Rel' page and chapter queries into specific prev/next ones.

I'm really not sure how we're going to do this one. Might have to move away from IntentService. Donno.

There are tons of places that need better error handling. Paging to the end of a series crashes an app. And I'm sure if mangapanda doesn't have the image when it shows the page (Will need to find an example of this) the app also explodes. It'll also explode if there's no network. Lots of little things.

Allow a user to favorite/bookmark their favorite series. Tie this into the notifications and updates process.

Be able to re-DL and parse any MangaElement. For the 'try again' type things. I might just let the SQLite url uniqueness constraint throw an exception and catch that. Might be pretty simple. We'll see.

Reproduction Steps

• Go all the way down to a page
• Turn the screen off
• Turn the screen back on
• Hit the back button

You can't see the very first item on the list, and part of the second.

Swap between Right to Left and Left to Right for page navigation.

Maybe on the PageViewer ActionBar?

Periodically scrape the front page for the newest series, and then make notifications for new chapters in the favorites list. (Depends on that being done)

Hopefully won't need to do too much.

The idea here is to use something like Rhino in combination with JSoup to be able to script the actual parsing process. Then load the scripts from a DB.

I'm not sure how big this would be, but something tells me it's pretty big. I'll have to do some reading on Rhino or some other scripting VM to embed.

Things like alternate titles, genre's, dates, authors, thumbnails, etc.

This might get a little obnoxious. The first stackoverflow I found seemed to suggest you needed to handle the buffer yourself, which is tedious and error-prone. Can probably write it once and stick it in FetcherSync.

This might be a prime target for AsyncTask. Or maybe have it generated just after we save the image? I'll take a look.

I think the savedInstanceState Bundle is the right answer, but I'm not sure. I'll probably need some more time researching here.

In Landscape, the image is off center vertically. Not a huge issue, but it's annoying.

What it says on the tin.

Maybe have it in a detail display style thing a'la Mango?