Jump to: navigation, search

Difference between revisions of "Xamarin XAML"


Line 5: Line 5:
 
== Basics ==
 
== Basics ==
 
There are predefined XAML templates available that can be overridden. If no override is found, the default template will be used.  
 
There are predefined XAML templates available that can be overridden. If no override is found, the default template will be used.  
Overrides need to be placed in the following folder (on Windows):  
+
Overrides need to be placed in the following folder:  
<span style="font-family: monospace;">'''[App Installation Path]/LocalState/xaml/'''</span>
+
<span style="font-family: monospace;">'''[App Installation Path]/LocalState/xaml/'''</span> (on Windows)
  
The overrides will be loaded during the startup of the app
+
The overrides will be loaded during the startup of the app.
 +
 
 +
== UBIKThemes.xamlx ==
 +
One of the most significant files is the ''UBIKThemes.xamlx'', as it is the place to override and extend '''global definitions'''.
 +
 
 +
The following paragraph showcases how easy it is to override global styles in ''UBIKThemes.xamlx''.
  
  
 
Override Styles
 
Override Styles

Revision as of 14:50, 1 July 2019

(WIP)

The User Interface of the Xamarin Clients (Android, iOS, new UWP) can be fundamentally customized using custom XAML definitions. This customization process is heavily influenced by the XAML Customization Process on the WinX Client.

Basics

There are predefined XAML templates available that can be overridden. If no override is found, the default template will be used. Overrides need to be placed in the following folder: [App Installation Path]/LocalState/xaml/ (on Windows)

The overrides will be loaded during the startup of the app.

UBIKThemes.xamlx

One of the most significant files is the UBIKThemes.xamlx, as it is the place to override and extend global definitions.

The following paragraph showcases how easy it is to override global styles in UBIKThemes.xamlx.


Override Styles