[WIP] CommandBar in PageHeader

[Jay-o-Way]

Description

This PR shows the use of a CommandBar in the PageHeader, to accommodate several buttons. It includes @niels9001 his new button for "About API", and I also started to add a Share button, that's supposed to open the OS Share window (ShowShareUIForWindow). The idea is that this can replace the CopyLinkButton. However, at the moment this is not functioning yet, because the (example*) code assumes this CS to be in MainWindow.xaml.cs and it uses a this keyword that doesn't work in the current place. #needhelp

Code example from https://learn.microsoft.com/windows/apps/develop/ui-input/display-ui-objects#for-classes-that-implement-idatatransfermanagerinterop

WinUI-Gallery/WinUIGallery/Controls/PageHeader.xaml.cs

Lines 116 to 117 in 4505036

	// Retrieve the window handle (HWND) of the current WinUI 3 window.
	var hWnd = WinRT.Interop.WindowNative.GetWindowHandle(this);

Tasks

Preview Give feedback

1. Fix this problem
2. Add visibility converters to hide when content is empty, maybe?
3. Investigate background at IsOpen; this is not visible in the commandbar in Photo app.
4. details, e.g. combine API details + Documentation?

Motivation and Context

This is a nice demonstration of a CommandBar. It is also adaptive in terms of width, so can't have any issues regarding size.
Issues:

• suggestion: use a CommandBar #1503
• Declutter page header #1678

Note: Incompatible with PR #1679

How Has This Been Tested?

Locally.

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Change in UX

[niels9001]

Hey @Jay-o-Way

Thank you for taking the time to create and submit your PR. We’ve carefully reviewed it, and while we appreciate the effort, we’ve decided not to proceed with it in its current form.

Here's our thinking:

• The current UI was intentionally designed by our design team to align with a standardized UX across our developer-focused Gallery applications (e.g., AI Dev Gallery, Windows Community Toolkit Gallery).
• The proposed changes provide limited functional value and introduce an additional click in some cases, which could reduce the discoverability of certain features.

We value the effort you’ve put into this contribution, but for future submissions involving significant UX changes, we should discuss the concept in an issue first. This ensures we can collaborate on the best possible solution and are aligned on the direction. That will avoid unnecessary development work.

[Jay-o-Way]

We’ve carefully reviewed it

Why is that review not public? I would like to see that.

• The current UI was intentionally designed by our design team to align with a standardized UX across our developer-focused Gallery applications (e.g., AI Dev Gallery, Windows Community Toolkit Gallery).

Those apps are different already. Not a strong argument to me.

• The proposed changes provide limited functional value and introduce an additional click in some cases, which could reduce the discoverability of certain features.

I would assume a developer would know to find these buttons. Especially one who used the app before. Note that this is still a work in progress, it's easy to change - like, moving more buttons out of the SecondaryCommands part.

We value the effort you’ve put into this contribution, but for future submissions involving significant UX changes, we should discuss the concept in an issue first. This ensures we can collaborate on the best possible solution and are aligned on the direction.

Now this is where I just get angry. You know very well I've been trying to draw attention to that issue for nine months and it has had no response at all! You all ignored it (and therefore me) and telling me this now is hypocritical and insulting!