In the previous posting in this series we navigated to a details page, but the display of the details left a lot to be desired.  We had a single string of information and not enough room to display it in the UITableViewCell in the BookListTableView.

Today, we’ll take a look at customizing the UITableViewCell.  We return to the same code, but we’ll add a new class, BookCell that will derive from UITableViewCell.  This cell will be used to describe how we want each cell in the table to display its data.

Continued here

In the previous installment in this series, I left off with binding data. Today we take a look at page navigation and passing that data around.
Navigation with Storyboards is accomplished with Segues.  This process is so easy it is almost frightening.  Passing data is almost as easy.

Segues

To get started, return to the application we left off previously, and reopen MainStoryboard.storyboard.  Drag a Navigation controller onto the design surface and notice that it brings a second controller with it.  It may be necessary to use the zoom feature to make enough room to see all three controllers.  Delete the second controller yu just dragged onto the design surface, so that you end up with the Navigation controller and the original View Controller.

Continued here

The first three posts in this series were all about Xamarin Forms.  That is because Forms are terrific, convenient and new.  But they are not the only game in town. 

It is possible to write iOS applications using native controls and reap the benefit of a visual designer.  Let’s take a look at working with the Xamarin Storyboard.

This post is continued here.

Xamarin happily supports two-way binding, and the mechanism will be intensely familiar to XAML programmers. 

The more I work with Xamarin, the more I think this is where Silverlight went to heaven.

[ This is the third in a series that starts here.]

To illustrate this, let’s create a simple Forms application that provides two way binding of information about books.

Continued here

In my previous posting (the first in this series) I showed how to create a simple cross-platform mobile application using the new Xamarin forms.  In this posting, I will recreate that same application, but using XAML.

Once again, fire up Xamarin Studio (or Visual Studio). We’re going to reuse the Monkey class and the MonkeyVewModel that we used in the previous posting. 

When using XAML the data binding will be explicit and the use of a ViewModel will be even more important.  Continued…

Today I officially launch my new blog series on learning cross-platform mobile development with Xamarin. 

Xamarin should be perfect for me because

• I really want to learn iOS and Android programming but don’t want to code in Java or (God help me) Objective-C
• I have 14 years experience with C# and really like it
• Xamarin 3 looks amazing
• Forms! Forms! Forms!
• My computer is a MacBook Pro running Parallels
• I have a subscription to Xamarin University, which will ease the way considerably [1]

Forms are particularly appealing as an entry point because they use XAML and C#, which allows me to dig into my muscle memory from days gone by when I coded for Silverlight, WPF and Windows Phone.  So that is where I’ll start.  Continued…