livebox:xapflash

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revisionBoth sides next revision
livebox:xapflash [2015/07/28 09:19] – [Joggler xAP binaries] minerva9livebox:xapflash [2017/01/17 20:41] brett
Line 83: Line 83:
 </code> </code>
  
-This self extracting shell script will install the following onto your joggler.+This self extracting shell script will install the following onto your Joggler.
 <code> <code>
 / /
Line 138: Line 138:
 Your hostname for the Joggler by default is "atom" you can change this in /etc/hostname it will be used in the triple "dbzoo.atom.XAP-PROGRAM" Your hostname for the Joggler by default is "atom" you can change this in /etc/hostname it will be used in the triple "dbzoo.atom.XAP-PROGRAM"
  
-Starting the Joggler xap software+Starting the Joggler xAP software
 <code> <code>
 /etc/init.d/boot.d/S70boot.xap start /etc/init.d/boot.d/S70boot.xap start
Line 146: Line 146:
 ==== xAPFlash installation ==== ==== xAPFlash installation ====
  
-If you already have xapflash installed on your Joggler this will perform an upgrade of the graphics and application leaving your XML configuration files intact.  If you don't already have it installed, it will additionally modify a configuration file so that the LAUNCH icon appears on your Joggler dashboard.  A reboot will be required if installing for the first time.  UPDATE: I found that even if just upgrading you needed a reboot for the new version to load.+If you already have xAPFlash installed on your Joggler this will perform an upgrade of the graphics and application leaving your XML configuration files intact.  If you don't already have it installed, it will additionally modify a configuration file so that the LAUNCH icon appears on your Joggler dashboard.  A reboot will be required if installing for the first time.  UPDATE: I found that even if just upgrading you needed a reboot for the new version to load.
  
 <code> <code>
Line 360: Line 360:
   * xapconfig.xml: ''<joggler> <layout> <background>''   * xapconfig.xml: ''<joggler> <layout> <background>''
   * xapconfig.xml: ''<joggler> <page> <background>''   * xapconfig.xml: ''<joggler> <page> <background>''
-  * xapconfig.xml: ''<joggler> <page> <textbox> <background>''+  * xapconfig.xml: ''%%<joggler> <page> <textbox> <background>%%''
   * config.xml: ''<joggler> <override> <layout> <background>''   * config.xml: ''<joggler> <override> <layout> <background>''
  
Line 381: Line 381:
   * L - Usable in the <layout> section   * L - Usable in the <layout> section
   * P - Usable in a <page> section   * P - Usable in a <page> section
-  * T - Usable in a <textbox> section+  * T - Usable in a %%<textbox>%% section
  
 ^ Tag ^ Key ^ Value ^ Description ^ ^ Tag ^ Key ^ Value ^ Description ^
Line 398: Line 398:
  
 Parent tag locations: Parent tag locations:
-  * config.xml: ''<joggler> <layout> <defaults>'' +  * config.xml: ''%%<joggler> <layout> <defaults>%%'' 
-  * xapconfig.xml: ''<joggler> <layout> <defaults>'' +  * xapconfig.xml: ''%%<joggler> <layout> <defaults>%%'' 
-  * config.xml: ''<joggler> <override> <layout> <defaults>''+  * config.xml: ''%%<joggler> <override> <layout> <defaults>%%''
  
 Here we establish the baseline for our visual components to create a common look and feel and to reduce the amount of repetition in their specification. Here we establish the baseline for our visual components to create a common look and feel and to reduce the amount of repetition in their specification.
Line 407: Line 407:
  
 ^^ Parent tag ^^ Allowed child tags ^^ Description ^^ ^^ Parent tag ^^ Allowed child tags ^^ Description ^^
-|| <label> || <font> <fontsize> <fontcolour> <alpha> <offset> || || +|| %%<label>%% || %%<font> <fontsize> <fontcolour> <alpha> <offset>%% || || 
-|| <bsctext> || <font> <fontsize> <fontcolour> <alpha>|| || +|| <bsctext> || %%<font> <fontsize> <fontcolour> <alpha>%%|| || 
-|| <button> || <font> <fontsize> <fontcolour> <alpha>|| || +|| %%<button>%% || %%<font> <fontsize> <fontcolour> <alpha>%%|| || 
-|| <textBox> || <font> <fontsize> <fontcolour> <alpha> <align> || || +|| %%<textBox>%% || %%<font> <fontsize> <fontcolour> <alpha> <align>%% || || 
-|| <time> || <font> <fontsize> <fontcolour> <alpha> <show> || || +|| <time> || %%<font> <fontsize> <fontcolour> <alpha> <show>%% || || 
-|| <button> || <style> <height> <width> <alpha> || ||+|| %%<button>%% || %%<style> <height> <width> <alpha>%% || ||
  
 Details about the children Details about the children
 ^^ Tag ^^ Description ^^ ^^ Tag ^^ Description ^^
-|| <font> || The name of a Font available from inside Flash. **Default: Verdana** ||+|| %%<font>%% || The name of a Font available from inside Flash. **Default: Verdana** ||
 || <fontsize> || the size of the font.  **Default: 14** || || <fontsize> || the size of the font.  **Default: 14** ||
 || <fontcolour> || A Hex triple in the format 0xRRGGBB \\ \\ Default: \\ label,textBox: 0xFFFFFF\\ bsctext,time: 0xFFFFCC || || <fontcolour> || A Hex triple in the format 0xRRGGBB \\ \\ Default: \\ label,textBox: 0xFFFFFF\\ bsctext,time: 0xFFFFCC ||
Line 423: Line 423:
 || <show> || valid values: true, false. **Default: true** || || <show> || valid values: true, false. **Default: true** ||
 || <offset> || This is the vertical offset of the label from its default - just below the button position (positive or negative, you can also use the word 'centre' to auto compute an offset. || || <offset> || This is the vertical offset of the label from its default - just below the button position (positive or negative, you can also use the word 'centre' to auto compute an offset. ||
-|| <style> || Defines the look and feel for the button.  see [[#the 'style' tag]] ||+|| %%<style>%% || Defines the look and feel for the button.  see [[#the 'style' tag]] ||
 || <width> || Default width || || <width> || Default width ||
 || <height> || Default height || || <height> || Default height ||
Line 485: Line 485:
  
 They maybe populated with any of the following child tags according to the usage key legend below They maybe populated with any of the following child tags according to the usage key legend below
-  * BT - ''<button>'' & ''<textbox>''+  * BT - ''<button>'' & ''%%<textbox>%%''
   * B - ''<button>'' only   * B - ''<button>'' only
-  * T - ''<textbox>'' only+  * T - ''%%<textbox>%%'' only
  
 ^ Tag ^ Key ^ Description ^ ^ Tag ^ Key ^ Description ^
Line 789: Line 789:
 No feedback from the endpoint can be rendered as part of the button's state, this is a fire-and-forget xAP message generator. No feedback from the endpoint can be rendered as part of the button's state, this is a fire-and-forget xAP message generator.
  
-<note important>The UID an SOURCE tags will be overwritten with the xAPFlash applications values however place holders for them must be present in the RAW xAP message and they cannot be omitted.</note>+<note important>The UID and SOURCE tags will be overwritten with the xAPFlash applications values however place holders for them must be present in the RAW xAP message and they cannot be omitted.</note>
  
 <code xml> <code xml>
Line 912: Line 912:
 | <background> | see [[#the 'background' section]]. | | <background> | see [[#the 'background' section]]. |
 | <alpha> | Alpha blending from 0.0 (transparent) to 1.0 (opaque).  ALL objects on the page will inherit this value. | | <alpha> | Alpha blending from 0.0 (transparent) to 1.0 (opaque).  ALL objects on the page will inherit this value. |
-| <visible> | Boolean to shows or hides the element at startup. Default: true |+| <visible> | Boolean to show or hide the element at startup. Default: true |
 | <group> | Only one member of a group can be active at once (radio group).  If a page in the group is made visible all others will be hidden. | | <group> | Only one member of a group can be active at once (radio group).  If a page in the group is made visible all others will be hidden. |
  
  • livebox/xapflash.txt
  • Last modified: 2017/01/17 21:35
  • by brett