starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Fluent Settings page (instead of settings.json and defaults.json) #7754

New Issue
Closed
opened 2026-01-31 01:11:56 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 01:11:56 +00:00
Owner
Copy Link

Originally created by @SFM61319 on GitHub (Apr 28, 2020).

Description of the new feature/enhancement

As the title says, it would look better and be easier to use for both programmers (who are familiar with JSON) and non-programmers. It would also solve many problems.

For example, I have 6 different profiles (3 default and 3 installed), and I want to style all of them at the same time and/or in the same way. Now, the problem is I have to do the same thing 6 times (not all styles are applied by using a common color scheme). But instead, if we have a settings page which lets us choose styles for individual profiles AND/OR lets us make a standard master style template for all profiles, it would make styling easier and much organized.

Also, everyone loves Windows 10's Fluent Design System, and therefore, a Fluent Settings page would make changing settings look much easier and more modern, and in the background, this also easily gets the work done.

Proposed technical implementation details

At the same time, these JSON files may not be removed.

We can create a Settings page (which opens as another tab OR as a completely different section in the same window), with options as checkboxes, color-pickers, float value text boxes (for floating points like "acrylicOpacity", "padding", etc.), etc., and the respective settings will be applied (after clicking on an "Apply" button at the end of the settings page OR dynamically applying them as soon as a setting is changed) by changing the settings.json file (which, if wished, can be accessed by the user by opening the Windows Terminal's directory).

TL;DR

We create a Fluent Settings interface with AcrylicBrush and RevealBrush, etc., which in the background dynamically modifies the settings.json file, as it fixes many boring problems (one of which has been mentioned before as an example), gives a good look and impression on Windows Terminal to many users and will be neatly welcomed.

Originally created by @SFM61319 on GitHub (Apr 28, 2020). # Description of the new feature/enhancement As the title says, it would look better and be easier to use for both programmers (who are familiar with JSON) and non-programmers. It would also solve many problems. For example, I have 6 different profiles (3 default and 3 installed), and I want to style all of them at the same time and/or in the same way. Now, the problem is I have to do the same thing 6 times (not all styles are applied by using a common color scheme). But instead, if we have a settings page which lets us choose styles for individual profiles **AND/OR** lets us make a standard master style template for all profiles, it would make styling easier and much organized. Also, everyone loves Windows 10's **Fluent Design System**, and therefore, a **Fluent Settings** page would make changing settings look much easier and more modern, and in the background, this also easily gets the work done. # Proposed technical implementation details #### At the same time, these JSON files may not be removed. We can create a **Settings** page (which opens as another tab **OR** as a completely different section in the same window), with options as checkboxes, color-pickers, float value text boxes (for floating points like `"acrylicOpacity"`, `"padding"`, etc.), etc., and the respective settings will be applied (after clicking on an "Apply" button at the end of the settings page **OR** dynamically applying them as soon as a setting is changed) by changing the `settings.json` file (which, if wished, can be accessed by the user by opening the Windows Terminal's directory). # TL;DR We create a **Fluent Settings** interface with `AcrylicBrush` and `RevealBrush`, etc., which in the background dynamically modifies the `settings.json` file, as it fixes many boring problems (one of which has been mentioned before as an example), gives a good look and impression on Windows Terminal to many users and will be neatly welcomed.
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 01:11:56 +00:00
claunia commented 2026-01-31 01:11:57 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Apr 28, 2020):

See issue #1564.

@j4james commented on GitHub (Apr 28, 2020): See issue #1564.
claunia commented 2026-01-31 01:11:57 +00:00
Author
Owner
Copy Link

@SFM61319 commented on GitHub (Apr 28, 2020):

@j4james Oh I did not know that existed. And btw, I was kinda talking about a slightly different UI than #1564
Should I close this issue in that case? And if I must close this issue, can I contribute in issue #1564 ?

@SFM61319 commented on GitHub (Apr 28, 2020): @j4james Oh I did not know that existed. And btw, I was kinda talking about a slightly different UI than #1564 Should I close this issue in that case? And if I must close this issue, can I contribute in issue #1564 ?
claunia commented 2026-01-31 01:11:58 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Apr 28, 2020):

Yeah, if you have suggestions for how the UI should work, it's best to add them to the original issue. You'll see there are already a bunch of comments there from different people with their own ideas. As for closing the issue, someone from MS will probably close it with a dup link eventually, but you can also close it yourself if you want.

@j4james commented on GitHub (Apr 28, 2020): Yeah, if you have suggestions for how the UI should work, it's best to add them to the original issue. You'll see there are already a bunch of comments there from different people with their own ideas. As for closing the issue, someone from MS will probably close it with a dup link eventually, but you can also close it yourself if you want.
claunia commented 2026-01-31 01:11:58 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 28, 2020):

Yep, this is definitely a dupe. We should continue the discussion over on that thread. Thanks!

/dup #1564

@zadjii-msft commented on GitHub (Apr 28, 2020): Yep, this is definitely a dupe. We should continue the discussion over on that thread. Thanks! /dup #1564
claunia commented 2026-01-31 01:11:58 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 28, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Apr 28, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Feature Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7754
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?