## Summary of the Pull Request Accumulated information from internal transition about the modules development, and reworked it to be added in dev docs. Also the dev docs intself was restructured to be more organized. New pages was verified by transition team. ## PR Checklist - [x] **Dev docs:** Added/updated --------- Co-authored-by: Zhaopeng Wang (from Dev Box) <zhaopengwang@microsoft.com> Co-authored-by: Hao Liu <liuhao3418@gmail.com> Co-authored-by: Peiyao Zhao <105847726+zhaopy536@users.noreply.github.com> Co-authored-by: Mengyuan <162882040+chenmy77@users.noreply.github.com> Co-authored-by: zhaopeng wang <33367956+wang563681252@users.noreply.github.com> Co-authored-by: Jaylyn Barbee <51131738+Jaylyn-Barbee@users.noreply.github.com>
1.3 KiB
Overview
Settings
is Windows App Sdk WinUI3 .Net Unpackaged desktop application. More details about Windows App Sdk can be found in Windows App SDK - Calling all Windows developers!. More details about WinUI can be found in Build apps with WinUI.
Settings V2 Project structure
The Settings project .Net WinUI3 based project which follows the MVVM architectural pattern where the graphical user interface is separated from the view models.
UI Components:
The UI Components are part of PowerToys.Settings project. It contains the xaml files for each of the UI components. It also contains the Hotkey logic for the settings control.
Viewmodels:
The Settings.UI.Library project contains the data that is to be rendered by the UI components.
Settings Runner:
The function of the settings runner project is to communicate all changes that the user makes in the user interface, to the runner so that it can be dispatched and reflected in all the modules.