[discussion] access to episodes page

[thigg]

Besides that the episodes page should load on application startup and not when you open it,
I find myself sometimes annoyed when using the pulley to open it. I guess it is because the pulley are two actions (pull +coordinate selection) and episodes is basically my main page.

I wanted to start a discussion about how the ui can be improved here.

I'll start with some ideas:

• add option to make episodes page the default page
• put episodes page somewhere on the pagestack
  • left might interfer with navigation
  • could always be right, if one is on the default page. For this, the player would have to go into a toolbox or smth.
• ... More ideas?

[sfbg]

Hi,
Great initiative. I have been having ideas on the exact same topic for a while, but never had the time to implement them and test them out.

This is how I imagine it:

• The filter (Downloaded, etc.) and Podcast (single podcast) episode list should be the same implementation. And always right of the Podcast list, accessible with a swipe right for the filtered list, or with a tap on a Podcast entry for the specific Podcast episode list.
• The filters should be reduced in number (Fresh, Downloaded, Not played, up for discussion) and be available directly in the pulley of the Episode list, not as now in a separate selection step (this annoys me a lot)
• The Player view should remain to the right of the Episodes list and be there also after startup (just empty)

If all three screens are always there we, would have a more consistent navigation (reminiscent of the Harmattan 3 screens).

I do not have an opinion on the initial startup screen, but would not mind it being the Episode list (Downloaded).

[thigg]

How about having a media player like in the stock media app?
what is your opinion on that?

[sfbg]

It might be fine, I do not know. It is just quite different from how I am used to using gPodder. But I am open to new options for sure.

[thigg]

maybe we should just draft some designs and select what seems to be the best?

[Keeper-of-the-Keys]

I'm puzzled here, when you open a podcast you are going to EpisodesPage afaik, when you apply a filter EpisodesPage gets modified.
I never use a pulley to get into the Episode List, only when I want to filter the list.

Also to the best of my knowledge (at least the way I use it) it does end up on the page stack.

Other then that I would actually like to replace filters with a search window that has presets, in the long run I would actually like to add search across all/multiple podcasts so that I can search for all episodes with a certain subject/word in the description.

[thigg]

Other then that I would actually like to replace filters with a search window that has presets, in the long run I would actually like to add search across all/multiple podcasts so that I can search for all episodes with a certain subject/word in the description.

Just a quick comment: your point is multiple but not all podcasts, right? Because the text search over all is implemented in the PR

[Keeper-of-the-Keys]

Cool, I had not yet tested it :) I thought it was only in the podcast you were filtering will test it after I do the gpodder-ui-qml stuff.

Searching across a subset of podcasts would be a more advanced function I guess.

[thigg]

How do you think about something like this?

We could add a searchbar like this to the page somehow.
When clicked, it shows suggestions like fresh, downloaded, podcast etc.
When a suggestion is clicked, it is added as tag with a possibility to add additional input (see examples).
Tags should be removable. Tags should always be placed first in the searchfield (right for RTL languages). Tags are AND related
If the tags fill more than 50% of the space, the box changes to multiline (tags in the first row, cursor in the second).

The result is built into a search query and loads the according model.

Example: All
If no Tag is selected, no filter is applied, thus all episodes are shown

Example: Fresh
The user clicks on the searchbar, a list of suggestions appears, the user clicks on fresh. A tag "fresh" appears in the searchbox, it can be removed by clicking on it/ the X on the field. The user may click the searchbutton/or switch focus to reload the model.

Example: Podcasts
the user clicks on the "podcast:" suggestion, visually a "podcast: " tag is created and the cursor appears inside the tag. The suggestions are now replaced with the list of podcasts. Typing filters this list.
If the user selects a podcast, the cursor is placed into the normal field again and the user may add more tags.

Example: Textsearch
The user already selected the fresh tag. On typing the suggestions disappear/are filtered out and an unclickable "search for text" suggestion appears. If the search button is clicked, the model is filtered for tags + searchtext

I have no idea how much effort it is to implement this/ if something like that exists already. I built something like this years ago, but this was pure JS. Using QML might be a whole different story...

Additionally clicking on a podcast in the podcast overview would just select the appropriate podcast: filter, thus we could unify the episode pages.