I already start using mvvmcross and i want to learn how to use a master/detail navigation. I can't find MvxMasterDetailPage described in this solution.
I have spent two days trying to start a master/detail navigation and nothing. I wouold like to do it with Xamarin Forms; i don't want to create any other presenter class but use the MvxFormsDroidMasterDetailPagePresenter for android. I had tried create a MvxFormsDroidMasterDetailPagePresenter in setup and also use MvxMasterDetailViewModel and nothing work.
Can some one please explain me or guide me to others options. Thanks.
Related
I´m starting to develop a application with Xamarin.forms we have the mockups and we need to implement somethink like a pull up menu / accordion menu. This component have to show over the content of the main page. I found a sketch from someone who wants to make the same as I, but no one give him a solution
This is the mockup of the component that I want to implement
I´ve searched a lot but i can not find something similar to the component that I want. Can some one please tell me if is possible to have components like this in xamarin? maybe using a external library
Thanks in advance
But, earlier When I used to work in Xamarin.Forms, The Default MasterDetailPage was like as shown below:
So, I got confuse with the latest one and previous one default MasterDetailPage, both are completely different by the VIEW.
I think you probably use the new Xamarin Forms Template of Visual Studio 2017, there is a bug that the Master Detail template is no MasterDetail at all, but uses a TabbedPage
https://bugzilla.xamarin.com/show_bug.cgi?id=53141 they probably didn't fix this, or at least not in a correct way ... https://forums.xamarin.com/discussion/90256/wrong-project-problematic-pages-template-issue-in-vs2017
Instead please see and use this sample https://developer.xamarin.com/samples/xamarin-forms/Navigation/MasterDetailPage/ in order to use a correct MasterDetailpage template.
Xamarin Forms' Master Detail layout is just the same as as before.
I am currently learning app-building basics with Xamarin. My question is what is the difference between "Blank-App (iPhone)" and "Master-Detail App (iPhone)".
Thanks for taking the time to answer my question.
These are two different templates for you to choose.
Blank-App (iPhone) means you just create an empty project without storyboard, RootViewController or other extensions. You can customize it whatever you want. If you are new to Xamarin.iOS and unsure about what template to use, try to use Single View Application.
Master-Detail App (iPhone) means when you choose this template. System will automatically create a UISplitViewController with a default Detail and Master for you. So there's no need to configure the rootView. It's a type of showing the ViewController.
You can try to create these two template projects then run to see the difference between them.
Is there any View on Xamarin.Forms to use like wizard? I must use Xamarin.Forms (not Xamarin.Android). Any suggestions?
I have seen this post but it looks like a bit complicated to me (Xamarin step by step wizard android views)
Update 17.04.2019:
Beginning with Xamarin.Forms 4.0, there is a new CarouselView control! This makes my old answer obsolete.
Old answer (obsolete):
The closest to what you're looking for is a CarouselPage. It holds several pages and you can navigate between them by swiping the screen to the left or the right.
Unfortunately, CarouselPage doesn't contain indicators which show on which page you are right now. You will have to implement this on your own if you need it. Your best choise are Custom Renderers.
I'm trying to build a MonoGame view inside MvvmCross on Android,iOS and WP8. On Windows side it's relatively easy to use dependency properties as a binding target, but how can I achieve a cross platform data binding solution that I can use on all platform?
This was covered in a previous MvvmCross version - see Insert a Monogame view inside MvvmCross monodroid Activity
The technical details have changes a bit since that post, but the core of the advice remains the same - use inheritance to add data-binding.
For example, if you want to adapt a FooActivity or FooViewController base class so that it can be used for MvvmCross data-binding, then you need to:
inherit from FooActivity to provide EventSourceFooActivity - to do this you need to add event notifications like those shown in MvxEventSourceFragmentActivity.cs
inherit from EventSourceFooActivity to provide BindingFooActivity - to do this you need to add all the members like DataContext from MvxFragmentActivity.cs
The process for Touch/iOS is very similar, but with iOS specific events and members. Take a look at any of the Mvx*ViewController classes to see what is involved.
This technique is also discussed in: Integrating Google Mobile Analytics with MVVMCross