-
Notifications
You must be signed in to change notification settings - Fork 7.6k
"What's new" improvements #44638
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"What's new" improvements #44638
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR introduces significant improvements to the "What's new" experience in PowerToys by replacing the old OOBE-based approach with a new standalone window (SCOOBE - Secondary OOBE) that presents release notes in a VS Code-style interface.
Changes:
- Created a new standalone
ScoobeWindowfor displaying release notes with a navigation menu for switching between versions - Replaced custom title bars with the inbox WinUI
TitleBarcontrol in both OOBE and SCOOBE windows - Upgraded
CommunityToolkit.Labs.MarkdownTextBlockpackage to version0.1.260107-build.2454for improved markdown rendering and bugfixes - Removed the
OobeWhatsNewpage andWhatsNewmodule from the OOBE flow, moving this functionality to the dedicated SCOOBE window - Implemented release grouping by major.minor version with support for combining point releases
Reviewed changes
Copilot reviewed 19 out of 19 changed files in this pull request and generated 11 comments.
Show a summary per file
| File | Description |
|---|---|
settings-ui.sln |
New solution file for Settings UI projects (appears to be a complete replacement) |
Resources.resw |
Added localization strings for the new ScoobeWindow and updated OobeWindow title property from .Text to .Title |
DashboardPage.xaml.cs |
Updated "What's New" button to launch ScoobeWindow instead of OobeWindow |
ScoobeWindow.xaml.cs |
New standalone window implementation for displaying release notes with IDisposable pattern |
ScoobeWindow.xaml |
XAML for the new SCOOBE window with MicaBackdrop |
OobeWindow.xaml.cs |
Added ExtendsContentIntoTitleBar property and minor refactoring |
ScoobeShellPage.xaml.cs |
New page for managing release notes navigation, fetching from GitHub, and grouping releases |
ScoobeShellPage.xaml |
Navigation UI with dynamic menu items for release versions |
ScoobeReleaseNotesPage.xaml.cs |
Markdown processing logic for release notes including hero image extraction and PR link conversion |
ScoobeReleaseNotesPage.xaml |
Display page for formatted release notes with hero image and markdown content |
ScoobeReleaseGroupViewModel.cs |
View model for grouping releases by major.minor version |
OobeWhatsNew.xaml.cs |
Deleted - functionality moved to ScoobeWindow |
OobeWhatsNew.xaml |
Deleted - UI moved to ScoobeWindow |
OobeShellPage.xaml.cs |
Removed WhatsNew module, changed from UserControl to Page, replaced custom title bar with TitleBar control |
OobeShellPage.xaml |
Updated to use TitleBar control, moved "What's New" to PaneFooter with Tapped event |
MainWindow.xaml.cs |
Updated to use ScoobeWindow for "What's New" functionality, added ExtendsContentIntoTitleBar |
App.xaml.cs |
Added ScoobeWindow state management methods and removed ExtendsContentIntoTitleBar setting during launch |
PowerToysModules.cs |
Removed WhatsNew enum value |
Directory.Packages.props |
Upgraded MarkdownTextBlock package version |
Summary of the Pull Request
TO DO: Upgrade to the latest version of MarkdownTextBlock: CommunityToolkit/Labs-Windows#771
This PR introduces the following changes:
Removed the custom titlebars on the OOBE Window, and replaced it with the inbox WinUI
TitleBarcontrol.New "What's new" experience following the VS Code release notes experience
CommunityToolkit.Labs.MarkdownTextblockto the latest version as it includes much needed bugfixes.Note: the blurry image shown above will be replaced in new releases by an image that fits the right dimensions.
PR Checklist
Detailed Description of the Pull Request / Additional comments
Validation Steps Performed