Closed mvegaca closed 3 years ago
Create apps using Windows UI Library 3 Preview 2 check WinUI doc to know the required development setup.
How have WinUI doc(s) been checked?
What knowledge has been gained of the required development setup? Is this documented anywhere?
Was this issue created to record that a mockup has been created or does it exist for any other specific purposes? If so, what are they?
"Create the mockup" is listed in the "next steps". How will this be different to what's in the referenced branch?
For the items in the list of Specs, pages, and features:
Has any consideration been given to reducing the coupling of ViewModels to views with these new templates? (X-Ref #2867)
I've noticed developers are increasingly putting their ViewModels in a .NET Standard library to enforce a reduced coupling of the ViewModel to the UI.
This doc explains the setup that you should install in your PC to develop WinUI3 apps, this setup was used to create the mockup.
Create Mockup is in the list of next steps (now renamed as Roadmap) and it's no marked as completed because there are some open issues and things that need to implement before creating templates (i.e. localized string resources, master-detail page or toast notification).
I'm not sure or how this templates will be included in the wizard, by this moment we should be focused in the mockup, the code and the integration with WinUI3 and WCT.
The list of initial pages and features was created using the list of most used templates in UWP and WPF platforms.
Win3UI will support Svg Icon in NavigationViewItem
Closing the issue in favor of #3810.
Create apps using Windows UI Library 3 Preview 2 check WinUI doc to know the required development setup.
The mockup is placed Mockup-WinUI3 branch.
Specs
Pages
Features
Roadmap
There are some issues on dev features or dev features that are not implemented yet and these are pending to be included in the mockup.
WinUI Known Issues
Windows Community Toolkit Issues