Feature Idea: Named Saved Views

[beville]

Not an exactly a feature request, but I was thinking about how I've been using Codex, and it's strength is the dynamic views that provides, as you mention in the README:

I usually have the UI on Top Group: Issues, Order by Added Time, descending, no filters. If I want to search for something, I tweak the controls for the top group, search, filter, sorting, etc. Then eventually re-adjust back to my favorite view.

How about a concept of saving views for quick changes? I guess this would be the equivalent of reading lists in other apps? Not sure.

Following along this line, there could be a number of common hard-coded 'preset' views, such as Newly Added, Oldest Unread, or whatever fits some typical usage pattern by many users.

From what I'm seeing of the OPDS XML feed URLs, these would probably nicely fit into an OPDS feed, which could expose these preset and user-created views. This would allow each user to create custom feeds.

As I'm typing this it seems pretty obvious, and you're probably already 5 steps ahead of me on this.

Thanks again for the great work on this.

[ajslater]

Yep. This has been sitting in my TODO list for a long time. It's a feature who's time will likely eventually come.

[bmfrosty]

I was about to create a issue for saving browser preferences on a global and per library basis as I always seem to start at at an issues view and have to change to Folder View/Filename. Consider this a 👍