microsoft / microsoft/WindowsAppSDK

Widget boards - differences

Open
#5,420 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
4.7k
Forks
471
Avg merge
3d 13h
Merged PRs (30d)
28

Description

Hi, I'm the developer of the Calendar Flyout app. While testing the widget included in the app, I noticed some differences between two versions of the widget board. As shown in the image below, the left column refers to the old version of the widget board, and the right column shows the WinUI-based widget board.

I have a few questions:
1. Are there any plans to align the engine that renders widgets from a JSON payload so that they appear the same across both boards?
2. If not, is there any way to detect which version of the widget board the client is using?
3. Are there any plans to fully replace the old widget board with the new WinUI-based version? If so, when is this expected to happen?

Currently, it's not possible to adjust the payload to look good on both widget boards. If you're offering app integration with the widget board, please ensure that everything is consistent and delivers the same high-quality experience.

Image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names the legacy and WinUI-based widget boards and their JSON payload rendering, but no source files, tests, or entry points. Start by locating the two board implementations and comparing their rendering paths; done would require an agreed compatibility or version-detection plan.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.