Proposal: Improve TitleBar Page

[Zakariathr22]

Summary

The TitleBar page in currently demonstrates only the TitleBar control. This can give a limited impression of title bar customization options available in WinAppSDK applications.

Proposal

Split the TitleBar page into two sections:

1. Default AppWindow TitleBar: Demonstrates how developers can work with the system-provided AppWindow.TitleBar and customize aspects such as background color, button colors, preferd height and theme...etc
2. TitleBar Control Keeps the current showcase of the TitleBar control as a custom solution for building fully flexible UI-driven title bars.

TitleBar Page  
 ├─ Default AppWindow TitleBar  
 │   └─ Samples: Background color, button colors...etc
 └─ TitleBar Control  
     └─ Existing samples

[niels9001]

We can probably re-use the existing titlebar samples (that we removed when adding the WinUI titlebar control samples - as the thinking was that all of those samples are on the Docs page already)?

Would it make sense to have 2 pages:

• Windowing
  • AppWindow
  • Multiple windows
  • TitleBar
  • TitleBar customization

or something like that? that way we separate the control vs. more advanced samples

[Zakariathr22]

We can probably re-use the existing titlebar samples (that we removed when adding the WinUI titlebar control samples - as the thinking was that all of those samples are on the Docs page already)?

Would it make sense to have 2 pages:

• Windowing

  • AppWindow
  • Multiple windows
  • TitleBar
  • TitleBar customization

or something like that? that way we separate the control vs. more advanced samples

Since the default title bar is a property of AppWindow, wouldn’t it make more sense to include its customization options in the AppWindow page instead?

[Zakariathr22]

any decision about this?

[niels9001]

My worry is that the AppWindow page already has so many samples? And would it be a logical place to find titlebar customizations?

My mental model would be that 'I want to customize the TitleBar, and if that requires AppWindow so be it.. but how would I know that's the API that I'd be using?'

[Zakariathr22]

My worry is that the AppWindow page already has so many samples? And would it be a logical place to find titlebar customizations?

My mental model would be that 'I want to customize the TitleBar, and if that requires AppWindow so be it.. but how would I know that's the API that I'd be using?'

Good, so I guess having two separate pages is the best option. Should I go ahead with this?