It doesn’t seem like a great idea to go into a series of posts talking about Metro-style apps without briefly defining the core components that they are built on. The most fundamental piece of the puzzle for these apps is Windows Runtime, or WinRT for short. WinRT is probably best described as an unmanaged, native API that can be leveraged from many different languages via a mechanism called language projection. Read more to find out some more details about how WinRT works.
Today is Stop SOPA Day and websites across the Internet are shutting down for the day and replacing their content with information regarding SOPA. Head over to Google or Reddit and join the cause. If you were hoping to look up information on Wikipedia or buy something on Craigslist you’ll be out of luck today.
SOPA and PIPA are very dangerous laws that inherently break the way the Internet works. Please join the cause by signing the petition or calling your Congressmen.
Which should you choose?
In the process of writing my first Windows 8 Metro style app using C# and XAML, I came across some limitations of the current WebView control’s implementation. The flow for the feature I was working on is fairly simple:
- Content for a webpage is displayed in a WebView (using the WebView’s Source property).
- User browses the page until they find something they want to save.
- User clicks a save button and the app parses the information into a readable format for saving in the app’s storage.
This is a pretty straightforward concept and I thought the implementation would be just as intuitive. Judging by the similarity of the WebView control to the Silverlight WebBrowser control, I went about implementing this functionality as I would have for Silverlight. I set the WebView’s Source property to the initial Uri where I wanted the browsing to begin. I wired up a test button that I thought would kick off the parsing process. That’s when I started to run into problems.