Changes
= Basics =
There are predefined XAML templates available that can be overriddencustomized. If no override customizing is found, the default template templates will be used. Overrides need to be placed in the following folder: <br/><code>[App Installation Path]/LocalState/xaml/</code> (on Windows)
== Important =Overriding default XAMLs=Make sure to change On Windows (WinX/UWP), the extension to <code>[App Package Folder]/LocalState/xaml/</code> folder can be accessed by the user and the customized XAML files directly added. An alternative to this on all platforms (including Android, iOS, etc.) is to use the '''x'Import Customizing'' button in the app settings to achieve import the desired loading and overriding behavior!templates, styles, images, etc. (file by file, or all files within a zip package). The changes should be reflected in the UI (except the current page) without restarting the app. After directly editing the customizings (Xamarin.UWP), you can also use the "Reload customizing" button without restarting the app.
[[Image:setup-themes-file.png|frameless|600px|border]]
* Open it with the text editor of your choice and add remove everything within the '''ResouceDictionary''' except the following definition:
<syntaxhighlight lang="xml">
<Color x:Key="UBIKForegroundThemeColorUBIKLightThemeColor">blue</Color>
</syntaxhighlight>
* Save the changes and restart ''UBIK''reload. You should see changes successfully implemented:[[Image:ubik-with-blue-foreground.png {{Attention|frameless|border]]For maintainability reasons, it's HIGHLY recommended to deploy only those XAML resources you want to override. For example, if you only want to customize the UBIKChildArea, don't deploy others like the UBIKMenuArea. If you only want to customize the UBIKChildItem, that's the only content you should include in the UBIKThemes.}}
== Custom Templates ==
Custom templates can be added, just like on the WinX /UWP client. Make sure to save the file as xaml'''x''' and include all '''namespace definitions''' (as attributes of the '''ContentView''' tag), otherwise the custom template will not load.
Similar to the ''UBIKThemes.xamlx'' file, custom or overridden templates start with a <code><ContentView></code> tag containing all '''namespaces'''. <code><ContentView.Resources></code> takes a '''ResourceDictionary''' and contains resources like references to converters. Finally, <code><ContentView.Content></code> contains the actual layout content (it's best to start with a '''Grid'''). Again, don't forget to add namespaces that you need!
Templates can also be defined in ''UBIKThemes.xamlx''. In this case, they need to be added into the <code><ResourceDictionary></code> inside the <code><ContentView.Resources></code> template as a <code><DataTemplate></code>. Similarly, if you want to split up the templates into seperate files, you need to make sure to follow the steps mentioned above and get the content of the <code><DataTemplate></code> into the <code><ContentView.Content></code> tag. ''' {{Attention|Templates defined in separate files will override templates defined in the ''UBIKThemes.xamlx'' override templates defined in seperate files!'''}}
== Adding Images ==
Consider the following example:<br/>
A label saying ''There are no children items available!'' should only be visible if the number of children-items is 0.
= Advanced =