1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
|
Writing the configuration file "config.xml"
===========================================
About "config.xml"
------------------
The file **config.xml** describes important data of the application
to the framework:
- the unique identifier of the application
- the name of the application
- the type of the application
- the icon of the application
- the permissions linked to the application
- the services and dependancies of the application
The file MUST be at the root of the widget and MUST be case sensitively name
***config.xml***.
The file **config.xml** is a XML file described by the document
[widgets].
Example of "config.xml"
-----------------------
Here is the example of the config file for the QML application SmartHome.
```xml
<?xml version="1.0" encoding="UTF-8"?>
<widget xmlns="http://www.w3.org/ns/widgets" id="smarthome" version="0.1">
<name>SmartHome</name>
<icon src="smarthome.png"/>
<content src="qml/smarthome/smarthome.qml" type="text/vnd.qt.qml"/>
<description>
This is the Smarthome QML demo application.
It shows some user interfaces for controlling an automated house.
The user interface is completely done with QML.
</description>
<author>Qt team</author>
<license>GPL</license>
</widget>
```
Standard elements of "config.xml"
---------------------------------
### The element widget
#### the attribute id of widget
The attribute *id* is mandatory (for version 2.x, blowfish) and must be unique.
Values for *id* are any non empty string containing only latin letters,
arabic digits, and the three characters '.' (dot), '-' (dash) and
'_' (underscore).
Authors can use a mnemonic id or can pick a unique id using
command **uuid** or **uuidgen**.
#### the attribute version of widget
The attribute *version* is mandatory (for version 2.x, blowfish).
Values for *id* are any non empty string containing only latin letters,
arabic digits, and the three characters '.' (dot), '-' (dash) and
'_' (underscore).
Version values are dot separated fields MAJOR.MINOR.REVISION.
### The element content
The element *content* is mandatory (for version 2.x, blowfish) and must designate a file
(subject to localisation) with its attribute *src*.
The content designed depends on its type. See below for the known types.
### The element icon
The element *icon* is mandatory (for version 2.x, blowfish) and must
be unique. It must designate an image file with its attribute *src*.
Known widget types and content
------------------------------
The configuration file ***/etc/afm/afm-launch.conf*** defines the types
of widget known and how to launch it.
Known types for the type of content are (for version 2.x, blowfish):
- ***text/html***:
HTML application,
content.src designates the home page of the application
- ***application/x-executable***:
Native application,
content.src designates the relative path of the binary
- ***application/vnd.agl.url***:
Internet url,
content.src designates the url to be used
- ***application/vnd.agl.service***:
AGL service defined as a binder,
content.src designates the directory of provided binders,
http content, if any, must be put in the subdirectory ***htdocs*** of the widget
- ***application/vnd.agl.native***:
Native application with AGL service defined as a binder,
content.src designates the relative path of the binary,
bindings, if any must be put in the subdirectory ***lib*** of the widget,
http content, if any, must be put in the subdirectory ***htdocs*** of the widget
- ***text/vnd.qt.qml***, ***application/vnd.agl.qml***:
QML application,
content.src designate the relative path of the QML root,
imports must be put in the subdirectory ***imports*** of the widget
- ***application/vnd.agl.qml.hybrid***:
QML application with bindings,
content.src designate the relative path of the QML root,
bindings, if any must be put in the subdirectory ***lib*** of the widget,
imports must be put in the subdirectory ***imports*** of the widget
- ***application/vnd.agl.html.hybrid***:
HTML application,
content.src designates the home page of the application,
bindings, if any must be put in the subdirectory ***lib*** of the widget,
http content must be put in the subdirectory ***htdocs*** of the widget
AGL features
------------
The AGL framework uses the feature tag for specifying security and binding
requirement of the widget.
The current version of AGL (up to 2.0.1, blowfish) has no fully implemented
features.
The features planned to be implemented are described below.
### feature name="urn:AGL:provides-binding"
Use this feature for each provided binding of the widget.
The parameters are:
#### param name="name"
REQUIRED
The value is the string that must match the binding prefix.
It must be unique.
#### param name="src"
REQUIRED
The value is the path of the shared library for the binding.
#### param name="type"
REQUIRED
Currently it must be ***application/vnd.agl.binding.v1***.
#### param name="scope"
REQUIRED
The value indicate the availability of the binidng:
- private: used only by the widget
- public: available to allowed clients as a remote service (requires permission+)
- inline: available to allowed clients inside their binding (unsafe, requires permission+++)
#### param name="needed-binding"
OPTIONAL
The value is a space separated list of binding's names that the binding needs.
### feature name="urn:AGL:required-permissions"
List of the permissions required by the widget.
Each required permission must be explicited using a <param> entry.
#### param name=[required permission name]
The value is either:
- required: the permission is mandatorily needed except if the feature
isn't required (required="false") and in that case it is optional.
- optional: the permission is optional
### feature name="urn:AGL:defined-permissions"
Each required permission must be explicited using a <param> entry.
#### param name=[defined permission name]
The value is the level of the defined permission:
- system:
- platform:
- partner
- public:
[widgets]: http://www.w3.org/TR/widgets "Packaged Web Apps"
[widgets-digsig]: http://www.w3.org/TR/widgets-digsig "XML Digital Signatures for Widgets"
[libxml2]: http://xmlsoft.org/html/index.html "libxml2"
[app-manifest]: http://www.w3.org/TR/appmanifest "Web App Manifest"
|
