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

Added responsive and mobile friendly UI changes #388

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

vijayvcm
Copy link

The current bootstrap UI design is not so mobile-friendly. Added some CSS and changed UI styles to support both desktop and mobile devices

Unfortunately, I have some issues with my laptop on FFmpeg. It shows an error when I run it with localhost.

metube-tablet.mp4
metube-desktop.mp4
metube-mobile.mp4

@alexta69
Copy link
Owner

Hi @vijayvcm ,
Thanks for the PR. I see that it changes the UI to be much less compact, which I think is not for the best. Let's keep the compact layout - the Add button alongside the options, and the advanced options in a drop-down under the Add button.

@vijayvcm
Copy link
Author

Hi @alexta69,

Could you clarify what you mean by 'compact layout'? I'm having trouble understanding it.

Do you prefer keeping the old 'Add' dropdown button instead of implementing advanced options?

Is this preference specific to certain screens or devices?

Could you provide more details on areas needing improvement?

Regarding the separation of the download folder and custom name prefix: The download folder path is often too long and doesn't fit well into the button dropdown area. That's the reason I separated it.

@alexta69
Copy link
Owner

Sorry for the delay in response.
The current layout is compact, in that there are only two rows (the URL and the options + add button). I wouldn't want to expand it to four rows.
On smaller screens, it currently unfolds into five rows, which is also fine. The only issue is with the Add dropdown in this case -- it overflows the screen and doesn't adapt to its size. This is the only problem that needs fixing, IMHO..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants