After the DC Earthquake of 2011, I became intrigued by the earthquake data exposed by the United States Geological Survey (USGS). During this time, I wrote my first app for the Windows Store that used USGS's earthquake data, Rumble Radar. Over the years, I have reused the data mainly for Spatial Data Visualization demos, but also as the basis of Xamarin, UWP and Windows Phone demos. What I failed to do, time and time again, was to build a reusable library for interacting with the USGS GeoJSON API. Therefore, I always had duplicated code in most of my demos which didn't necessarily add value to the topic or technology being showcased. That is why I wrote the UsgsClient library.
Updating Raspberry Pi apps in the field can be tricky. This post covers the general problem and address some specific side-loading problems you are likely to run into.
If you've ever clicked the "Decrypt HTTPS Traffic" button in Fiddler you know how extremely easy it is to initiate a man-in-the-middle attack, and watch (and even modify) the encrypted traffic between an application and a server. You can see passwords and app private information and all kinds of very interesting data that the app authors probably never intended to have viewed or modified.
It's also easy to protect against against man-in-the-middle attacks, but few apps do.
TL;DR - In the Package Manager Configuration, turn "Auto Update" OFF and make sure 1.3 is the selected version. Then, manually add the TV Extensions 3.0 repository to the Extensions SDK.
Horrifying. That about describes my first art class. As a computer science major with virtually no art experience I was surrounded by students who had devoted nearly every waking moment to drawing, painting, sculpting, and bending metal into non-functional shapes.
We love tools that help our clients save time,
Choosing the right tech stack for a project can be difficult. There are many factors that weigh in on which tools to use. Your team's proficiency in a language, available frameworks, hardware requirements, existing components, and many other variables help shape this decision.
For a recent project we build a WPF application to run on the windows 10 platform, but we were hoping to take advantage of some of the new hotness that didn't exist in Windows when WPF was created. Enter the Windows Desktop Bridge, or Project Centennial depending on how you google it.
- Maximize UI performance by reducing excess render cycles associated with traditional view nesting
- Increase maintainability and readability by removing ceremony and keeping layout code concise
- Simplify usage of RelativeLayout while increasing its power and abstracting away its quirks
In this post I’ll briefly explain what it is, then get into why we need a new UI framework in the context of each of the above three goals. I'll finish with limitations, some history, and how to get started.