Verel Pode

@JohnF38 Consider also [BladeView](https://docs.microsoft.com/en-us/windows/communitytoolkit/controls/bladeview). Even if you end up deciding that BladeView doesn't suit your particular app, you'll still get a benefit anyway, because thinking about BladeView will expand your...

@JohnF38 To clarify, even though I find the current design of GridSplitter problematic, and the unofficial GridSplitter in Community Toolkit has the same problematic design, you could still use it...

@jordui > Floating/Docked windows are a must-have and can be achieved with XamlIslands. I'm confused by your comment. Did you accidentally say XamlIslands instead of some other tech? XAML Islands...

@MarkIngramUK -- UWP's ability for multiple windows is not new. I mentioned [ApplicationView](https://docs.microsoft.com/en-us/windows/uwp/design/layout/show-multiple-views) in a previous message. ApplicationView was introduced in Windows v10.0.10240, released during 2015. To me, your description...

@MarkIngramUK -- and you dislike the different thread? I agree with you. I complained about this threading issue already in [my previous message](https://github.com/microsoft/microsoft-ui-xaml/issues/1080#issuecomment-514664194). Thankfully jevansaks then pointed out that this...

@JohnF38 > Do you think WinUI is actually an appropriate choice for a new 100% desktop application ? Definitely (except in very special cases). When you make a new project...

@michael-hawker > would you mind summarizing the problems you have with GridSplitter as a new issue for the toolkit? OK, I've opened [issue #2976](https://github.com/windows-toolkit/WindowsCommunityToolkit/issues/2976).

Re the comments about docked windows, note that `AppWindow` is unnecessary for creating a so-called "window" in a docked state. ### Dock + Auto Hide: If the "docked window" should...

@michael-hawker -- Although I can think of reasons to choose the .NET Core option over Framework, I don't know the best reason. What's the best or most important reason? Earlier...

> In this case it is, that's why it's called FontIcon. It's called FontIcon not TextIcon therefore it shouldn't behave like text, but currently it does behave like text and...