mirror of https://github.com/microsoft/PowerToys.git synced 2025-12-15 03:07:56 +01:00

Files

Stefan Markovic 073caffef4 [Settings, Common.UI, runner exe] Unify exe/dll naming (#15005 )

* Unify exe/dll naming - PowerToys.Runner

Align naming with other exes - PowerToys Runner -> PowerToys.Runner

* Unify exe/dll naming - Microsoft.PowerToys.Common.UI

Project name - Microsoft.PowerToys.Common.UI -> Common.UI
dll name - Microsoft.PowerToys.Common.UI.dll -> PowerToys.Common.UI.dll

* Unify exe/dll naming - Settings

Project names - Microsoft.PowerToys.Settings* -> Settings*
Dll names - Microsoft.PowerToys.Settings*.dll -> PowerToys.Settings*.dll

* Revert file autoformat

* [Docs] Update paths to settings projects/files

* Fix tests - Update path

2021-12-15 12:56:52 +01:00

1.3 KiB

Raw Blame History

UI Architecture

The UI code is distributed between two projects: PowerToys.Settings and Settings.UI. PowerToys.Settings is a WPF .net core application. It contains the parent display window and corresponding code is present in MainWindow.xaml. Settings.UI is UWP applications and contains views for base navigation and modules. Fig 1 provides a description of the UI controls hierarchy and each of the controls have been summarized below :

MainWindow.xaml is the parent WPF control.
WindowsXamlHost control is used to host UWP control to MainWindow.xaml parent control.
ShellPage.xaml is a UWP control, consisting of a side navigation panel with an icon for each module. Clicking on a module icon loads the corresponding setting.json file and displays the data in the UI.

Fig 1: UI Architecture for settingsv2

1.3 KiB Raw Blame History

UI Architecture

1.3 KiB

Raw Blame History