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

Replace TerminalSettings runtimeclasses with interfaces only #1196

New Issue
Open
opened 2026-01-30 22:18:50 +00:00 by claunia · 0 comments
claunia commented 2026-01-30 22:18:50 +00:00
Owner
Copy Link

Originally created by @DHowett-MSFT on GitHub (May 17, 2019).

Originally assigned to: @carlos-zamora on GitHub.

TerminalSettings.dll exists because it is difficult to coerce the C++/WinRT build infrastructure to produce a type library and a set of headers without either statically linking (which rolls up the generated types into the consuming project) or dynamically linking (which forces us to put a DLL on disk).

I posit that the ideal representation of settings is the ICoreSettings and IControlSettings interfaces only. No classes need to be implemented in TerminalSettings.dll, because all they'd do is ferry data back and forth.

By dropping the classes and switching to the interfaces, we can remove the setters from the interfaces, and remove the runtime classes completely. Cascadia (or TerminalApp::<something>) can implement ICoreSettings and IControlSettings as views over existing profile data.

This will reduce both the number of runtime hops required for loading and saving settings and the number of code authoring hops required for adding new settings.

Approach

  • #7139: Introduce/Move TerminalApp bridge
    • Move TerminalSettings::TerminalSettings to TerminalApp::TerminalSettings
  • #7140: Move TerminalSettings interfaces
    • Move TerminalSettings::ICoreSettings to TerminalControl project
    • Move TerminalSettings::IControlSettings to TerminalControl project
  • #7141: Transform TerminalApp settings objects into WinRT objects
    • Profile
    • ColorScheme
    • GlobalSettings
    • Keybindings (this may be moved out to be its own PR)
  • Move the new WinRT settings objects into TerminalSettings project
    • I'll close the scenario when this is complete
Originally created by @DHowett-MSFT on GitHub (May 17, 2019). Originally assigned to: @carlos-zamora on GitHub. **TerminalSettings.dll** exists because it is difficult to coerce the C++/WinRT build infrastructure to produce a _type library_ and a set of headers without either statically linking (which rolls up the generated types into the consuming project) or dynamically linking (which forces us to put a DLL on disk). I posit that the ideal representation of settings is the `ICoreSettings` and `IControlSettings` interfaces _only_. No classes need to be implemented in TerminalSettings.dll, because all they'd do is ferry data back and forth. By dropping the classes and switching to the interfaces, we can remove the setters from the interfaces, and remove the runtime classes completely. Cascadia (or `TerminalApp::<something>`) can implement `ICoreSettings` and `IControlSettings` as views over existing profile data. This will reduce both the number of runtime hops required for loading and saving settings and the number of code authoring hops required for adding new settings. ## Approach - [x] #7139: Introduce/Move TerminalApp bridge - Move `TerminalSettings::TerminalSettings` to `TerminalApp::TerminalSettings` - [x] #7140: Move `TerminalSettings` interfaces - Move `TerminalSettings::ICoreSettings` to TerminalControl project - Move `TerminalSettings::IControlSettings` to TerminalControl project - [ ] #7141: Transform TerminalApp settings objects into WinRT objects - Profile - ColorScheme - GlobalSettings - Keybindings (this may be moved out to be its own PR) - [ ] Move the new WinRT settings objects into TerminalSettings project - I'll close the scenario when this is complete
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 Area-Settings Issue-Scenario Needs-Tag-Fix Product-Terminal Resolution-Fix-Committed
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#1196
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?