search

microsoft / microsoft-ui-xaml

WinUI: a modern UI framework with a rich set of controls and styles to build dynamic and high-performing Windows applications.
MIT License
6.38k stars 683 forks source link

👨‍💻☎ WinUI Community Call: August 18, 2021 #5482

Closed anawishnoff closed 3 years ago

anawishnoff commented 3 years ago

This live event has now ended, but you can view the recording on YouTube at the link below. If you didn't get your question answered, feel free to open it up as a question on this repo. Thanks all for joining!

https://youtu.be/RcA89AnGdJw

Details

Date: Wednesday, August 18, 2021 Time: 16:00-17:00 UTC (9:00-10:00am Pacific)

Anyone and everyone is welcome - no pre-registration is required. This will be an informal interactive live stream directly with members of our engineering team.

Format

The community call is a call among the WinUI team that is live-streamed onto YouTube. We present on new updates, share information, welcome guests, and answer your questions.

Agenda

Q&A Code of Conduct

Leave us your questions in the comments on this issue or live in the YouTube chat during the stream!

Lorymi commented 3 years ago

I am surprised when I see that winforms has started to receive updates, but wpf and uwp have become ghosts and no one is responsible for these two!

Four years ago, a request was made that we will read in 2021, it is funny (Especially for non-.NET developers) https://github.com/dotnet/wpf/issues/91

Instead of fixing the basic wpf and uwp problems, ask us about WINUI programs? I wish you cared about the desktop as much as you care about ASP

I think the biggest question right now is what will happen to UWP? Do you still avoid answering? Why should UWP be removed from the WINUI roadmap? And then tell us, maybe one day we will think about it again ?!

https://github.com/microsoft/WindowsAppSDK/discussions/1055

Make no mistake, I'm a fan of Microsoft and .NET, but your decisions always disappoint us

Take a look at the Flutter project on github to see how active it is and how much people are helping to develop it. or ReactNative?? Now compare the two with MAUI and Xamarin!!!

The only reason is the name Microsoft because it always obsolete a system after a while and does not provide a reason for that

You will obsolete the same WINUI for another two years and put your users in a dilemma

groovykool commented 3 years ago

What should a UWP developer that uses Map Control, Win2D and Ink Canvas do considering UWP .NET and C# are 2 full versions behind?

Why should Desktop apps that are currently in development using UWP or WPF (Desktop Bridge) move to WinUI3 and WindowAppSDK considering the huge number of bugs and missing functionality in them?

What are the current requirements for Desktop apps to be submitted to the Windows store?

robloo commented 3 years ago

Are additional controls still going to be open sourced and added here to the WinUI library? i.e. Grid source code, CommandBar source code, etc. Or are all controls not already here going to remain in WinUI3-only indefinitely.

Is there still a plan to open source WinUI3? I kind-of expect that promise to be revoked at this point. All the warning signs are there.

ghost1372 commented 3 years ago

When will we see WinUI 2.6 visual styles in WinUI 3? (i found answer) When will WinUI 3 the preview version 1.0 be released?

mrlacey commented 3 years ago

@anawishnoff As there's not going to be a July call, you might want to remove the scheduled YouTube entry: https://www.youtube.com/watch?v=KveLAGNafdw Also, the issue for the June call is still pinned in the repo.

anawishnoff commented 3 years ago

@mrlacey Thanks! Just addressed those issues.

pjmlp commented 3 years ago

With the release of Microsoft Game Developer Kit (GDK), UWP has been made into legacy from XBox team point of view:

UWP apps and games are community-supported only; partners inside Xbox managed programs (Xbox, Xbox Game Pass, Xbox Game Streaming) should use Microsoft Win32 + GDK.

HoloLens team is also moving away from UWP.

This article relates to the legacy WinRT native APIs. For new native app projects, we recommend using the OpenXR API.

Using XBox and HoloLens as examples why UWP still matters doesn't seem to be the case as per respective teams communication channels and own roadmaps.

So can we actually get an official coherent message on what is happening with UWP across the board?

Symbai commented 3 years ago

When can we expect new features for WPF? Just to name a few: Folder dialog, trimming support, AOT support, Acryl brush, Directx 11 + 12 support, bug-free WindowChrome class...

mrlacey commented 3 years ago

Question for the call (or anywhere else as an answer would be really enlightening) Apparently, it is by design that a read-only textbox looks the same as one that can be edited. Why is this the case? I think this is important because:

shaheedmalik commented 3 years ago

When is WinUI 3 coming to UWP?

When is WinUI 3 going to be open sourced?

Marv51 commented 3 years ago

From the last call:

Can you speak about CsWinRT again? It seems responsible for a large number of the really critical bugs. The team seems super small and future of WinUI seems to depend on getting CsWinRT right. Is the feeling of the team that the backlog of major bugs is decreasing?

Marv51 commented 3 years ago

What factors went into the decision to deviate from the planned "stable releases roughly every three months" to now having 5 months between 0.8 (June) and 1.0 (November). With the Windows 11 design refresh and the increasing amount of developer interest it seems like a sub-optimal time to hold features for a big 1.0 release.

To me a smaller 0.9 release in September would have been preferable.

pjmlp commented 3 years ago

@Marv51 Given the stagnation of C++/WinRT Visual Studio tooling in spite of Microsoft decided to deprecate C++/CX, 4 years ago, I wouldn't have higher expectations for CsWinRT to have a better future.

yoshiask commented 3 years ago

HoloLens team is also moving away from UWP.

This article relates to the legacy WinRT native APIs. For new native app projects, we recommend using the OpenXR API.

For what it's worth, it looks like OpenXR still uses UWP to some extent under the hood: https://github.com/microsoft/OpenXR-MixedReality/blob/main/samples/BasicXrApp/BasicXrApp_uwp.vcxproj

And the Mixed Reality Toolkit (which is used by all Hololens dev) still requires the UWP workload.

groovykool commented 3 years ago

When is WinUI 3 coming to UWP? Never

https://github.com/microsoft/microsoft-ui-xaml/issues/5484

yoshiask commented 3 years ago

There's really not much need for WinUI 3 on UWP. WinUI 2.x has most of the same features, and is still getting updates for the foreseeable future.

pjmlp commented 3 years ago

@yoshiask The UWP workload is for legacy applications.

https://docs.microsoft.com/en-us/windows/mixed-reality/develop/choosing-an-engine

And had you bothered to actually read the C++ source code from BasicXrApp instead of giving us the project file, you would have noticed that there is zero UWP code there, the sample has been migrated to OpenXR, and those UWP references are leftovers from the migration.

khdc commented 3 years ago

This might be a dumb question, but will you be sticking with the name "WinUI" moving forward, or is there any potential name changes since you are part of the Windows App SDK?

The reason why I ask, is that I am preparing to build my company's internal UX Toolkit and would hate to have my repo and namespaces have the WinUI name in them if it's going to change in the near future. 🤣

terrycox commented 3 years ago

There appear to be TreeView behavior changes from WinUI 3 0.5 and 0.8 as regards node selection. Can someone comment on this?

Lukespacewalker commented 3 years ago

When will Mica material be available in WinUI 3.0 ?

christiannagel commented 3 years ago

When can we expect a fix with the incompatibility of the Identity Client package?

5143

christiannagel commented 3 years ago

It would be great to have AppCenter support for WinUI #5343

JanRajnoha commented 3 years ago

WinUI currently have 2 critical bugs for me. The first is bug related to XAML Parse exception, which have many reasons why is thrown, and second is in CsWinRt related to null reference exception in PropertyChanged. This two bugs, for me, are only reason, why our app couldn't be released. I hope, you and CsWinRt team will solve it ASAP.

Marv51 commented 3 years ago

@christiannagel In https://github.com/microsoft/appcenter-sdk-dotnet/issues/1523 the AppCenter SDK has been working on WinUI and there is a promise to ship next month.

LadderLogic commented 3 years ago

Hello. Could y'all please post those links that were part of the stream here? The links didn't get through the youtube. I am specifically interested in Lifted Comp API documentation link. Cheers!

anawishnoff commented 3 years ago

Sure @LadderLogic - I think this is what we were trying to link you! Microsoft.UI.Composition Namespace

terrycox commented 3 years ago

My apologies for my earlier question. The Treeview behavior issue I thought I had was really a coding issue on my part. WinUI 3 marches on; keep up the good work.

terrycox commented 3 years ago

I had asked on the Github WCT discussion thread about the plan for the Toolkit to work with Windows App SDK 1.0 experimental. Here's the reply:

@michael-hawker michael-hawker 4 days ago Maintainer Author We're waiting for WinUI 3 to support the WinUI 2.6 styles as we just updated to reference those. Once WinUI 3 releases a preview or stable build with support for those, we'll release an updated version of the Toolkit packages for it.

Until then our current version is for the 0.8 release as per the WinUI release notes.

groovykool commented 3 years ago

There's really not much need for WinUI 3 on UWP. WinUI 2.x has most of the same features, and is still getting updates for the foreseeable future.

Quoting Ryan Demopoulos "As to why someone might target WinUI 3 today, there are several reasons and advantages: the mixture of Win32 support (for example, so you can use libraries & APIs that can’t be used in UWP), plus a modern set of Fluent controls & styles, plus Webview2, plus modern .NET, is a compelling combination for some app authors already."

pjmlp commented 3 years ago

Meanwhile they still don't know what to do with Win2D, and I expect another reboot if Windows 11 does another Windows 8.