Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support read/unread state tracking #12

Open
josharian opened this issue Mar 20, 2012 · 4 comments
Open

Support read/unread state tracking #12

josharian opened this issue Mar 20, 2012 · 4 comments

Comments

@josharian
Copy link
Collaborator

No description provided.

@josharian
Copy link
Collaborator Author

UI questions to consider:

  • Displaying state. Maybe a nice blue dot for unread?
  • Mark as (un)read. Maybe a left or right swipe, a la Reeder?
  • Mark all as (un)read. Maybe not supported, maybe support through edit menu (like download/delete all).
  • Initial state. Suggestion: All currently downloaded comics be marked as read.
  • Is this surfaced in the search interface? (I.e. can you search only read/unread comics?) Probably not?

@josharian
Copy link
Collaborator Author

Also: How will it interact with #4 (starred/favorited comics)?

@paulrehkugler
Copy link
Owner

It's reasonable to assume that starred/favorites will already have been read, i.e. the ui could reserve space for these (mutually exclusive): empty space (i.e. left padding), an unread dot, or a 'favorite' star.

@josharian
Copy link
Collaborator Author

the ui could reserve space for these (mutually exclusive): empty space (i.e. left padding), an unread dot, or a 'favorite' star.

Works for me. Presumably the backend would store them independently, and then there'd be some kind of trumping -- e.g. stars trump unread -- with the assumption that those collisions will be very rare.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants