m |
(→XML Attributes Description) |
||
Line 17: | Line 17: | ||
| title="Attribute" | gn:data_columns_width{n} | | title="Attribute" | gn:data_columns_width{n} | ||
| title="Description" | Defines the width of each column from left to right that appears in listview | | title="Description" | Defines the width of each column from left to right that appears in listview | ||
− | + | Can be | |
* hardcoded, i.e. 50,50,50 | * hardcoded, i.e. 50,50,50 | ||
|- | |- | ||
| title="Attribute" | gn:data_columns_name{n} | | title="Attribute" | gn:data_columns_name{n} | ||
| title="Description" | Defines the names from left to right that will appear in header columns | | title="Description" | Defines the names from left to right that will appear in header columns | ||
− | + | Can be | |
* hardcoded, i.e. resident_nfcTagUid,resident_firstName | * hardcoded, i.e. resident_nfcTagUid,resident_firstName | ||
* <code>@string</code> | * <code>@string</code> | ||
Line 28: | Line 28: | ||
| title="Attribute" | gn:data_columns_settings{n} | | title="Attribute" | gn:data_columns_settings{n} | ||
| title="Description" | Defines the settings for each column from left to right that is displayed in listview. | | title="Description" | Defines the settings for each column from left to right that is displayed in listview. | ||
− | + | If there is a single column to be shown in listview there is no separator between settings for columns. | |
− | + | ||
− | + | If there are 2 or more columns whose settings should be configured “pipe” (<code>|</code>) is used to separate them i.e. “<code>settingsColumn1|settingsColumn2|…</code>”. | |
− | + | ||
+ | Can be | ||
* <code>format</code> – converting long to human readable date and time, correct formats [http://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html here] | * <code>format</code> – converting long to human readable date and time, correct formats [http://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html here] | ||
|- | |- | ||
| title="Attribute" | gn:data_columns_id{n} | | title="Attribute" | gn:data_columns_id{n} | ||
| title="Description" | Defines column identifiers | | title="Description" | Defines column identifiers | ||
− | + | ||
− | + | If the data is loading from a <code>dbRequest</code> that has columns i.e. <code>name, surname</code>, to read that data to listview your columns should have same id’s <code>surname, name</code>. Note that the order here is not important. | |
+ | |||
+ | Can be | ||
* hardcoded, i.e. resident_nfcTagUid,resident_firstName | * hardcoded, i.e. resident_nfcTagUid,resident_firstName | ||
* <code>@string</code> | * <code>@string</code> | ||
Line 43: | Line 46: | ||
| title="Attribute" | gn:data_columns_type | | title="Attribute" | gn:data_columns_type | ||
| title="Description" | Defines cell type for each row which will display data | | title="Description" | Defines cell type for each row which will display data | ||
− | + | Can be | |
* <code>text</code> | * <code>text</code> | ||
* <code>pictures</code> | * <code>pictures</code> | ||
Line 52: | Line 55: | ||
| title="Attribute" | gn:data_filters{n} | | title="Attribute" | gn:data_filters{n} | ||
| title="Description" | Defines filter parameter to sort data | | title="Description" | Defines filter parameter to sort data | ||
− | + | ||
− | + | Once data is loaded into <code>GnListView</code>, it can be filtered by defining filter parameter. | |
+ | |||
+ | Filters are separated by <code>,</code> (comma symbol) and they have special syntax. More about filters [[#Filtering|here]]. | ||
|- | |- | ||
| title="Attribute" | gn:data_columns_sort{n} | | title="Attribute" | gn:data_columns_sort{n} | ||
| title="Description" | Defines column by which data will be sorted | | title="Description" | Defines column by which data will be sorted | ||
− | + | ||
− | + | Currently, sorting only accepts ascending sort by columnID defined by value of this attribute. | |
+ | |||
+ | For example if dbRequest has columns: name,surname,timestamp, and name is set as a value for this attribute then all rows will be sorted ascending by name. | ||
|- | |- | ||
| title="Attribute" | gn:lstRefreshNoFilter | | title="Attribute" | gn:lstRefreshNoFilter | ||
| title="Description" | Defines that on refresh data will not be filtered (used only in special cases when business logic implementation is used) | | title="Description" | Defines that on refresh data will not be filtered (used only in special cases when business logic implementation is used) | ||
− | + | ||
− | + | This attribute is not relevant to designer and if developing a standard ginstr app then it can be omitted. | |
+ | |||
+ | Can be | ||
* <code>true</code> | * <code>true</code> | ||
* <code>false</code> | * <code>false</code> | ||
Line 69: | Line 78: | ||
| title="Attribute" | gn:lstExpandToFitChildren | | title="Attribute" | gn:lstExpandToFitChildren | ||
| title="Description" | Stretches <code>[[GnListView]]</code> to load all children without scroll | | title="Description" | Stretches <code>[[GnListView]]</code> to load all children without scroll | ||
− | + | Used only if listView is: <code>com.ginstr.widgets.internal.ExpandableHeightListView</code> in <code>control/widget_en_listview.xml</code>, if set to <code>true</code>, GnListView will stretch to load all children without scroll | |
− | + | ||
+ | Can be | ||
* <code>true</code> | * <code>true</code> | ||
* <code>false</code> | * <code>false</code> |
Revision as of 10:04, 27 March 2017
GnListView
- Widget XML tag
<com.ginstr.widgets.GnListView>
- Description
GnListView
is used to show data in a table appearance, with header on the top and data in rows with cells below.
XML Attributes Description
Attribute | Description |
---|---|
gn:data_columns_width{n} | Defines the width of each column from left to right that appears in listview
Can be
|
gn:data_columns_name{n} | Defines the names from left to right that will appear in header columns
Can be
|
gn:data_columns_settings{n} | Defines the settings for each column from left to right that is displayed in listview.
If there is a single column to be shown in listview there is no separator between settings for columns. If there are 2 or more columns whose settings should be configured “pipe” ( Can be
|
gn:data_columns_id{n} | Defines column identifiers
If the data is loading from a Can be
|
gn:data_columns_type | Defines cell type for each row which will display data
Can be
|
gn:data_filters{n} | Defines filter parameter to sort data
Once data is loaded into Filters are separated by |
gn:data_columns_sort{n} | Defines column by which data will be sorted
Currently, sorting only accepts ascending sort by columnID defined by value of this attribute. For example if dbRequest has columns: name,surname,timestamp, and name is set as a value for this attribute then all rows will be sorted ascending by name. |
gn:lstRefreshNoFilter | Defines that on refresh data will not be filtered (used only in special cases when business logic implementation is used)
This attribute is not relevant to designer and if developing a standard ginstr app then it can be omitted. Can be
|
gn:lstExpandToFitChildren | Stretches GnListView to load all children without scroll
Used only if listView is: Can be
|
Example
<com.ginstr.widgets.GnListView android:id="@+id/lstResidents" android:layout_width="match_parent" android:layout_height="match_parent" android:layout_gravity="center_horizontal" android:background="#e1e1e1" gn:data_columns_name="resident_nfcTagUid,resident_firstName,resident_lastName,resident_roomNo,resident_buildingCode" gn:data_columns_id="resident_nfcTagUid,resident_firstName,resident_lastName,resident_roomNo,resident_buildingCode" gn:data_columns_type="text,text,text,text,text" gn:serverTableGenerator="ignore" gn:lstRefreshNoFilter="true" gn:s_listSelector="#00000000" gn:custom_xml="customList_listview.xml" gn:custom_header_xml="residentsList_header.xml" gn:custom_row_xml="residentsList_row.xml" gn:complex_cell_layout="true" />
Filtering
- Once data is loaded from the database it can be filtered by a filter mechanism. You can also filter the data loaded into the
GnListView
by using the following filter types:
VALUE
WIDGET
KEYWORD
- Filters can also be chained by chain words:
AND
OR
- If the filters are chained then each of filter statements must be true in order to show some record that is in
GnListView
data. - i.e.
[@+id/widgetOne]|[=]|[columnOne],[AND]|[#today]|[=]|[timestamp],[AND]|[dog]|[=]|[columnAnimalType]
- The upper statement filters the
GnListView
in the following way: - IF the widget that has id “
@+id/widgetOne
” has a value equal to the value incolumnOne
in listview rows AND iftimestamp
value in listview rows is within today AND ifcolumnAnimalType
value in listview rows is equal to “dog
”, then the row from listview rows will be displayed inGnListView
.
- Based the example above, the filter chaining definition is:
[CHAIN WORD]|[FILTER],[CHAIN WORD]|[FILTER1]…
- General filter
[FILTER]
definition is: [VALUE]|[COMPARATOR]|[COLUMNID]
- Filters behave differently depending on the content of the
[VALUE]
field.
[VALUE]
field special characters
Special Character | Description |
---|---|
::
|
Defines range in VALUE (turns filter into RANGE filter) (not yet implemented) |
*
|
Equivalent to like |
#
|
Keyword identifier (turns filter into KEYWORD filter) |
@+id/
|
Widget id |
\
|
Escape character |
- In order to use special characters as standard text you need to escape them as follows:
\::
,\*
,\#
,\@+id/
or\\
Comparators
- Comparators define the relation between the two values that are being compared.
- The following comparators can be used to compare:
Comparator Symbol | Description | Value Types Allowed |
---|---|---|
=
|
Equals to values | STRING , NUMBER
|
c=
|
Case sensitive equals to values | STRING , NUMBER
|
>
|
Greater than value | NUMBER
|
Filters
Filter | Description |
---|---|
[VALUE] |
|
[WIDGET] |
|
[KEYWORD] |
|
pointer additional XML attributes
Attribute | Description |
---|---|
gn:data_source_request | id of query which will be used to get pointed value
|
gn:data_source_table | name of table which will get queried
|
gn:data_source_field | column of referenced table which we would like to display supported referencing columns of data type text
|
gn:data_source_keys | optional
query keys in case referenced table values need to be reduced. This optimises memory on large table loads.
|