Update Windows App SDK Roadmap #2270
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ghost
added
the
ryandemopoulos
approved these changes
Mar 15, 2022
|
/azp run |
1 similar comment
|
/azp run |
riverar
reviewed
Mar 16, 2022
| - **Improved default and custom title bar** with new functionalities like z-order, sizing/resizing, tall title bar, and extended show. | ||
| - Apps using the Windows App SDK can **run with elevated permissions**. | ||
| - Apps that deploy with all their dependencies together are now able to include the Windows App SDK as well. **(self-contained deployment)** |
There was a problem hiding this comment.
Awkward sentence and floating parenthetical.
| - Apps using the Windows App SDK can **run with elevated permissions**. | ||
| - Apps that deploy with all their dependencies together are now able to include the Windows App SDK as well. **(self-contained deployment)** | ||
| - Apps can **push notifications** regardless of being packaged/unpackaged, or whether the app is published in the Store. |
There was a problem hiding this comment.
Suggested change
| - Apps can **push notifications** regardless of being packaged/unpackaged, or whether the app is published in the Store. | |
| - Apps can **push notifications** regardless of packaging and where the app is published. |
| - Apps that deploy with all their dependencies together are now able to include the Windows App SDK as well. **(self-contained deployment)** | ||
| - Apps can **push notifications** regardless of being packaged/unpackaged, or whether the app is published in the Store. | ||
| - The **environment variables** PATH, and PATHEXT can be managed and tracked at runtime using new convenient APIs. |
There was a problem hiding this comment.
Suggested change
| - The **environment variables** PATH, and PATHEXT can be managed and tracked at runtime using new convenient APIs. | |
| - The **environment variables** PATH and PATHEXT can be managed and tracked at runtime using new convenient APIs. |
| - Apps can **push notifications** regardless of being packaged/unpackaged, or whether the app is published in the Store. | ||
| - The **environment variables** PATH, and PATHEXT can be managed and tracked at runtime using new convenient APIs. | ||
| - Apps can **restart** manually or register themselves to be restarted if it was running when a system update occurs. |
There was a problem hiding this comment.
Suggested change
| - Apps can **restart** manually or register themselves to be restarted if it was running when a system update occurs. | |
| - Apps can **restart** manually or register themselves to be restarted after a system update occurs. |
|
|
||
| Technologies within the Windows App SDK have already benefitted greatly from the incredible feedback and insights the community has provided around features to build, and bugs to fix. | ||
| *Thank you* for your continued passion and drive to make Windows App SDK the best platform it can be; it has really made a difference! |
There was a problem hiding this comment.
Windows App SDK isn't a platform and AFAIK isn't documented as such.
Suggested change
| *Thank you* for your continued passion and drive to make Windows App SDK the best platform it can be; it has really made a difference! | |
| *Thank you* for your continued passion and drive to make Windows App SDK the best it can be; it has really made a difference! |
|
@gabbybilka did you see my comments above? |
|
Pipelines were unable to run due to time out waiting for the pull request to finish merging. |
1 similar comment
|
Pipelines were unable to run due to time out waiting for the pull request to finish merging. |
|
Doesn't matter now, went live and shown on WinUI Community Call. Great community engagement. |
|
Hey @riverar, unfortunately I wasn't able to address your comments yesterday as we were running into issues with the Azure Pipelines bot and had to manually run the PR pipeline to merge in the roadmap. As time was short between then and the call, I prioritized having a publicly available roadmap for folks to view and leave additional feedback on. I've opened up a new PR to refine the roadmap based off of your suggestions, thank you! #2273 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.