Jump to: navigation, search

Changes


HowTo:Configure Start Screen Content

1,345 bytes added, 10:21, 31 July 2014
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"> <IntentURITargetURI> https://www.google.com/maps/place/Linz/@48.295065,14.327405,12z/data=!3m1!4b1!4m2!3m1!1s0x47739595fa99854d:0x7c53292c577975c4 </IntentURITargetURI> </CustomIntentButton> </Tab> </StartScreenConfiguration>
</source>
== Tab Groups ==
The user can configure up to 6 tabs 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
* 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 ==
109
edits