Press the Buzzer is based on the infamous Milgram Experiment. This brilliant song captures the entire essence of the experiment and the fall out from it, without ever losing its compelling folk rock rhythm.
Like nearly all her music, this one is highly recommended.
I’m feeling sorry for this guy that I press to shock
He gets the answers wrong, I have to up the watts
And he begged me to stop, but they told me to go
I press the buzzer, I press the buzzer…
I recently posted about obtaining data for purposes of creating demonstration programs.
That actually was written in service to today’s post, which will use that data to create a list of “people” and then allow you to search incrementally, as shown in the illustration; I typed “Jaco” and any name that contained Jaco was brought up.
This post shows two meaningful techniques: it reviews grouping and it demonstrates incremental searches.
I set out to write a post on Incremental Searching in Xamarin applications (which I will do next) but along the way I realized i need a goodly amount of data to search.
This is a problem that arises fairly often, so I wrote a quick and dirty solution which is not terribly generalizable but was fun nonetheless.
This marks the first in a series of postings on the Internet of Things (IoT). Come with me as I learn more about these emerging technologies which promise to revolutionize everything we do.
First, the obligatory introduction for those of you who have been living in a cave…
IoT is the use of web/network based everyday appliances and other, well, things. IoT represents vending machines that keep their own inventory, toasters that alert you when the toast is done, fire alarms that wake you while calling the fire fighters, and so much more.
IoT presents a significant opportunity for developers; a technology space that is growing rapidly, and in many directions at once. While the market may not yet support a substantial investment, this is a sector you want to track closely.
As you can probably tell from my previous posts, I love Xamarin.Forms; principally because of XAML and DataBinding. It is just easier to create a cross-platform (iOS, Android and Windows Phone) with Xamarin.Forms than any other way.
Sometimes however, you do need to reach down to the native code to accomplish something that just isn’t wrapped in Xamarin.Forms. One good example is dialing the phone. Let’s build an application that does just that.
Yet Another Podcast (YAP) had quite a run in its first iteration. We had (among many others), Scott Guthrie, Miguel de Icazza, Scott Hanselman, Charles Petzold, John Papa, Laurent Bugnion… the list is too long.
The last show, however, was last year, show #135 with Miguel de Icazza. It is time to restart, inviting industry leaders in the Xamarin and .NET world to come back and bring us up to date. So… our first new show will be May 13, and we’ll try for at least two shows per month.
I’m working on setting up a mailing list so that you can (optionally) be informed when a new show is available. At a minimum, we’ll be available through iTunes and Stitcher as well as this site.
If Xamarin programing is going to be how you make your living, then I highly recommend this list of hardware and software.
iOS, OSX, Android, Windows Phone, Windows
If you are going to develop on both Mac and Windows, it is painful to switch back and forth between machines.
Ideally, you’ll run Windows on a Mac, using Parallels or something similar. Parallels is the right thing, but you need hardware that will fully support dual operating systems.
But even a fully tricked out MacBookPro is not quite powerful enough to make this entirely painless. When compiling in Windows, I find that the Mac slows to a crawl.
The solution is to get serious and buy a MacPro (desktop) with enough memory (32GB) and enough Cores (6) to never experience a slow down. You’ll also want to get a lot of storage, I recommend at least a Terrabyte of Flash storage. This configuration will set you back just over $5,000.
15.4-inch MacBook Pro 2.3GHz Quad-core Intel i7 with Retina Display
16GB of memory and 512GB Flash drive.
It is one year old, in excellent condition and has 2 years left on AppleCare.
Cost me $3200, asking $1600.
Email to email@example.com or 339-201-6010
[Reason for sale, acquisition of another MacBook Pro, A Macbook Air and a MacPro. I gotta’ sell this or my wife will kill me. Save a life, call me.]
iOS has a very useful segmented control. It is, essentially, a set of radio buttons that look more like an array of normal buttons…
It would be great to have this on iOS and Android, and by the way I’d like it to work in Xamarin.Forms. So I set out to write it, and I did so the way I do, which is to first see if someone else has already done it(!) Sure enough, my buddy Venkata pointed me at Chris Pellett’s project on GitHub. It does, at least to a first approximation, exactly what I want.
My mistakes are part of your learning
(With apologies to Shawn)
Call it a sliding window, a drawer, a hamburger; it is the latest craze in navigation. You click on the ubiquitous icon of three lines and the page slides over to reveal… Well whatever you want. Often it reveals navigation choices.
So the question arises: how do you do this in Xamarin.Forms? I have looked at a number of sources and samples and have synthesized them into an approach I like.
Start with a Xamarin.Forms Application
The technique I’m going to describe is designed to work with Xamarin.Forms. All of the work is done in the PCL. Begin by creating a BaseContentPage which derives from ContentPage and adds a NavigationPageName. This will let pages identify themselves,
By now, all my friends and relatives know that if they receive an email, even from someone they know, they should not click on any links. (Danger, Will Robinson).
But I like sending links to important articles or videos. How can I help my friends and relatives feel safe and yet open the email.
Easy, I send each of my friends and family an email that says:
“Please check this email by writing back and asking if I really sent it, or even better by calling me at 339-201-6010 From now on, when I send you email with a link, I will put the word fadoodle* at the bottom, so that you know it is really from me. Please do the same if you are sending me a link”
*Fadoodle is any made up word and not the one I use
This simple mechanism reassures the recipient that the email really came from you. You can use any word, but you are best doing what you would do with a password: the longer the better.
There definitely are more secure ways to do this, but this is sufficiently secure for me, and it is painless.