DS-Homebrew / TWiLightMenu

DSi Menu replacement for DS/DSi/3DS/2DS
https://wiki.ds-homebrew.com/twilightmenu/
GNU General Public License v3.0
3.24k stars 202 forks source link

Redo Settings.srldr conpletely #853

Open NightScript370 opened 4 years ago

NightScript370 commented 4 years ago

Is your feature request related to a problem? Please describe. The interface is very text oriented, which makes it feel less user-friendly and moreso of editing the INI file directly (just with more checks so that you dont do anything illegal and know what you're doing).

Describe the solution you'd like A completely remade System Settings module that can be changed based on your theme selection. It would have an initial setup with 5 different pages:

  1. Greetings Page, welcoming you to the application and letting you know that you could always change these settings at a later point in time by using the settings app or editing the INI file manually. This page will also show you if you're missing any files from a failed copy.

Similar to Android and iOS initial setup, this will allow you to change your language. A sub option will be to change your region.

The back button which would normally be present will be replaced with a "Use Defaults" button Hitting the Use Defaults button would show a list of all the default settings that will be applied instead. Hitting "OK" will set those settings and boot you to the menu. Here's the list of Default Settings:

  1. Which theme to use (DSi | 3DS, HBL | Saturn, R4 | Gameboy, AceKard). The order is picked in terms of left being "official" and right being wacky

At the bottom, alongside the next button will be a skins button, in case one already added them.

  1. Boot Intro settings (Show Health and Safety + TWiLight Menu++ boot screen)

That's just initial setup though. We also have the main star of the show: The settings rewrite in general. This would be accurate to the DSi theme but the 3DS theme would only need to change a button placement and remove some text.

For the record, let's set up some terminology. This is a "page", where you navigate through all the settings you could change: image

This would be the "sub page", where you actually change the settings: image

The first page would be all about Themes, so the entries would be "Theme Selection", "Skin Selection", "Per-Theme Settings" & "File Type" Settings. Theme Selection would be the DSi | 3DS, Saturn, R4 and AceKard thing above, with the "Next" bottom button removed. (leaving just back and sub-theme)

SubTheme settings would be designed like the Data Management page, like this: image

The top screen would have a preview of the selected sub theme.

The "Per-Theme settings" sub page would be like this: image

It would contain these options, depending on which theme you use:

Sort: Custom, Recent Played, Most Played, File Type, Alphabetical Hidden Files Show Folders Animated Icons (Do not show on R4 Theme) Box Art (Do not show on R4 Theme): None, Enabled, In Memory Clock Format: 24, 12 Scroll Speed: Fast, Medium, Slow Zoom Icons (AceKard theme ONLY): On, Off

File Type should be self explanatory. It'll be the layout of the Per-Theme settings with all the console types being shown

Page 2 would be the events that happen on bootup, such as Main Menu & Splashes Page 3 will be all about GBARunner2 Page 4 will be all about nds-bootstrap Page 5 would be Advanced, with options like LED Lights, to use bootstrap/gbarunner2 at all, debugging and logging as well as Slot1SCFG unlocking and force sleep mode patches

Describe alternatives you've considered

NightScript370 commented 4 years ago

https://cdn.discordapp.com/attachments/489307733074640926/661983589151539201/Initial_setup_mockup.png

I forgot to post this, but Vulpes made this concept image

NightScript370 commented 2 years ago

I updated the issue to match with the later TWiLight versions.

I didnt finish, though, due to time constraints. Im only bumping this so I can get a general feel of what everyone thinks about this. Either way, I want to make concept art cause my wording skills were poor and the way I currently describe it seems like there would be 100 or so pages that users would have to navigate through to change one setting, when I already have an idea for a fix