{{indexmenu_n>1}}
====== APP Node ======
\\
Node in which the special and main features of the app will be defined in, for each and every one of the collections.   \\
\\

It is made of:
  - **Attributes** which provides that features.
  - **Nodes**.\\
\\

An example format would be the following one:\\
\\
<code xml>
    <app 
        prefix="gen" 
        version="0.0.28.390" 
        debug="false" 
        sql-debug="false" 
        
        keyboard-bar-visible="true" 
        keyboard-bar-bgcolor="C1B82F" 
        
        autologon="false" 
        load-wait="true" 
        screen-orientation="portrait" 
        resolution-width="720" 
        resolution-height="1280" 
        companycolor="#C1B82F" 
        forecolor="#FFFFFF" 
        entry-point="MenuPrincipal">
        
	<!-- El atributo strict-mode="true" indica al framework que revise el fichero .CSS en busca de errores -->
        <style url="default.css" strict-mode="true" />
        <style url="default-ios.css" conditions="ios" strict-mode="true" />
    	<style url="default_hor.css" conditions="phone:horizontal" strict-mode="true" />
    	<style url="default_hor.css" conditions="tablet:horizontal" strict-mode="true "/>
        
        <!-- También se pueden incluir aquí los ficheros vbs y js en lugar de hacerlo en la colección de empresas -->
        <include file="funciones.js" language="javascript" />
        
        <connection name="mtto" connstring="bd/gestion.db" />
        
        <!-- Conexión con la BD de réplica de ficheros (Solo Android)-->
        <connection name="Info_ReplicaFiles" connstring="Provider=Xone Remote Provider;Data Source=local;ProgID=com.xone.db.impl.replicafiles.RplFilesConnection;DBMS Name=Ibd;User Name=sa;Password=;appname=ClientMobility;Timeout=60" prefix="" />
         
        <!-- Colección de Login Personalizada, que puede ser un fichero XML externo al mappings --> 
        <!-- Este nodo viene a sustituir al atributo login-coll="true" que se especificaba en el nodo coll de la colección de login,
             de forma que así tenemos mejor localizada la colección de login, además de poder especificar condiciones y llamar a un login u otro... -->
        <login-coll>
		<item name="LogonColl" conditions=""></item>
	</login-coll>

	<!-- Este nodo también viene a sustituir al atributo entry-point="ColeccionEntrada" que se definía en el nodo app. 
             También aquí podemos especificar condiciones para que entre en una colección u otra -->
	<entry-point>
		<item name="portadaQ" />
		<item name="portadaQTH" conditions="tablet:horizontal" />
		<item name="portadaQ" conditions="phone;hiphone" />
	</entry-point>
    
    </app>

</code>
\\
**NODE ATTRIBUTES:**\\
\\

|< 85% 15% - >|
^ATTRIBUTE^DESCRIPTION^
|**prefix**|Node to define the  ##PREF## macro, it is used in the SQL of the  mappings collections.|
|**version**|Definition of the mappings version. The <nowiki>XOnestudio</nowiki>, when saving the mappings, automatically increases this number, un such way that we will be able to have the control of versions.|
|**companycolor**|To define a general color for the whole app. They are colors applied to the tabs menus or selections, as long as in that places we cannot any colors for that areas.  Colors are passed.|
|**forecolor**|The texts color in general way. Colors are indicated. |
|**compatibility-mode**  |Mode in compatibility with previous versions. It is good to use it if we have an app made with previous versions of other frameworks, in order the view hasn´t a dramatic change.  “true” or “false” values. By default, “false”.|
|**hardware-keyboard**|Automatically showing or not the keyboard in the device, for this it is put to “true”, so we are indicating that the device has a hardware keyboard and then it doesn´t show the keyboard whenever we are placed in a field. It is only valid for the WM framework . By default is “false”.|
|**debug**|It is indicated to the framework that it is been executing in debug mode, so it will show us more information. This is for  "Android" device, when we are working in debugging mode or with the <nowiki>:XOnestudio</nowiki>.  “true” or “false” values, by default “false”.|
|**sql-debug**|It is indicated to the framework that log every SQL that are running in the framework. “true” or “false” values, by default “false”.|
|**entry-point**|The framework is indicated that the entry to the app it is not appwizard anymore, but it is the collection name passed in this attribute. It is useful for making a customized menu.|
|**screen-orientation**|The framework is forced to always show the app in landscape mode or in portrait mode. The values can be landscape or portrait.  For instance: screen-orientation="portrait".|
|**resolution-width**|When we put values in POINTS as for example the width of a button (Ex:width="35p"), by changing resolution and taking another device, we want that value be  "relative" and that find out automatically the correction factor for the new device.  That is, we have to put the resolution which we have developed the app for, (For instance: resolution-width="320"), so that if we use  a device that has a resolution of 640 wide, it must multiply by 2 all the  width specified in points.|
|**resolution-height**|Same than in the previous one, it is to relativize the sizes specified in points, by indicating the "original" resolution for which the app was created and it was "ok", so that the  framework recalculate sizes when it is into another device with another resolution different than the "original" one.  |\\
|**hypermedia**| **true** or **false** value (the //false// value is the default one). If it is **true** it enables the  optimizations for the hipermedia apps. **THIS FRAMEWORK IS  COMMERZIALIZED SEPARATELY**|\\
|**fullscreen**| **true** or **false** values (the //false// value is the default one). If it is **true** the app will be displayed in full screen by hiding the status bar of the mobile device. For instance: in the iPad the bar with time and battery status. |\\
|**autologon**| **true** or **false** value (the  //false// value is the default one ). This attribute controls automatic login for applications that do not need it. To make it work it is necessary to have an admin user with an empty password in the database. |\\
|**use-analytics**|**true** or **false**  values (the//false//  value is the default one).|\\
|**analytics-type**|**google** or **nielsen** values (http://www.google.com/intl/es/analytics/ or http://es.nielsen.com/products/ac.shtml).|\\
|**analytics-nielsen-domain**|**string** value. url with the domain name by following the Nielsen specifications for native apps. |\\
|**analytics-uid**|**string** value. It indicates the UID for Google analytics or the **client id** for Nielsen.| 
|**default-language**|**string** value. It indicates the language by default for the scripts if it is not specified in the tag where the script is defined. (vbscript or javascript).| 
\\
\\
** iOS EXCLUSIVE ATTRIBUTES **
|< 85% 15% - >|
^ATTRIBUTE^DESCRIPTION^
|**google-api-enable**|true or false. By default, iOS uses the Apple services to locate the coordinates we are going to show in a contents of <nowiki>mapview</nowiki> type. If we want to use the Google APIs for a better location and that the location be exactly the same than in Android, we must put this attribute to true.|
|**google-api-key**|Here, we will put the value of the key API that Google provides us in order to use its services, if the attribute is to true, we must specify a value.|
\\
\\
**SUBNODES OF THE **APP** NODE AND ITS ATTRIBUTES:**\\
\\
==== <login-coll> Node ====
\\
Node that points to the collection for login in the app. \\
\\
|< 65% 10% - >|
^ATTRIBUTE^DESCRIPTION^
|**name**|The name of the collection that will be our login window. <wrap hi>Case Sensitive</wrap>.|
|**conditions**|Same condition as the other nodes. (Orientation, platform/OS, Phone/tablet) |
\\
<code xml>
<!-- Colección de Login Personalizada, que puede ser un fichero XML externo al mappings --> 
<!-- Este nodo viene a sustituir al atributo login-coll="true" que se especificaba en el nodo coll de la colección de login,
     de forma que así tenemos mejor localizada la colección de login, además de poder especificar condiciones y llamar a un login u otro... -->

<login-coll>
	<item name="LogonColl" conditions=""></item>
</login-coll>

</code>
==== <entry-point> Node ====
\\
Node that points to the main menu collection. \\
\\
|< 65% 10% - >|
^ ATTRIBUTE ^ DESCRIPTION ^
|**name**|Name of the main menu collection. <wrap hi>Case Sensitive</wrap>.|
|**conditions**|Same conditions as the other nodes. (Orientation, platform/OS, Phone/tablet) |
\\

<code xml>
<!-- Este nodo también viene a sustituir al atributo entry-point="ColeccionEntrada" que se definía en el nodo app. 
     También aquí podemos especificar condiciones para que entre en una colección u otra -->
<entry-point>
	<item name="portadaQ" />
	<item name="portadaQTH" conditions="tablet:horizontal" />
	<item name="portadaQ" conditions="phone" />
</entry-point>
</code>
\\

==== <style> Node====
\\
Node to define the CSS used in the app.\\
\\
|< 65% 15% - >|
^ATTRIBUTE^DESCRIPTION^
|**url**|It indicates the CSS file name that it is going to be used in the app. |
|**strict-mode="true"**|It makes the framework to parse the .CSS file looking for errors.|

\\
<wrap info>More info [[wiki:2.-desarrollo-app:2.3.-codigo:d.-estilos-css:start|here]]</wrap>
\\
\\


==== <battery> Node====
\\
Node to control the battery, by showing messages according the indications of its attributes.  \\
<wrap hi>**IMPORTANT**: It is only valid for the Windows Mobile framework.</wrap>\\
\\

|< 65% 10% - >|
^ATTRIBUTE^DESCRIPTION^
|**Limit3**|First warning message, by indicating that it has the percentage of battery that we put as value in the attribute. |
|**Limit2**|Second warning message, with the indicated percentage. |
|**Limit1**|Third and last warning message, by indicating that in some 5 seconds the app will be closed in a controlled manner. It may have any data loss, which will be those ones that are on screen and they have not been saved. Any other data wont be lost.|
\\