As Jason said, you can either use Interface Builder (which is part of
xcode) with C#, or write it in code. Interface builder is really just
building a big object graph, so the result is pretty much the same.

How you do it depends on the app, and you can mix and match as needed.
If you are dealing with lists of data (and if you look closely, most
things on the iPhone ARE lists, see here:
http://tirania.org/blog/archive/2010/Feb-23.html and here:
http://docs.xamarin.com/ios/tutorials/MonoTouch.Dialog ) then learn a
bit about UITableViewController and how it works, then go use
MonoTouch.Dialog, which wraps it all up and makes it really easy to
use. It helps to atleast have a play with UITableViewController /
UINavigationController etc tho, as you then know how the engine works,
so to speak.

Either way, you are going to be using CocoaTouch, which is the same
API as you'd be using from Obj-C. If you have someone working with you
who knows CT, then they are going to be instantly at home (Assuming
they know C#). It's literally the same calls, with a different syntax:

UIView myView;
//init it
// use it....
[myView doSomething:1 withAnotherParameter:@"hello!"];

vrs

UIView myView;
//init it
//use it...
myView.DoSomething(1, "Hello!");

There are often a few differences, but it's more to make it look like
proper c#-style methods. The underlying stuff is the same.




On Mon, May 28, 2012 at 11:06 PM, dspw <[email protected]> wrote:
> Hi Nic,
>
> Amazing answers indeed. Thank you very much! I originally posted my
> questions on Stackoverflow, but was voted down as they apparently frown down
> on multiple questions.
>
> What you've said has put my mind more at ease about trying MonoTouch.
>
> My final question is in regards to building the GUI. Does MonoTouch have its
> own way of doing this, or should I stick to learning the Cocoa GUI? In fact,
> someone who will help me code the app uses objective C (and therefore
> probably uses CocoaTouch), so perhaps that would be preferable if possible.
> But then does it come down to the issue of mixing C# and objective C again?
>
> --
> View this message in context: 
> http://monotouch.2284126.n4.nabble.com/Misc-Qs-regarding-ease-of-porting-from-C-to-MonoTouch-tp4655053p4655079.html
> Sent from the MonoTouch mailing list archive at Nabble.com.
> _______________________________________________
> MonoTouch mailing list
> [email protected]
> http://lists.ximian.com/mailman/listinfo/monotouch



-- 
Nic Wise
t.  +44 7788 592 806 | @fastchicken | http://www.linkedin.com/in/nicwise
b. http://www.fastchicken.co.nz/

Earnest: Self-employed? Track your business expenses and income.
http://earnestapp.com
Nearest Bus: find when the next bus is coming to your stop. http://goo.gl/Vcz1p
mobileAgent (for FreeAgent): get your accounts in your pocket.
http://goo.gl/IuBU
Trip Wallet: Keep track of your budget on the go: http://goo.gl/ePhKa
London Bike App: Find the nearest Boris Bike, and get riding! http://goo.gl/Icp2
_______________________________________________
MonoTouch mailing list
[email protected]
http://lists.ximian.com/mailman/listinfo/monotouch

Reply via email to