0

How would I go about implementing something in C# for iOS, that looks and feels like the MonoTouch.Dialog controls, without actually using Monotouch.Dialog?

pravprab
  • 2,301
  • 3
  • 26
  • 43
Goober
  • 13,146
  • 50
  • 126
  • 195
  • Go, check the source of MT.Dialog (https://github.com/migueldeicaza/MonoTouch.Dialog) and then implement it differently. Not sure why you would want to do that, though. – Krumelur Feb 05 '14 at 11:46
  • What I mean is, if I were coding for example a Settings page, but using Objective C, it would be very straightforward to make it look like the Settings app in iOS. I can do the same using MonoTouch.Dialog, but I've had problems with the EntryElements not always working, so I wanted to know how to get that look/feel/functionality of the settings page, using C Sharp, but not using Monotouch.Dialog....if there's a way without writing loads and loads of code? Or is that the point? i.e. Is Monotouch.Dialog there because without using it, it's a lot of work to get that Settings style implementation? – Goober Feb 05 '14 at 13:40

1 Answers1

2

It is the same amount of code if you use ObjC or Xamarin.iOS. Just slightly different syntax.

Your alternatives are

  • MT.Dialog (if you want to do the UI in code). This will dramatically reduce the complexity and MT.Dialog was designed exactly for the creation of quick and simple settings screens. In most cases, you will want to subclass the predefined elements to get best results.
  • Static UITableViewCells if you want to use Interface Builder. This allows you to create your UI in IB (or the iOS Designer built into Xamarin Studio). You can find tutorials on the web, like this one.
Krumelur
  • 32,180
  • 27
  • 124
  • 263
  • So ultimately if I write the whole thing in code, without using IB and without using MT.Dialog, then the easiest way to make it look and feel like the usual iOS Settings app, is to use tables? – Goober Feb 06 '14 at 12:28
  • Exactly. But that's the most inconvenient way. – Krumelur Feb 06 '14 at 14:08