-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
New Settings categorization #9587
Comments
Uh oh! #9580 is already on the way. Should we discuss more about this? Personally, I don't find Related to |
Will the subscription json file be added to the import/export as well? Just wondering as every few months we get an issue about how to import new pipe subscriptions and i think it might be a good idea to include it here as well as a description indicating that you could use it to import subscriptions into other youtube clients (ex: invidious, piped or freetube) |
Right now, the focus is on just rearranging the currently existing settings. After this is done, we can consider adding or removing settings, etc.
We can ask people to test the PR and give feedback about this.
We can ask @pratyaksh1610 if he would like to take this up. What say, Pratyaksh? |
Meanwhile, @ChunkyProgrammer you can add your opinion to #3192. |
How about to merge YouTube and PeerTube settings in Services section and remove Content section at all (worst offender indeed). Not clear what exactly will remain there since pretty much everything (except age toggles) moving to it's own sections |
Maybe. Testing a PR would help iron these things out. |
@opusforlife2 Sure, I will work on this. |
Should I raise a new PR for the same or continue working on the same branch and modify it ? #9580 |
@pratyaksh1610 Can you update the branch name? I think everything else is editable in an existing PR, but I think that needs a new PR. |
can i work on it |
@pratyaksh1610 Could you confirm if you're still working on this? |
I am working on it. Lost track of this due to my exams. |
@abhi835 You're welcome to take up some other issue you're interested in. |
@pratyaksh1610 Is this still on your plate? |
Hi @opusforlife2,
|
@snaik20 Thanks for having a look! What you see in the description is all we have right now. So icons will have to be discussed. Regarding the order, it will have to be rechecked. Off the top of my head I can't think of anything that needs to be changed. So maybe any modifications that come up can be discussed in the PR? Oh, but before there's further movement on this, let's ensure we have a go ahead from the team. @TobiGr? |
Hi @opusforlife2, @TobiGr, Made some changes in #10490. Please let me know if you have any feedback around the changes and icons used/missing. |
- Added a new settings option to enable the settings page redesign. - This option allows us to integrate and test the new settings page gradually, minimizing disruptions to the current behavior. - Reused the rest of the debug menu to reflect in the new settings page. - Verified the functionality of all debug settings. Next plan: - Create PRs to gradually add all the subsections as detailed in TeamNewPipe#9587. Note: - This PR prepares for upcoming updates by setting up the necessary changes for follow-up PRs.
- Added new files for the Fragment and xml related to the player settings page. - Implemented the player settings page per the description in TeamNewPipe#9587. - These changes facilitate easier switching between current and new behaviors. - They also lay the groundwork for easier cleanup when the new design is approved and enabled by default. Video: - https://github.com/TeamNewPipe/NewPipe/assets/87667048/00385bbb-6a2f-4ce5-b6b9-6cf1cb5c5636
Checklist
Feature description
Hey there. The team went through several rounds of discussion regarding the current Settings tree/layout, and finalised a new one that should hopefully make the menus much easier and intuitive to navigate.
Here is the current layout:
Here is the new layout the team has decided on:
Why do you want this feature?
The current layout has been a struggle to fit new settings into, and has become very non-intuitive.
Additional information
No response
The text was updated successfully, but these errors were encountered: