Monday, June 03, 2013

N=25 - Tabs - N+1 Days of MvvmCross

Following on from splitview presenters, this talk gives an introduction into using tabs on Xamarin.Android, Xamarin.iOS and WindowsPhone.


For WindowsPhone, we use a Panorama as the local equivalent of Tabs - and we also mention Pivots.


For iOS, we show how to use a custom presenter to perform navigation within a tab child.


For Android, we hint at a future discussion of Fragments, but for now we discuss only Activities.


The video is:






The code is at https://github.com/slodge/NPlus1DaysOfMvvmCross/tree/master/N-25-Tabbed


For more on the N+1 series, check out this excellent index - http://mvvmcross.wordpress.com/ - thanks Aboo!

2 comments:

  1. Hi, Stuart! Thanks for the great new video!
    However, personally, that would be more obvious to navigate to the "Great" view fully (not inside the tab) - I am not sure if that's not embarassing for users.
    But, anyway, still, a great explanation of the controllers logic.

    ReplyDelete
  2. As for any next videos. What do you think of something like the following as a material for next videos:
    views own logic in collaboration with Mvvm-model? I am surely understand that that's not directly Mvvm-pattern issue, but that would happen anyway. (That's like you can not ommit Javascript on client side when using ASP.NET MVC).
    I saw your explanative answer on stackoverflow (http://stackoverflow.com/questions/11053535/alerts-or-popups-in-mvvmcross/11074498#11074498), but that would be really useful to see those things in practice. I am sure, that part is very important (either in meaning of general pattern or just as a sample for each architecture).
    Example of such things is the following:

    If we have login, password fields and we left login empty, filled password and clicking Return (on iOS keyboard, for instance) button, then we should be focused to login, but if login is filled in, then forse "logging in" process. (In case we are trying to check "login" right in the code, it breaks "model-driven" approach a little bit, but if we check for "IsFilled" property in Model, then how do we know that we need to focus to login (but not password). That thing is a simple one, but might be commonly used as a concept.
    Thank you!

    ReplyDelete