Hey SteveRichter. No. There's no CSS for XAML. Styles are easier than you might think. Maybe you want to watch this? https://mva.microsoft.com/en-US/training-courses/xaml-for-windows-10-controls-14482?l=HXmdQWKtB_1604819052 ">https://mva.microsoft.com/en-US/training-courses/xaml-for-windows-10-controls-14482?l=HXmdQWKtB_1604819052
Jerry is a Microsoft Developer Evangelist in Colorado.
|Coffeehouse||Windows 8 Apps: Xaml vs. HTML5||31||May 23, 2012 at 8:53AM|
Jan 28, 2016 at 1:32PM
This section does a great job of demonstrating the Hamburger Menu. That being said, there are some styling issues that impact accessibility. These issues are resolved in this implementation: https://github.com/Windows-XAML/Template10/blob/master/Template10%20(Library)/Controls/HamburgerMenu.xaml
At 6:00, I am 100% sure you mean "resilience" instead of resilence". But at the rate Azure is releasing new features, I would not surprised to see resilence showing up soon. Be a good name for a firewall service.
At 6:10 Harini is telling us how to handle a specific "is this phone" UI. These are referred to as tailored experiences. The basic idea is that you don't; instead, you determine when you want to have a one-handed experience and to query the diagonal size of the physical device. This is not a visual state solution. This is a query on load and a separate XAML view.
@mumair85: Prism for Windows Apps has transitioned to open source/community. There is a plan to rev it, yes.
Okay. I will publish this on my Blog so you can have the source. Give me a day or two. http://jerrynixon.com
What a great video Jerry, very informative, Unni and Ari where excellent.
WPF will be here when you’re ready to grow up.
Hey, that video was fun to make and there will be more coming. First, thanks for wording it like I still have some growing up to do. I like to agree. And we're also in agreement with the future viability of WPF.
That being said, the level of investment around WinRT-XAML is nothing to be ignored. Because it is important to Windows itself, WinRT-XAML will continue to evolve into a powerful successor of WPF over time. That is to say, Windows has traditionally employed several UI technologies but is now consolidating on XAML - not for apps but for the OS.
This makes WinRT-XAML the beneficiary of performance tuning and other capabilities that will eventually make it an equal or maybe better option for the WPF line of business developer. Windowing, Win32 access, cross -architecture, cross-platform, inking, touch, NUI, and more. As the modality of computers evolves, WinRT-XAML will be compelling. To cutting edge apps, this is already true. To others, it may take time for this transition. For some, it may never happen.
I'm certainly not disagreeing with your premise. It sounds like we are both WPF fans. But I do think there's a freight train around WinRT-XAML coming that shouldn't be ignored by developers. Thanks for your comments. Thanks for using the platform. Thanks for your contribution.
Think about things like Code Analyses, Memory Profiling, live XAML Tree, Code Coverage, Timeline and Power profiling, rock-solid third party controls, trusted enterprise design patterns with .Net - there's so much to love. So many reasons to lean toward it.
It's not an simple answer. Sometimes a web-based application is quicker to write and easier to deploy. But most line-of-business applications are not quick and easy. They take a team of developers months or years to write. They are secure, transactional, scalable, and significant. If I were writing the checks, I would commission many web-based apps. But the one that runs my business, the one where I bet the farm? I'd likely prefer solid, proven technologies like .Net - where thousands of Fortune 5,000 companies have led before me with proven success.
But, in the end, only you know your company and its variables.