per-feed open-in settings

[mkanilsson]

This adds a "Open-in settings" when long-pressing on a feed, allowing users to specify how a feed is opened.

This was a draft because:

1. Internal Browser isn't a option yet. This is marked unnecessary as Chrome-Custom-Tags is basically the same thing. (see per-feed open-in settings #1266 (comment))
2. The option isn't persistent. Unsure why, it's stored in the database but it's always read back as null? This has been fixed thanks to David! (f850ad2)
3. Unsure what a good tag here is. This has been fixed by using a RuntimeException instead.

Closes #1221, #1058 and #957.

Preview

per-feed.mp4

[David-Development]

Internal Browser isn't a option yet.

Good point.. I'm not sure what I would expect as a user.. Do I want the app to open the detail view and navigate to the page automatically? (so that when I do the back navigation I get to the rss item that's stored in the app? - or do I basically want to replace it in the detail view?)

So basically:

• ListView user clicks on item
• ListView -> DetailView (with RSS item) -> automatically navigates to the URL of the article
• user performs back navigation
• ListView -> DetailView (with RSS item)
• user performs back navigation
• ListView

This would also make things easier I think in terms of what happens if you scroll through all unread articles in the DetailView.

---

Unsure what a good tag here is.

Maybe just throw an exception? In that case I wouldn't mind if the app was crashing - this can't happen in real life anyways as we define which values are possible for that field. And if we ever extend it the crash will let us know

[mkanilsson]

I'm thinking that maybe we can skip the Built-In Browser option as Chrome-Custom-Tabs offers basically the same thing with the convenience of not really leaving the app.

NOTE: I'd like to add that if a user clicks on an item that opens in detailed view, swiping left/right works the same as it usually does (i.e. it stays in detailed view and to open in some sort of browser, a tap on the title is required).

---

An exception it is!

[David-Development]

I'm thinking that maybe we can skip the Built-In Browser option as Chrome-Custom-Tabs offers basically the same thing with the convenience of not really leaving the app.

That sounds good to me! I agree that the Built-In Browser doesn't offer any advantage over the Chrome Custom Tabs.

[David-Development]

@mkanilsson Thank you! Looking forward to create a new release sometime this week to make all these new great features available for everyone!