you can build UI either using IB/XCode or by doing it in code - MT doesn't provide any UI designer of its own, although it does have some helpers for doing common things like building UITableViews (via MT.Dialog)
either way, it relies upon the native iOS UI, so it is definitely in your interest to become familiar with what iOS provides. Reading Apple's HIG document is a good way to start. On Mon, May 28, 2012 at 5: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 >
_______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
