Closed touseefbsb closed 7 years ago
@touseefbsb it will be. At the moment we're not building templates that target the preview SDK but will in time. Your request is quite generic. Do you have any specific requests? We already have an issue tracking changing to the new NavigationView at #308 There's also #306 too.
yeah I mainly wanted the navigation view to follow fluent design. but all other features of fluent design in general would be great. but yeah if you will support that after official release of the SDK that is perfect, looking forward to it :) @mrlacey
@touseefbsb we just got out of a meeting with the Fluent, XAML, and Composition teams. We're going to see how we can enable this direct while providing the support for the current release. Once we're on 15086 as our min target, we can do some more clever things.
yeah that right you guyx need to support all targets from 15086 upto 16190 ( preview sdk ) the code must be somehow adaptive already in the template to switch to page with splitview ( if user has window 10 older builds ) otherwise switch to fluent design system if user has creators fall update
I'm going to break this apart into the work back items we've identified. (https://github.com/Microsoft/WindowsTemplateStudio/wiki/Fluent
we have a branch for this.
I think we can close this in favor of small issues we currently have:
Closing as it is now we are ready for FCU and there are other issues tracking the details.
the new fluent design system introduced in insider preview windows SDK as showed in BUILD 2017 should be included in the template, with navigation control as "navigation view" control as it is present in latest preview SDK.