This topic provides information on how to customize a Mobile application and includes links to relevant examples.
This approach allows you to customize a DevExtreme widget by accessing a corresponding XAF Mobile wrapper . These wrappers are of the Dictionary<String, Object> type, and you can access them in the same way as WinForms and ASP.NET application controls. The Dictionary's keys coincide with the corresponding widget's property names.
Refer to the following topics to see examples of how to access and customize DevExtreme widgets using wrappers:
You should create a special folder in one of the following places before adding a Mobile Custom Module:
the Mobile application project
This is aimed at new Mobile Custom Module development. Since this Module is in the application project, you can load a new Module version by reloading a page in a browser without rebuilding the application.
In the MySolution.Mobile project, create a new Static folder and a modules subfolder in it. Set the XafMobileStaticFilesLocation key value to Static in the web.config file.
the Mobile module project
Select this option to integrate an existing ready-to-use Mobile Custom Module.
In the MySolution.Module.Mobile project, create a new resources folder (for example, MobileResources) with the modules subfolder. Implement the IMobileResourcesHolder interface in the module's ModuleBase descendant, the GetMobileResourcesRelativePath method should return the resources folder name.
Refer to the Resources in Mobile Applications topic for code examples of the scenarios mentioned above.
To add a new Mobile Custom Module to one of these folders, use the Template Gallery.
Each module consists of the following files by default:
Refer to the How to: Add an XAF Mobile Custom Module topic to see the full step-by-step instructions.
See examples of using Mobile Custom Modules in the following topics:
one the following methods used to register your script:
You can use XAF client-side API in scripts. We recommend that you know how an XAF Mobile client application is designed before using this API.
XAF Mobile client applications follow the general MVVM (Model-View-View Model) pattern principles and consist of the following components:
In addition to the View Model, Mobile client applications have a Global Model that provides application-level properties used to share data between Views.
The scheme below illustrates the interaction between the application's items:
The following topics demonstrates how to use the client-side API:
You can add a Cordova Plugin in your Mobile application to use native device capabilities. To do this, register a plugin in the Mobile application's PhoneGap configuration file. Refer to the How to: Use a Custom Plugin in a Mobile Application topic to learn how to add plugins to your Mobile application. To see more examples, refer to the following articles: