Using UISearchBar with Xamarin iOS and MVVMCross - xamarin.ios

We have a standard SearchView - SearchViewModel binding that works in our Android and Windows Store apps.
There are various places in the app that call ShowViewModel to show the SearchViewModel. In this call we pass the Search Text.
We are now looking to reuse that same ViewModel in Xamarin.iOS.
The UISearchBar examples show the Search Bar filtering data in the current ViewModel.
I want to use it as a way of triggering a ShowViewModel, with the Search text being passed across to the SearchViewModel. That would then take the user from the current View to the Search View.
How do I trap the initiation of the Search so that I can pass the Search Text across to our SearchViewModel using ShowViewModel?

Related

Selector field displaying as free text acumatica mobile

I am trying to display WorkflowStage property as selector field just like in web application as screenshot below.
And this is the code that I have added in the xml file.
But still it gets rendered as a textbox field in mobile (free text) like this.
What is missing here?
As of right now, Acumatica mobile apps do not support Tree Selectors used in various screens inside Acumatica. Adding Workflow Stage as a text box field is the only possible way to add such fields on a mobile device.

Map application similar to Windows 10 maps using Template10

I want to design my map application using template 10 but the problem is i am using webview and want search and directons results on same page when splitview search button or directions button is clicked similar to Windows 10 maps app i dont want a master details page structure how to acheive this using template10
Edit 1:
Sorry for not being clear.I don't want search or direction on other page but on the same map page as a flyout same as in windows 10 maps.
How split view handles navigation and how back button is handled.Is it a page or a user control.
What you are wanting has already been demonstrated in the Search (and Login) project in the Samples folder on GitHub. http://aka.ms/template10. What you are asking is not uncommon, neither is it complex. I think reviewing the sample you will see how you need to construct your XAML.

Using a iOS UITabBar with MVVMCross MvxViewController not MvxTabBarViewController

We have a 4 views that are considered siblings in the UX design and so we would like to display them on a TabBar in iOS. We already have them in a NavigationDrawer in Android.
Lets call them
Customer
CustomerOrders
CustomerHistory
Returns
These are represented by 4 separate ViewModels. Looking at the MvxTabBarViewController samples I have to created a Uber ViewModel that exposes all 4 ViewModels as properties. Then attach the 4 views (MvxViewControllers) to a Parent View (MvxTabViewController).
UPDATE
I don't want to create a ViewModel just to support iOS' way of doing things.
I tried creating a UITabBar as a standalone view but that fails to deal with more than 5 items.
I have given up trying to fight the toolbar and am going to create a iOS specific ViewModel to host the Customer, CustomerOrders, CustomerHistory and Returns ViewModels. That is how the MvxTabViewController wants me to do it so I will. Getting that to work involves some MVVMCross configuration that I think is best handled by a new question. Once created I will link to it from here New question
Any suggestions?

Can I create a custom DialogPreference based on a pre-existing custom Dialog?

In my Android project I've already created a custom dialog: A class named SelectColorDialog, extending Dialog, that allows the user to view a large matrix of color cells in order to select a particular color. The dialog returns the selected color value (as Integer) to the dialog initiator – typically an Activity – via a callback function.
I've a similar custom dialog, SelectTypefaceDialog, to allow easy font selection. A list of available typefaces are shown, as ListView rows, each identified by name and with an associated short sample text rendered in that typeface. The available typefaces include usual droid fonts, such as NORMAL, MONOSPACE, etc. as well as any externally sourced TTF font files that the user cares to load into a particular subdirectory on the SDCard.
These custom dialogs were not initially designed to be used directly in conjunction with SharedPreferences, preferences definition XML files or with any PreferenceActivity. Instead of, each dialog can be popped up from any activity, via the user pressing a button or via a menu item. The activity classes that create these dialogs also have internal callback classes, selection event listeners, to detect when the user selects a color or font.
These two dialogs do not have OK and Cancel buttons. Instead, the user just clicks on an item - a view of some kind - in the dialog to select the corresponding color or typeface value (implicit OK) or else presses the device’s back button to dismiss the dialog with no action taken (implicit Cancel).
I would now like to go further and incorporate these two custom dialogs into the shared preferences framework via a preferences.XML and an associated PreferenceActivity.
I would prefer to base two DialogPreference subclasses directly on these existing dialogs if possible, but I cannot see how to do so. I suspect that I cannot, and that I'll need to start all over again, and copy or adapt all the java code that is presently in the custom dialog classes – for color or font display and selection – directly into the custom DialogPreference classes instead, perhaps by overriding onCreateDialogView() and/or other methods?
This question may be a bit old, but I hope to help those, looking at the same problem in future: just extend Preference instead of DialogPreference. DialogPreference is designed badly and expected "official" way to use custom Dialog - overriding protected showDialog method does not work, because this single method contains half of class logic.

Using an Outline with XPages Extension Library Mobile Controls

I am using the XPages Extension Library mobile controls to create a mobile web interface for an existing Notes app.
When displaying a document with a large number of fields I would like to use an accordion type UI so that parts of the page can be expanded or collapsed to show or hide the fields in each pane (similar to sections in a traditional Notes client app).
Having looked at the "Accordion Outline" in the Ext Lib demo app I started to build the page using the Outline control. Within each entry (node) of the Outline I, ideally, want to place a rounded list and then put my fields & controls inside that.
But it looks like the nodes in the Outline can't contain this type of content - unless I'm missing something?
Any suggestions as to which controls I can use this type of UI?
Thanks
You can any time use an xp:panel and assign it the dijit.accordeon (look up the exact name please) dojo type. Then you can put anything inside including repeat controls etc. I would guess it might make sense to build your own CC to hold the content for each accordeon panel

Resources