timusus/Shuttle

Playlist Padding / Remove Default Playlists

Open

#337 opened on May 6, 2018

View on GitHub
 (7 comments) (3 reactions) (0 assignees)Java (2,217 stars) (494 forks)batch import
enhancementgood first issue

Description

I want to suggest that the padding (size) of the playlists be reduced, or at least have to option to remove/hide the defailt playlists. As it stands, when I scroll to my playlist tab in the library view, I can only see 5 playlists, 4 of which are the default:

-Podcats -Recently added -Most played -Favourites -Created playlist

At the moment I have 0 need for any of the prebuilt playlists and want to not have to scroll to reach my own. At the very least an option to re-order the playlist so I can put my own at the top. It doesn't help that when scrolling between tabs in the library view (horizontally) the scrolling hangs and stops if you accidentally scroll vertically. It makes reaching and playing my playlists really difficult.

Thanks for your effort anyways, Cheers

Shuttle version:

2.0.4 (Upgraded)

Device, OS:

Huawei P9 Lite SLA-L02 EMUI 5.1 Android 7.0

Contributor guide

Tech stack
javaandroid
Domain
mobile
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Java programmingAndroid development experience
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Examine the layout files for the playlist tab (likely in res/layout) and the playlist adapter code. Identify where default playlists are created (possibly in a database helper or mock data provider). Check the issue comments for any maintainer suggestions on approach. Test the current behavior to confirm the desired change.