[0.37 release] work items checklist

[enricogior]

Only install/run on 1903 and higher #9417

• Update the .exe installer to only run on 1903 and higher [Auto-update] Remove special case logic for autoupdate disabling #10264
• Update the .msi installer to only run on 1903 and higher [MSI] Require at least Windows 1903 #10263
• Remove code that supports running on older than 1903 ([Auto-update] Remove special case logic for autoupdate disabling #10756)
• Update the runner to only run on 1903 and higher (low priority, postponed) ([runner] prevent the runner from starting on older than 1903 #11075)

Remove old Settings #9417

• Remove old Settings from the MSI ([msi] remove old settings from installer #10546)
• Remove old Settings from the main Solution ([old settings] deprecate old settings #10548)
• Delete old Settings source files ([old settings] deprecate old settings #10548)
• Image Resizer: remove in-app settings ([Image Resizer] remove old settings #10837)

Migrate KBM engine out of the runner #10127

• Create a standalone C++ project, since we have some project names conflicts, let's call it KeyboardManagerEngine for now, we will later rename it accordingly before merging it.
• The executable will be called PowerToys.KeyboardManager.exe
• Use Keyboard.ico for the PowerToys.KeyboardManager.exe process
• Use a file watcher or a system event to reload the settings.
• Add system events to suspend/resume the engine while the editor is open.
• Update telemetry if needed
• Add global exception handler
• Add new binaries to the installer
• Add new binaries to the signing stage
• Add log to the BugReportTool
• Set proper version number on the .exe

Migrate KBM editor out of the runner #10127

• Replace the KeyboardManagerUI project KeyboardManagerEditor and make it a standalone app
• From the Settings app, invoke the KeyboardManagerEditor directly, without passing through the runner and the module callback
• Send events to pause/resume the KBM engine
• Add keyboard hook to enable typing keys
• Add global exception handler
• Use Keyboard.ico for the PowerToys.KeyboardManager.exe process
• Add new binaries to the installer
• Add new binaries to the signing stage
• Coordinate with the localization team to minimize the impact of these changes
• Add log to the BugReportTool
• Set DPI awareness
• Set proper version number on the .exe
• Exit when PowerToys.exe quits

Update Color Picker to use the Runner keyboard hook to start/show the UI #8831

• Add module interface to register the shortcut
• In ColorPicker module interface implementation, start ColorPicker if it's not already running and notify to show the UI
• In ColorPickerUI, process the command line arguments to detect if it was started from PT Run or standalone. If running standalone use the internal keyboard hook

Unify Naming Structure for Telemetry Events

• see checklist in Unify Naming Structure for Telemetry Events #9343

[htcfreek]

@crutkas
With 0.37 readme we should add a comment for us that new plugins should be mentioned with the keyword. Otherwise the user doesn't know this.

[crutkas]

This is a work track item for 0.37. Assuming this is more in terms of a readme? Can you give an example of how you'd like to see it show up in a readme?

[htcfreek]

This is a work track item for 0.37. Assuming this is more in terms of a readme? Can you give an example of how you'd like to see it show up in a readme?

Here or in a new issue/the docs issue?

Something like this:

• New Plugin "VS Code"
  (Actionkey: {; Off by default)
  This plugin .....

[crutkas]

@htcfreek, the readme for 0.35 directly states the action key.

[htcfreek]

@htcfreek, the readme for 0.35 directly states the action key.

Yes. Found it later.