Difference between revisions of "HowTo:Configure Start Screen Content"
| Line 8: | Line 8: | ||
The following xml shows an example configuration: | The following xml shows an example configuration: | ||
<source lang="xml"> | <source lang="xml"> | ||
| − | <StartScreenConfiguration> | + | <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"> | |
| − | + | <TargetURI> | |
| − | + | https://www.google.com/maps/place/Linz/@48.295065,14.327405,12z/data=!3m1!4b1!4m2!3m1!1s0x47739595fa99854d:0x7c53292c577975c4 | |
| − | + | </TargetURI> | |
| − | + | </CustomIntentButton> | |
| − | + | </Tab> | |
| − | </StartScreenConfiguration> | + | </StartScreenConfiguration> |
</source> | </source> | ||
== Tab Groups == | == Tab Groups == | ||
| − | The user can configure | + | The user can configure tab groups in the XML. However the allowed number of tabs to configure may vary depending on the screen size of the device. As parameters, the caption is needed. |
== Buttons == | == Buttons == | ||
Buttons should be placed inside tab elements and can be parameterized. Buttons are configurable in terms of | Buttons should be placed inside tab elements and can be parameterized. Buttons are configurable in terms of | ||
| Line 33: | Line 33: | ||
* Group/tab | * Group/tab | ||
* Action + Parameters if needed | * Action + Parameters if needed | ||
| + | |||
| + | For now, the supported button types are the following, they are categorized based on their availability in specific projects: | ||
| + | |||
| + | UBIK.Android.UI: | ||
| + | • Content Browser Button | ||
| + | • Custom Intent Button (using a customized intent URI or target class) | ||
| + | UBIK.Android.Kernel.AR: | ||
| + | • Maps Activity (plus POI Layers, POI Groups and specific targets) | ||
| + | • ID Marker Scanning | ||
| + | • QR/Barcode Scanning | ||
| + | • POI View | ||
| + | |||
| + | Also, buttons should be configurable. They are placed as elements inside the tab element and can be parameterized. | ||
| + | 6.2.1 Button Types | ||
| + | |||
| + | The supported button types depend on the available features. Since different (customized) apps can be assembled from different features, it must be possible to extend the button types relatively dynamically as well. This has to be accounted for in the TD. For now, the supported button types should be the following: | ||
| + | |||
| + | UBIK.Android.UI: | ||
| + | • Content Browser Button | ||
| + | • Custom Intent Button (using a customized intent URI or target class) | ||
| + | UBIK.Android.Kernel.AR: | ||
| + | • Maps Activity Button | ||
| + | • ID Marker Scanning Button | ||
| + | • QR/Barcode Scanning Button | ||
| + | • POI View Button | ||
| + | • Configurable AR Button | ||
| + | UBIK.Android.ARNavigation: | ||
| + | • AR Navigation POI View Button | ||
| + | • AR Navigation Maps View Button | ||
| + | |||
| + | |||
== Results == | == Results == | ||
Revision as of 10:21, 31 July 2014
Contents
Introduction
The Dynamic Configurable start screen feature allows the UBIK Service engineer to tailor the buttons on the start screen according to the needs of the customer.
Setup
- 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 Online XML Schema Validator. The schema used to validate against will be found inside the UBIK Folder and is named ConfigurableStartScreenSchema.
The following xml shows an example configuration:
<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">
<TargetURI>
https://www.google.com/maps/place/Linz/@48.295065,14.327405,12z/data=!3m1!4b1!4m2!3m1!1s0x47739595fa99854d:0x7c53292c577975c4
</TargetURI>
</CustomIntentButton>
</Tab>
</StartScreenConfiguration>
Tab Groups
The user can configure tab groups in the XML. However the allowed number of tabs to configure may vary depending on the screen size of the device. As parameters, the caption is needed.
Buttons
Buttons should be placed inside tab elements and can be parameterized. Buttons are configurable in terms of
- Icon
- Caption
- Group/tab
- Action + Parameters if needed
For now, the supported button types are the following, they are categorized based on their availability in specific projects:
UBIK.Android.UI: • Content Browser Button • Custom Intent Button (using a customized intent URI or target class) UBIK.Android.Kernel.AR: • Maps Activity (plus POI Layers, POI Groups and specific targets) • ID Marker Scanning • QR/Barcode Scanning • POI View
Also, buttons should be configurable. They are placed as elements inside the tab element and can be parameterized. 6.2.1 Button Types
The supported button types depend on the available features. Since different (customized) apps can be assembled from different features, it must be possible to extend the button types relatively dynamically as well. This has to be accounted for in the TD. For now, the supported button types should be the following:
UBIK.Android.UI: • Content Browser Button • Custom Intent Button (using a customized intent URI or target class) UBIK.Android.Kernel.AR: • Maps Activity Button • ID Marker Scanning Button • QR/Barcode Scanning Button • POI View Button • Configurable AR Button UBIK.Android.ARNavigation: • AR Navigation POI View Button • AR Navigation Maps View Button
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.
