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

Make "Playback speed controls" dialog contents more compact #6150

Closed
wants to merge 2 commits into from
Closed

Make "Playback speed controls" dialog contents more compact #6150

wants to merge 2 commits into from

Conversation

AmooHashem
Copy link

@AmooHashem AmooHashem commented Apr 23, 2021

What is it?

  • Bugfix (user facing)
  • Feature (user facing)
  • Codebase improvement (dev facing)
  • Meta improvement to the project (dev facing)

Description of the changes in your PR

  • As mentioned in Speedmenu layout in landscape mode #4913, it's better in UX to add a landscape layout for "Playback Speed Control" and do some small changes on it, in proportion to portrait layout.
  • In addition, there was some redundant properties for xml tags in portrait layout, that I remove them.

Fixes the following issue(s)

Relies on the following changes

APK testing

On the website the APK can be found by going to the "Checks" tab below the title and then on "artifacts" on the right.

Due diligence

@TobiGr
Copy link
Contributor

TobiGr commented Apr 25, 2021

Thank you. Can you post screenshots of the changes? And please give your PR a proper title

@AudricV
Copy link
Member

AudricV commented May 3, 2021

@AmooHashem Can you do what @TobiGr said above, please? Thank you!

@triallax triallax changed the title Issue#4913 Make "Playback speed controls" dialog contents more compact May 4, 2021
@AmooHashem
Copy link
Author

Sorry for late answering.
I just put "Unblock (may cause distortion)" and "Fast-forward during silence" check boxes in one row in landscape layout, there is no other changes.

@triallax triallax added feature request Issue is related to a feature in the app GUI Issue is related to the graphical user interface labels May 12, 2021
@timjefferies
Copy link

timjefferies commented Jun 9, 2021

Instead of a scrollable window pane which is very confusing, it would be much more intuitive to have a 2 column grid with extra speed steps, i.e. 1.75x 2x 2.5x and 3x

The word Speed needs to look like a button or nobody will know it can be changed.

Reset, OK and cancel buttons are too close together and could be accidentally pressed.

@Stypox
Copy link
Member

Stypox commented Jun 9, 2021

Why not just making it so that the speed button in the popup open the same dialog as the background and normal players?

android:paddingTop="@dimen/video_item_search_padding"
android:paddingRight="@dimen/video_item_search_padding">

<RelativeLayout
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While you are at it, please convert everything to a single ConstraintLayout nested inside a ScrollView, it will make everything simpler and with less nesting.

@@ -14,6 +14,7 @@
<dimen name="video_item_search_thumbnail_image_width">142dp</dimen>
<dimen name="video_item_search_thumbnail_image_height">80dp</dimen>
<!-- Calculated: 2*video_item_search_padding + video_item_search_thumbnail_image_height -->
<dimen name="video_item_search_padding">18dp</dimen>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is this? Also, pay attention to the comment in the line above (16): I think it refers to the line below (18), not to this one (15)

@Stypox
Copy link
Member

Stypox commented Jun 9, 2021

@SameenAhnaf I don't think your menu is a good idea. Designing small unfamiliar menus with not-so-clear actions just for the purpose of reducing used space is not a good option. The current menu is ok, there's no need to reinvent the wheel, otherwise the app will become unusable for everyone except experts and very difficult to maintain due to the many bugs that would arise. When you propose a solution, please think about this: is it a standard component or would it require designing a completely new layout with strange actions? is it easily understandable by someone who has never ever used the app? are the various actions easy to click on (i.e. no small buttons), even on Android TV (i.e. navigating with ←↑↓→ is obvious)?

@SameenAhnaf

This comment has been minimized.

@timjefferies
Copy link

A scrollable menu in this usage case is terrible ux. It took me minutes to figure out what you meant and that's with you explaining and pointing it out. Casual users have no hope. Also for me it would take more button pushes than the existing menu.

@Stypox
Copy link
Member

Stypox commented Jun 9, 2021

"Unhook" and "FF" are not meaningful to a new user. Changing pitch can only be done by accessing yet another nested menu. The graphic would be difficult to implement and would not provide any real advantage.

Let 10% be the only step. No need to keep too many steps. I wonder who requires so many precise steps like 1 or 5%.

I sometimes use them, someone who wants to play guitar a little bit slower (e.g. 8%) would use them, ...
If there's one thing I've learned, is that people have different needs and such an assumption is not valid.

Why not just keep the current layout and call it a day? I mean, it provides all of the needed features. This PR fixes the problem arising on tablets/landscape, when the user would have to scroll down in order to be able to reach all of the buttons, and that definitely needs fixing. But let's not reinvent the wheel just because a button may be more accessible... that can usually be solved in simpler ways, e.g. just by moving things around on tablets/landscape like this PR did.

Copy link
Member

@Stypox Stypox left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(This comment applies only to the landscape layout) I just tested and noticed the "Fast-forward during silence" button overlays the "Unhook" text. This has to be solved. I would also move the "Tempo" and "Pitch" labels to the left of the seekbars, as there is plenty of horizontal space, and remove as much vertical spacing as possible (but it should still look good, not cluttered).

@thatwasso
Copy link

What about making "presets" for speed playback? Without having to modify it every time, buttons with common speeds would be interesting (1.25x, 1.50x, 2x)

To explain better I use a lot AntennaPod and I like this speed options a lot image

@litetex
Copy link
Member

litetex commented Nov 5, 2021

Superseded by #7351 and #7363.
May be closed in favor of these PRs.

@litetex
Copy link
Member

litetex commented Nov 12, 2021

Superseded by #7363.

Anyway thank you for the PR 😄

@litetex litetex closed this Nov 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Issue is related to a feature in the app GUI Issue is related to the graphical user interface
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Speedmenu layout in landscape mode
9 participants