* The first step is to configure the start screen data using an xml in order for UBIK® to recognize the different tabs and buttons. The xml file should be placed in a subfolder under the "UBIK" folder on the device's SD card.
* After the folder is configured, the next step is to validate the schema against an online validator. A solution can be found at [http://www.utilities-online.info/xsdvalidation/ Online XML Schema Validator]. The schema used to validate against can will be found inside the UBIK Folder and is named ConfigurableStartScreenSchema.
The following xml shows an example configuration:
<source lang="xml">
<StartScreenConfiguration>
<Tab caption="Content">
<ContentBrowserButton caption="Content Browser"/>
<ContentBrowserButton caption="My Tasks" UBIK-UID="5baf5be8-ed79-11e3-83b1-82687f4fc15c" iconPath="tasks.png"/>
</Tab>
<Tab caption="AR">
<MapsButton/>
<PoiViewButton caption="AR View"/>
<CustomIntentButton caption="Map of Linz">
<IntentURI>
https://www.google.com/maps/place/Linz/@48.295065,14.327405,12z/data=!3m1!4b1!4m2!3m1!1s0x47739595fa99854d:0x7c53292c577975c4
</IntentURI>
</CustomIntentButton>
</Tab>
</StartScreenConfiguration>
</source>
== types of Tags == === StartScreenConfiguration Tag === === Tab Tag =Groups ==The user can configure up to 6 tabs groups in the XML. As parameters, the caption is needed.=== IDMarkerScanButton Tag =Buttons ===== QRCodeScanButton Tag ===Buttons should be placed inside tab elements and can be parameterized. Buttons are configurable in terms of:=== ConfigurableARButton Tag ====== CustomIntentButton Tag ====== ContentBrowserButton Tag ====== POIViewButton Tag ====== MapsButton Tag ====== ARNavigationButton Tag ====== MapsNavigationButton Tag === == '''Example''' ==** Icon** Caption** Group/tab** Action + Parameters if needed
=== Results ===
The result is that the tabs and buttons configured in the XML file will be visible and open the right activity once they are clicked.
[[Category:How-To]]
[[Category:UBIK Client]]