Merge lp:~unity-api-team/indicator-network/connectivity-service-bindings-docs into lp:indicator-network/14.10

Proposed by Antti Kaijanmäki on 2014-08-15
Status: Merged
Approved by: Charles Kerr on 2014-08-19
Approved revision: 406
Merged at revision: 406
Proposed branch: lp:~unity-api-team/indicator-network/connectivity-service-bindings-docs
Merge into: lp:indicator-network/14.10
Prerequisite: lp:~unity-api-team/indicator-network/connectivity-service-bindings
Diff against target: 7239 lines (+6310/-334)
61 files modified
CMakeLists.txt (+5/-4)
debian/connectivity-doc.install (+1/-1)
debian/control (+12/-10)
debian/copyright (+41/-36)
doc/CMakeLists.txt (+27/-0)
doc/dbus/connectivity-api.txt (+26/-0)
doc/qt/CMakeLists.txt (+3/-0)
doc/qt/cpp/CMakeLists.txt (+40/-0)
doc/qt/cpp/Doxyfile.in (+2316/-0)
doc/qt/cpp/css/base.css (+638/-0)
doc/qt/cpp/css/qtquick.css (+772/-0)
doc/qt/cpp/css/reset.css (+8/-0)
doc/qt/cpp/css/scratch.css (+61/-0)
doc/qt/cpp/examples/CMakeLists.txt (+6/-0)
doc/qt/cpp/examples/example_networking_status.cpp (+86/-0)
doc/qt/cpp/pages/mainpage.dox (+18/-0)
doc/qt/cpp/pages/networking-status.dox (+35/-0)
doc/qt/cpp/pages/using.dox (+26/-0)
doc/qt/cpp/ubuntu-appdev-site-footer.html (+53/-0)
doc/qt/cpp/ubuntu-appdev-site-header.html (+35/-0)
doc/qt/qml/CMakeLists.txt (+41/-0)
doc/qt/qml/connectivity-qml.qdocconf.in (+55/-0)
doc/qt/qml/css/base.css (+638/-0)
doc/qt/qml/css/qtquick.css (+772/-0)
doc/qt/qml/css/reset.css (+8/-0)
doc/qt/qml/css/scratch.css (+61/-0)
doc/qt/qml/examples/example_networking_status.qml (+66/-0)
doc/qt/qml/pages/mainpage.qdoc (+25/-0)
doc/qt/qml/qml-api/NetworkingStatus.qml (+84/-0)
src/indicator/sim-unlock-dialog.cpp (+18/-0)
src/menumodel-cpp/action-group-exporter.h (+11/-12)
src/menumodel-cpp/action-group-merger.h (+11/-11)
src/menumodel-cpp/action-group.h (+11/-11)
src/menumodel-cpp/action.cpp (+11/-11)
src/menumodel-cpp/action.h (+11/-11)
src/menumodel-cpp/gio-helpers/util.cpp (+11/-11)
src/menumodel-cpp/gio-helpers/util.h (+11/-11)
src/menumodel-cpp/gio-helpers/variant.h (+11/-11)
src/menumodel-cpp/menu-exporter.h (+11/-11)
src/menumodel-cpp/menu-item.h (+11/-11)
src/menumodel-cpp/menu-merger.h (+11/-11)
src/menumodel-cpp/menu-model.h (+11/-12)
src/menumodel-cpp/menu.h (+11/-11)
src/notify-cpp/notification.cpp (+11/-11)
src/notify-cpp/notification.h (+11/-11)
src/notify-cpp/snapdecision/sim-unlock.cpp (+11/-11)
src/notify-cpp/snapdecision/sim-unlock.h (+11/-11)
src/qt/include/ubuntu/connectivity/NetworkingStatus (+0/-1)
src/qt/include/ubuntu/connectivity/networking-status.h (+54/-4)
src/qt/qml/Ubuntu/Connectivity/networking-status.h (+1/-1)
src/qt/src/CMakeLists.txt (+1/-2)
src/qt/src/networking-status.cpp (+1/-1)
src/url-dispatcher-cpp/url-dispatcher.cpp (+11/-11)
src/url-dispatcher-cpp/url-dispatcher.h (+11/-11)
tests/integration/qt/cpp/main.cpp (+10/-7)
tests/integration/qt/cpp/tst_networking.cpp (+1/-1)
tests/integration/qt/cpp/tst_networking.h (+0/-3)
tests/unit/menumodel-cpp/test-menu-exporter.cpp (+14/-13)
tests/utils/action-utils.cpp (+14/-13)
tests/utils/action-utils.h (+14/-13)
tests/utils/main.cpp (+14/-13)
To merge this branch: bzr merge lp:~unity-api-team/indicator-network/connectivity-service-bindings-docs
Reviewer Review Type Date Requested Status
Charles Kerr (community) 2014-08-15 Approve on 2014-08-19
PS Jenkins bot (community) continuous-integration Approve on 2014-08-19
Review via email: mp+230918@code.launchpad.net

Commit message

Documentation for the connectivity Qt C++ and QML API
Also fix licensing information.

To post a comment you must log in.
Antti Kaijanmäki (kaijanmaki) wrote :

This is a mere documentation branch. No actual code changes involded.
To test this branch, please check the contents of the produced .deb files and verify they are all populated and contain sane files.
Especially the connectivity-doc package is of interest.

Charles Kerr (charlesk) wrote :

I compared .debs using:

meld \
 <(dpkg -c build-area-trunk/indicator-network_0.5.1+14.10.20140808.2-0ubuntu1_i386.deb) \
 <(dpkg -c build-area-bindings-docs/indicator-network_0.5.1+14.10.20140808.2-0ubuntu1_i386.deb)

and all looks the same. LGTM

review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'CMakeLists.txt'
2--- CMakeLists.txt 2014-08-19 17:36:21 +0000
3+++ CMakeLists.txt 2014-08-19 17:36:21 +0000
4@@ -1,6 +1,8 @@
5 project(indicator-network C CXX)
6 cmake_minimum_required(VERSION 2.8.9)
7
8+string(TOLOWER "${CMAKE_BUILD_TYPE}" build_type_lower)
9+
10 set(CMAKE_MODULE_PATH "${CMAKE_SOURCE_DIR}/cmake" "${CMAKE_MODULE_PATH}")
11
12 find_package(PkgConfig REQUIRED)
13@@ -89,8 +91,7 @@
14 include_directories(${CMAKE_BINARY_DIR})
15
16 set(COMMON_FLAGS "-Wall -Wextra -Wpedantic -fno-permissive")
17-string(TOLOWER "${CMAKE_BUILD_TYPE}" BUILD_TYPE)
18-if(NOT BUILD_TYPE MATCHES debug)
19+if(NOT build_type_lower MATCHES debug)
20 set(COMMON_FLAGS "${COMMON_FLAGS} -Werror")
21 endif()
22
23@@ -112,7 +113,7 @@
24 # * Find html report in subdir coveragereport
25 # * Find xml report feasible for jenkins in coverage.xml
26 #####################################################################
27-IF(BUILD_TYPE MATCHES coverage)
28+IF(build_type_lower MATCHES coverage)
29 SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -ftest-coverage -fprofile-arcs" )
30 SET(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -ftest-coverage -fprofile-arcs" )
31 SET(CMAKE_MODULE_LINKER_FLAGS "${CMAKE_MODULE_LINKER_FLAGS} -ftest-coverage -fprofile-arcs" )
32@@ -124,9 +125,9 @@
33 set(CONNECTIVITY_QT_VERSION_MINOR 0)
34 set(CONNECTIVITY_QT_LIB_TARGET connectivity-qt${CONNECTIVITY_QT_VERSION_MAJOR})
35 add_subdirectory(data)
36-#add_subdirectory(doc)
37 add_subdirectory(src)
38 add_subdirectory(po)
39+add_subdirectory(doc)
40
41 enable_testing()
42 add_subdirectory(tests)
43
44=== modified file 'debian/connectivity-doc.install'
45--- debian/connectivity-doc.install 2014-08-19 17:36:21 +0000
46+++ debian/connectivity-doc.install 2014-08-19 17:36:21 +0000
47@@ -1,1 +1,1 @@
48-usr/share/doc/libconnectivity/*
49+usr/share/doc/connectivity-api/*
50
51=== modified file 'debian/control'
52--- debian/control 2014-08-19 17:36:21 +0000
53+++ debian/control 2014-08-19 17:36:21 +0000
54@@ -8,8 +8,10 @@
55 # make g++ version explicit for ABI safety, see https://wiki.ubuntu.com/cpp-11
56 g++-4.9,
57 debhelper (>= 9.0.0),
58- google-mock (>= 1.6.0+svn437),
59+ google-mock (>= 1.6.0+svn437),
60+ doxygen,
61 dbus-test-runner,
62+ graphviz,
63 libconnectivity-cpp-dev (>=0.0.1+14.10.20140709),
64 libdbus-cpp-dev (>= 4.0.0),
65 libglib2.0-dev,
66@@ -104,12 +106,12 @@
67 .
68 This package contains the qtdeclarative bindings for Ubuntu connectivity API.
69
70-#Package: connectivity-doc
71-#Section: doc
72-#Architecture: all
73-#Depends: ${misc:Depends},
74-# ${shlibs:Depends},
75-#Description: Unity Action API - documentation
76-# Ubuntu Connectivity API
77-# .
78-# This package contains developer documentation.
79+Package: connectivity-doc
80+Section: doc
81+Architecture: all
82+Depends: ${misc:Depends},
83+ ${shlibs:Depends},
84+Description: Unity Action API - documentation
85+ Ubuntu Connectivity API
86+ .
87+ This package contains developer documentation.
88
89=== modified file 'debian/copyright'
90--- debian/copyright 2013-04-08 19:10:46 +0000
91+++ debian/copyright 2014-08-19 17:36:21 +0000
92@@ -1,42 +1,47 @@
93 Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
94
95 Files: *
96-Copyright: 2013 Canonical Ltd.
97-License: GPL-3
98-
99-Files: secret-agent/*
100-Copyright: 2013 Canonical Ltd.
101-License: LGPL-3
102-
103-License: GPL-3
104- This program is free software: you can redistribute it and/or modify
105- it under the terms of the GNU General Public License version 3, as
106- published by the Free Software Foundation.
107- .
108- This program is distributed in the hope that it will be useful,
109- but WITHOUT ANY WARRANTY; without even the implied warranty of
110- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
111- GNU General Public License for more details.
112- .
113- You should have received a copy of the GNU General Public License
114- along with this program. If not, see <http://www.gnu.org/licenses/>
115- .
116- On Debian systems, the complete text of the GNU General
117- Public License version 3 can be found in "/usr/share/common-licenses/GPL-3".
118-
119-License: LGPL-3
120- This package is free software; you can redistribute it and/or modify
121- it under the terms of the GNU Lesser General Public License version 3,
122- as published by the Free Software Foundation.
123- .
124- This package is distributed in the hope that it will be useful, but
125- WITHOUT ANY WARRANTY; without even the implied warranty of
126- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
127- Lesser General Public License for more details.
128- .
129- You should have received a copy of the GNU General Public License
130- along with this program. If not, see <http://www.gnu.org/licenses/>
131- .
132+Copyright: 2014 Canonical Ltd.
133+License: GPL-3
134+
135+Files: src/dbus-cpp/*
136+Copyright: 2014 Canonical Ltd.
137+License: LGPL-3
138+
139+Files: src/notify-cpp/*
140+Copyright: 2014 Canonical Ltd.
141+License: LGPL-3
142+
143+Files: src/url-dispatcher-cpp/*
144+Copyright: 2014 Canonical Ltd.
145+License: LGPL-3
146+
147+Files: src/menumodel-cpp/*
148+Copyright: 2014 Canonical Ltd.
149+License: LGPL-3
150+
151+Files: src/qt/*
152+Copyright: 2014 Canonical Ltd.
153+License: LGPL-3
154+
155+Files: tests/integration/qt*
156+Copyright: 2014 Canonical Ltd.
157+License: LGPL-3
158+
159+Files: tests/menumodel-cpp/*
160+Copyright: 2014 Canonical Ltd.
161+License: LGPL-3
162+
163+Files: tests/utils/*
164+Copyright: 2014 Canonical Ltd.
165+License: LGPL-3
166+
167+License: GPL-3
168+ On Debian systems the full text of the GNU General Public
169+ License, version 3 can be found in the file
170+ '/usr/share/common-licenses/GPL-3'.
171+
172+License: LGPL-3
173 On Debian systems the full text of the GNU Lesser General Public
174 License, version 3 can be found in the file
175 '/usr/share/common-licenses/LGPL-3'.
176
177=== added directory 'doc'
178=== added file 'doc/CMakeLists.txt'
179--- doc/CMakeLists.txt 1970-01-01 00:00:00 +0000
180+++ doc/CMakeLists.txt 2014-08-19 17:36:21 +0000
181@@ -0,0 +1,27 @@
182+set(INSTALL_DOCDIR ${CMAKE_INSTALL_DATAROOTDIR}/doc/connectivity-api)
183+
184+if(build_type_lower MATCHES debug)
185+ option(BUILD_DOC "Build documentation by default" FALSE)
186+else()
187+ option(BUILD_DOC "Build documentation by default" TRUE)
188+endif()
189+option(PRIVATE_DOCS "Build private documentation" FALSE)
190+
191+if(${BUILD_DOC})
192+ set(IS_ALL ALL)
193+endif()
194+
195+add_subdirectory(qt)
196+set(DBUS_FILES
197+ dbus/connectivity-api.txt
198+)
199+
200+add_custom_target(doc ${IS_ALL}
201+ SOURCES ${DBUS_FILES}
202+)
203+add_dependencies(doc cppdoc qmldoc)
204+
205+install(
206+ DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}/dbus/
207+ DESTINATION ${INSTALL_DOCDIR}/dbus/
208+)
209
210=== added directory 'doc/dbus'
211=== added file 'doc/dbus/connectivity-api.txt'
212--- doc/dbus/connectivity-api.txt 1970-01-01 00:00:00 +0000
213+++ doc/dbus/connectivity-api.txt 2014-08-19 17:36:21 +0000
214@@ -0,0 +1,26 @@
215+Service com.ubuntu.connectivity1
216+Interface com.ubuntu.connectivity1.NetworkingStatus
217+Object path /com/ubuntu/connectivity1/NetworkingStatus
218+Policy group connectivity
219+Supports org.freedesktop.DBus.Introspectable
220+ org.freedesktop.DBus.Properties
221+
222+Properties array{string} Limitations [readonly]
223+
224+ String array representing the possible limitations
225+ on networking.
226+
227+ Currently available limitations are:
228+ "bandwith"
229+
230+ "bandwith" - indicates that the bandwith of the
231+ Internet connection has limitations.
232+ Applications should minimize their bandwith
233+ usage if possible.
234+
235+ string Status [readonly]
236+
237+ Status of the Internet connectivity.
238+
239+ Possible values:
240+ "offline", "connecting", "online"
241
242=== added directory 'doc/qt'
243=== added file 'doc/qt/CMakeLists.txt'
244--- doc/qt/CMakeLists.txt 1970-01-01 00:00:00 +0000
245+++ doc/qt/CMakeLists.txt 2014-08-19 17:36:21 +0000
246@@ -0,0 +1,3 @@
247+add_subdirectory(cpp)
248+add_subdirectory(qml)
249+
250
251=== added directory 'doc/qt/cpp'
252=== added file 'doc/qt/cpp/CMakeLists.txt'
253--- doc/qt/cpp/CMakeLists.txt 1970-01-01 00:00:00 +0000
254+++ doc/qt/cpp/CMakeLists.txt 2014-08-19 17:36:21 +0000
255@@ -0,0 +1,40 @@
256+add_subdirectory(examples)
257+
258+set(EXTRACT_PRIVATE NO)
259+set(INTERNAL_DOCS NO)
260+set(SOURCE_DIRS "${CMAKE_SOURCE_DIR}/src/qt/include ${CMAKE_CURRENT_SOURCE_DIR}")
261+
262+if(${PRIVATE_DOCS})
263+ set(EXTRACT_PRIVATE YES)
264+ set(INTERNAL_DOCS YES)
265+ set(SOURCE_DIRS "${SOURCE_DIRS} ${CMAKE_SOURCE_DIR}/src")
266+endif()
267+
268+set(DOC_FILES
269+ Doxyfile.in
270+ pages/mainpage.dox
271+ pages/using.dox
272+ pages/networking-status.dox
273+)
274+
275+find_package(Doxygen)
276+if(DOXYGEN_FOUND)
277+ configure_file(
278+ ${CMAKE_CURRENT_SOURCE_DIR}/Doxyfile.in
279+ ${CMAKE_CURRENT_BINARY_DIR}/Doxyfile @ONLY
280+ )
281+ add_custom_target(cppdoc
282+ ${DOXYGEN_EXECUTABLE} ${CMAKE_CURRENT_BINARY_DIR}/Doxyfile
283+ WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}
284+ COMMENT "Generating API documentation with Doxygen" VERBATIM
285+ SOURCES ${DOC_FILES}
286+ )
287+ install(
288+ DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}/html
289+ DESTINATION ${INSTALL_DOCDIR}/cpp/
290+ )
291+ install(
292+ DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}/xml
293+ DESTINATION ${INSTALL_DOCDIR}/cpp/
294+ )
295+endif(DOXYGEN_FOUND)
296
297=== added file 'doc/qt/cpp/Doxyfile.in'
298--- doc/qt/cpp/Doxyfile.in 1970-01-01 00:00:00 +0000
299+++ doc/qt/cpp/Doxyfile.in 2014-08-19 17:36:21 +0000
300@@ -0,0 +1,2316 @@
301+# Doxyfile 1.8.7
302+
303+# This file describes the settings to be used by the documentation system
304+# doxygen (www.doxygen.org) for a project.
305+#
306+# All text after a double hash (##) is considered a comment and is placed in
307+# front of the TAG it is preceding.
308+#
309+# All text after a single hash (#) is considered a comment and will be ignored.
310+# The format is:
311+# TAG = value [value, ...]
312+# For lists, items can also be appended using:
313+# TAG += value [value, ...]
314+# Values that contain spaces should be placed between quotes (\" \").
315+
316+#---------------------------------------------------------------------------
317+# Project related configuration options
318+#---------------------------------------------------------------------------
319+
320+# This tag specifies the encoding used for all characters in the config file
321+# that follow. The default is UTF-8 which is also the encoding used for all text
322+# before the first occurrence of this tag. Doxygen uses libiconv (or the iconv
323+# built into libc) for the transcoding. See http://www.gnu.org/software/libiconv
324+# for the list of possible encodings.
325+# The default value is: UTF-8.
326+
327+DOXYFILE_ENCODING = UTF-8
328+
329+# The PROJECT_NAME tag is a single word (or a sequence of words surrounded by
330+# double-quotes, unless you are using Doxywizard) that should identify the
331+# project for which the documentation is generated. This name is used in the
332+# title of most generated pages and in a few other places.
333+# The default value is: My Project.
334+
335+PROJECT_NAME = "Ubuntu Connectivity Qt API"
336+
337+# The PROJECT_NUMBER tag can be used to enter a project or revision number. This
338+# could be handy for archiving the generated documentation or if some version
339+# control system is used.
340+
341+PROJECT_NUMBER = @CONNECTIVITY_QT_VERSION_MAJOR@.@CONNECTIVITY_QT_VERSION_MINOR@
342+
343+# Using the PROJECT_BRIEF tag one can provide an optional one line description
344+# for a project that appears at the top of each page and should give viewer a
345+# quick idea about the purpose of the project. Keep the description short.
346+
347+PROJECT_BRIEF =
348+
349+# With the PROJECT_LOGO tag one can specify an logo or icon that is included in
350+# the documentation. The maximum height of the logo should not exceed 55 pixels
351+# and the maximum width should not exceed 200 pixels. Doxygen will copy the logo
352+# to the output directory.
353+
354+PROJECT_LOGO =
355+
356+# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path
357+# into which the generated documentation will be written. If a relative path is
358+# entered, it will be relative to the location where doxygen was started. If
359+# left blank the current directory will be used.
360+
361+OUTPUT_DIRECTORY =
362+
363+# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 4096 sub-
364+# directories (in 2 levels) under the output directory of each output format and
365+# will distribute the generated files over these directories. Enabling this
366+# option can be useful when feeding doxygen a huge amount of source files, where
367+# putting all generated files in the same directory would otherwise causes
368+# performance problems for the file system.
369+# The default value is: NO.
370+
371+CREATE_SUBDIRS = NO
372+
373+# If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII
374+# characters to appear in the names of generated files. If set to NO, non-ASCII
375+# characters will be escaped, for example _xE3_x81_x84 will be used for Unicode
376+# U+3044.
377+# The default value is: NO.
378+
379+ALLOW_UNICODE_NAMES = NO
380+
381+# The OUTPUT_LANGUAGE tag is used to specify the language in which all
382+# documentation generated by doxygen is written. Doxygen will use this
383+# information to generate all constant output in the proper language.
384+# Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Catalan, Chinese,
385+# Chinese-Traditional, Croatian, Czech, Danish, Dutch, English (United States),
386+# Esperanto, Farsi (Persian), Finnish, French, German, Greek, Hungarian,
387+# Indonesian, Italian, Japanese, Japanese-en (Japanese with English messages),
388+# Korean, Korean-en (Korean with English messages), Latvian, Lithuanian,
389+# Macedonian, Norwegian, Persian (Farsi), Polish, Portuguese, Romanian, Russian,
390+# Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish, Swedish, Turkish,
391+# Ukrainian and Vietnamese.
392+# The default value is: English.
393+
394+OUTPUT_LANGUAGE = English
395+
396+# If the BRIEF_MEMBER_DESC tag is set to YES doxygen will include brief member
397+# descriptions after the members that are listed in the file and class
398+# documentation (similar to Javadoc). Set to NO to disable this.
399+# The default value is: YES.
400+
401+BRIEF_MEMBER_DESC = YES
402+
403+# If the REPEAT_BRIEF tag is set to YES doxygen will prepend the brief
404+# description of a member or function before the detailed description
405+#
406+# Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
407+# brief descriptions will be completely suppressed.
408+# The default value is: YES.
409+
410+REPEAT_BRIEF = YES
411+
412+# This tag implements a quasi-intelligent brief description abbreviator that is
413+# used to form the text in various listings. Each string in this list, if found
414+# as the leading text of the brief description, will be stripped from the text
415+# and the result, after processing the whole list, is used as the annotated
416+# text. Otherwise, the brief description is used as-is. If left blank, the
417+# following values are used ($name is automatically replaced with the name of
418+# the entity):The $name class, The $name widget, The $name file, is, provides,
419+# specifies, contains, represents, a, an and the.
420+
421+ABBREVIATE_BRIEF =
422+
423+# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
424+# doxygen will generate a detailed section even if there is only a brief
425+# description.
426+# The default value is: NO.
427+
428+ALWAYS_DETAILED_SEC = NO
429+
430+# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
431+# inherited members of a class in the documentation of that class as if those
432+# members were ordinary class members. Constructors, destructors and assignment
433+# operators of the base classes will not be shown.
434+# The default value is: NO.
435+
436+INLINE_INHERITED_MEMB = NO
437+
438+# If the FULL_PATH_NAMES tag is set to YES doxygen will prepend the full path
439+# before files name in the file list and in the header files. If set to NO the
440+# shortest path that makes the file name unique will be used
441+# The default value is: YES.
442+
443+FULL_PATH_NAMES = NO
444+
445+# The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path.
446+# Stripping is only done if one of the specified strings matches the left-hand
447+# part of the path. The tag can be used to show relative paths in the file list.
448+# If left blank the directory from which doxygen is run is used as the path to
449+# strip.
450+#
451+# Note that you can specify absolute paths here, but also relative paths, which
452+# will be relative from the directory where doxygen is started.
453+# This tag requires that the tag FULL_PATH_NAMES is set to YES.
454+
455+STRIP_FROM_PATH =
456+
457+# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the
458+# path mentioned in the documentation of a class, which tells the reader which
459+# header file to include in order to use a class. If left blank only the name of
460+# the header file containing the class definition is used. Otherwise one should
461+# specify the list of include paths that are normally passed to the compiler
462+# using the -I flag.
463+
464+STRIP_FROM_INC_PATH = @CMAKE_SOURCE_DIR@/src/qt/include
465+
466+# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter (but
467+# less readable) file names. This can be useful is your file systems doesn't
468+# support long names like on DOS, Mac, or CD-ROM.
469+# The default value is: NO.
470+
471+SHORT_NAMES = NO
472+
473+# If the JAVADOC_AUTOBRIEF tag is set to YES then doxygen will interpret the
474+# first line (until the first dot) of a Javadoc-style comment as the brief
475+# description. If set to NO, the Javadoc-style will behave just like regular Qt-
476+# style comments (thus requiring an explicit @brief command for a brief
477+# description.)
478+# The default value is: NO.
479+
480+JAVADOC_AUTOBRIEF = NO
481+
482+# If the QT_AUTOBRIEF tag is set to YES then doxygen will interpret the first
483+# line (until the first dot) of a Qt-style comment as the brief description. If
484+# set to NO, the Qt-style will behave just like regular Qt-style comments (thus
485+# requiring an explicit \brief command for a brief description.)
486+# The default value is: NO.
487+
488+QT_AUTOBRIEF = NO
489+
490+# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make doxygen treat a
491+# multi-line C++ special comment block (i.e. a block of //! or /// comments) as
492+# a brief description. This used to be the default behavior. The new default is
493+# to treat a multi-line C++ comment block as a detailed description. Set this
494+# tag to YES if you prefer the old behavior instead.
495+#
496+# Note that setting this tag to YES also means that rational rose comments are
497+# not recognized any more.
498+# The default value is: NO.
499+
500+MULTILINE_CPP_IS_BRIEF = NO
501+
502+# If the INHERIT_DOCS tag is set to YES then an undocumented member inherits the
503+# documentation from any documented member that it re-implements.
504+# The default value is: YES.
505+
506+INHERIT_DOCS = YES
507+
508+# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce a
509+# new page for each member. If set to NO, the documentation of a member will be
510+# part of the file/class/namespace that contains it.
511+# The default value is: NO.
512+
513+SEPARATE_MEMBER_PAGES = NO
514+
515+# The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen
516+# uses this value to replace tabs by spaces in code fragments.
517+# Minimum value: 1, maximum value: 16, default value: 4.
518+
519+TAB_SIZE = 4
520+
521+# This tag can be used to specify a number of aliases that act as commands in
522+# the documentation. An alias has the form:
523+# name=value
524+# For example adding
525+# "sideeffect=@par Side Effects:\n"
526+# will allow you to put the command \sideeffect (or @sideeffect) in the
527+# documentation, which will result in a user-defined paragraph with heading
528+# "Side Effects:". You can put \n's in the value part of an alias to insert
529+# newlines.
530+
531+ALIASES = "accessors=\par Accessors:\n" \
532+ "initvalue=\par Initial Value:\n" \
533+ "notify=\par Notify:\n"
534+
535+# This tag can be used to specify a number of word-keyword mappings (TCL only).
536+# A mapping has the form "name=value". For example adding "class=itcl::class"
537+# will allow you to use the command class in the itcl::class meaning.
538+
539+TCL_SUBST =
540+
541+# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
542+# only. Doxygen will then generate output that is more tailored for C. For
543+# instance, some of the names that are used will be different. The list of all
544+# members will be omitted, etc.
545+# The default value is: NO.
546+
547+OPTIMIZE_OUTPUT_FOR_C = NO
548+
549+# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java or
550+# Python sources only. Doxygen will then generate output that is more tailored
551+# for that language. For instance, namespaces will be presented as packages,
552+# qualified scopes will look different, etc.
553+# The default value is: NO.
554+
555+OPTIMIZE_OUTPUT_JAVA = NO
556+
557+# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
558+# sources. Doxygen will then generate output that is tailored for Fortran.
559+# The default value is: NO.
560+
561+OPTIMIZE_FOR_FORTRAN = NO
562+
563+# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
564+# sources. Doxygen will then generate output that is tailored for VHDL.
565+# The default value is: NO.
566+
567+OPTIMIZE_OUTPUT_VHDL = NO
568+
569+# Doxygen selects the parser to use depending on the extension of the files it
570+# parses. With this tag you can assign which parser to use for a given
571+# extension. Doxygen has a built-in mapping, but you can override or extend it
572+# using this tag. The format is ext=language, where ext is a file extension, and
573+# language is one of the parsers supported by doxygen: IDL, Java, Javascript,
574+# C#, C, C++, D, PHP, Objective-C, Python, Fortran (fixed format Fortran:
575+# FortranFixed, free formatted Fortran: FortranFree, unknown formatted Fortran:
576+# Fortran. In the later case the parser tries to guess whether the code is fixed
577+# or free formatted code, this is the default for Fortran type files), VHDL. For
578+# instance to make doxygen treat .inc files as Fortran files (default is PHP),
579+# and .f files as C (default is Fortran), use: inc=Fortran f=C.
580+#
581+# Note For files without extension you can use no_extension as a placeholder.
582+#
583+# Note that for custom extensions you also need to set FILE_PATTERNS otherwise
584+# the files are not read by doxygen.
585+
586+EXTENSION_MAPPING =
587+
588+# If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
589+# according to the Markdown format, which allows for more readable
590+# documentation. See http://daringfireball.net/projects/markdown/ for details.
591+# The output of markdown processing is further processed by doxygen, so you can
592+# mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in
593+# case of backward compatibilities issues.
594+# The default value is: YES.
595+
596+MARKDOWN_SUPPORT = YES
597+
598+# When enabled doxygen tries to link words that correspond to documented
599+# classes, or namespaces to their corresponding documentation. Such a link can
600+# be prevented in individual cases by by putting a % sign in front of the word
601+# or globally by setting AUTOLINK_SUPPORT to NO.
602+# The default value is: YES.
603+
604+AUTOLINK_SUPPORT = YES
605+
606+# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
607+# to include (a tag file for) the STL sources as input, then you should set this
608+# tag to YES in order to let doxygen match functions declarations and
609+# definitions whose arguments contain STL classes (e.g. func(std::string);
610+# versus func(std::string) {}). This also make the inheritance and collaboration
611+# diagrams that involve STL classes more complete and accurate.
612+# The default value is: NO.
613+
614+BUILTIN_STL_SUPPORT = YES
615+
616+# If you use Microsoft's C++/CLI language, you should set this option to YES to
617+# enable parsing support.
618+# The default value is: NO.
619+
620+CPP_CLI_SUPPORT = NO
621+
622+# Set the SIP_SUPPORT tag to YES if your project consists of sip (see:
623+# http://www.riverbankcomputing.co.uk/software/sip/intro) sources only. Doxygen
624+# will parse them like normal C++ but will assume all classes use public instead
625+# of private inheritance when no explicit protection keyword is present.
626+# The default value is: NO.
627+
628+SIP_SUPPORT = NO
629+
630+# For Microsoft's IDL there are propget and propput attributes to indicate
631+# getter and setter methods for a property. Setting this option to YES will make
632+# doxygen to replace the get and set methods by a property in the documentation.
633+# This will only work if the methods are indeed getting or setting a simple
634+# type. If this is not the case, or you want to show the methods anyway, you
635+# should set this option to NO.
636+# The default value is: YES.
637+
638+IDL_PROPERTY_SUPPORT = YES
639+
640+# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
641+# tag is set to YES, then doxygen will reuse the documentation of the first
642+# member in the group (if any) for the other members of the group. By default
643+# all members of a group must be documented explicitly.
644+# The default value is: NO.
645+
646+DISTRIBUTE_GROUP_DOC = NO
647+
648+# Set the SUBGROUPING tag to YES to allow class member groups of the same type
649+# (for instance a group of public functions) to be put as a subgroup of that
650+# type (e.g. under the Public Functions section). Set it to NO to prevent
651+# subgrouping. Alternatively, this can be done per class using the
652+# \nosubgrouping command.
653+# The default value is: YES.
654+
655+SUBGROUPING = YES
656+
657+# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and unions
658+# are shown inside the group in which they are included (e.g. using \ingroup)
659+# instead of on a separate page (for HTML and Man pages) or section (for LaTeX
660+# and RTF).
661+#
662+# Note that this feature does not work in combination with
663+# SEPARATE_MEMBER_PAGES.
664+# The default value is: NO.
665+
666+INLINE_GROUPED_CLASSES = NO
667+
668+# When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and unions
669+# with only public data fields or simple typedef fields will be shown inline in
670+# the documentation of the scope in which they are defined (i.e. file,
671+# namespace, or group documentation), provided this scope is documented. If set
672+# to NO, structs, classes, and unions are shown on a separate page (for HTML and
673+# Man pages) or section (for LaTeX and RTF).
674+# The default value is: NO.
675+
676+INLINE_SIMPLE_STRUCTS = NO
677+
678+# When TYPEDEF_HIDES_STRUCT tag is enabled, a typedef of a struct, union, or
679+# enum is documented as struct, union, or enum with the name of the typedef. So
680+# typedef struct TypeS {} TypeT, will appear in the documentation as a struct
681+# with name TypeT. When disabled the typedef will appear as a member of a file,
682+# namespace, or class. And the struct will be named TypeS. This can typically be
683+# useful for C code in case the coding convention dictates that all compound
684+# types are typedef'ed and only the typedef is referenced, never the tag name.
685+# The default value is: NO.
686+
687+TYPEDEF_HIDES_STRUCT = NO
688+
689+# The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This
690+# cache is used to resolve symbols given their name and scope. Since this can be
691+# an expensive process and often the same symbol appears multiple times in the
692+# code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small
693+# doxygen will become slower. If the cache is too large, memory is wasted. The
694+# cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range
695+# is 0..9, the default is 0, corresponding to a cache size of 2^16=65536
696+# symbols. At the end of a run doxygen will report the cache usage and suggest
697+# the optimal cache size from a speed point of view.
698+# Minimum value: 0, maximum value: 9, default value: 0.
699+
700+LOOKUP_CACHE_SIZE = 0
701+
702+#---------------------------------------------------------------------------
703+# Build related configuration options
704+#---------------------------------------------------------------------------
705+
706+# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
707+# documentation are documented, even if no documentation was available. Private
708+# class members and static file members will be hidden unless the
709+# EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES.
710+# Note: This will also disable the warnings about undocumented members that are
711+# normally produced when WARNINGS is set to YES.
712+# The default value is: NO.
713+
714+EXTRACT_ALL = YES
715+
716+# If the EXTRACT_PRIVATE tag is set to YES all private members of a class will
717+# be included in the documentation.
718+# The default value is: NO.
719+
720+EXTRACT_PRIVATE = @EXTRACT_PRIVATE@
721+
722+# If the EXTRACT_PACKAGE tag is set to YES all members with package or internal
723+# scope will be included in the documentation.
724+# The default value is: NO.
725+
726+EXTRACT_PACKAGE = NO
727+
728+# If the EXTRACT_STATIC tag is set to YES all static members of a file will be
729+# included in the documentation.
730+# The default value is: NO.
731+
732+EXTRACT_STATIC = YES
733+
734+# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) defined
735+# locally in source files will be included in the documentation. If set to NO
736+# only classes defined in header files are included. Does not have any effect
737+# for Java sources.
738+# The default value is: YES.
739+
740+EXTRACT_LOCAL_CLASSES = YES
741+
742+# This flag is only useful for Objective-C code. When set to YES local methods,
743+# which are defined in the implementation section but not in the interface are
744+# included in the documentation. If set to NO only methods in the interface are
745+# included.
746+# The default value is: NO.
747+
748+EXTRACT_LOCAL_METHODS = NO
749+
750+# If this flag is set to YES, the members of anonymous namespaces will be
751+# extracted and appear in the documentation as a namespace called
752+# 'anonymous_namespace{file}', where file will be replaced with the base name of
753+# the file that contains the anonymous namespace. By default anonymous namespace
754+# are hidden.
755+# The default value is: NO.
756+
757+EXTRACT_ANON_NSPACES = NO
758+
759+# If the HIDE_UNDOC_MEMBERS tag is set to YES, doxygen will hide all
760+# undocumented members inside documented classes or files. If set to NO these
761+# members will be included in the various overviews, but no documentation
762+# section is generated. This option has no effect if EXTRACT_ALL is enabled.
763+# The default value is: NO.
764+
765+HIDE_UNDOC_MEMBERS = NO
766+
767+# If the HIDE_UNDOC_CLASSES tag is set to YES, doxygen will hide all
768+# undocumented classes that are normally visible in the class hierarchy. If set
769+# to NO these classes will be included in the various overviews. This option has
770+# no effect if EXTRACT_ALL is enabled.
771+# The default value is: NO.
772+
773+HIDE_UNDOC_CLASSES = NO
774+
775+# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, doxygen will hide all friend
776+# (class|struct|union) declarations. If set to NO these declarations will be
777+# included in the documentation.
778+# The default value is: NO.
779+
780+HIDE_FRIEND_COMPOUNDS = YES
781+
782+# If the HIDE_IN_BODY_DOCS tag is set to YES, doxygen will hide any
783+# documentation blocks found inside the body of a function. If set to NO these
784+# blocks will be appended to the function's detailed documentation block.
785+# The default value is: NO.
786+
787+HIDE_IN_BODY_DOCS = NO
788+
789+# The INTERNAL_DOCS tag determines if documentation that is typed after a
790+# \internal command is included. If the tag is set to NO then the documentation
791+# will be excluded. Set it to YES to include the internal documentation.
792+# The default value is: NO.
793+
794+INTERNAL_DOCS = @INTERNAL_DOCS@
795+
796+# If the CASE_SENSE_NAMES tag is set to NO then doxygen will only generate file
797+# names in lower-case letters. If set to YES upper-case letters are also
798+# allowed. This is useful if you have classes or files whose names only differ
799+# in case and if your file system supports case sensitive file names. Windows
800+# and Mac users are advised to set this option to NO.
801+# The default value is: system dependent.
802+
803+CASE_SENSE_NAMES = YES
804+
805+# If the HIDE_SCOPE_NAMES tag is set to NO then doxygen will show members with
806+# their full class and namespace scopes in the documentation. If set to YES the
807+# scope will be hidden.
808+# The default value is: NO.
809+
810+HIDE_SCOPE_NAMES = NO
811+
812+# If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of
813+# the files that are included by a file in the documentation of that file.
814+# The default value is: YES.
815+
816+SHOW_INCLUDE_FILES = YES
817+
818+# If the SHOW_GROUPED_MEMB_INC tag is set to YES then Doxygen will add for each
819+# grouped member an include statement to the documentation, telling the reader
820+# which file to include in order to use the member.
821+# The default value is: NO.
822+
823+SHOW_GROUPED_MEMB_INC = NO
824+
825+# If the FORCE_LOCAL_INCLUDES tag is set to YES then doxygen will list include
826+# files with double quotes in the documentation rather than with sharp brackets.
827+# The default value is: NO.
828+
829+FORCE_LOCAL_INCLUDES = NO
830+
831+# If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the
832+# documentation for inline members.
833+# The default value is: YES.
834+
835+INLINE_INFO = YES
836+
837+# If the SORT_MEMBER_DOCS tag is set to YES then doxygen will sort the
838+# (detailed) documentation of file and class members alphabetically by member
839+# name. If set to NO the members will appear in declaration order.
840+# The default value is: YES.
841+
842+SORT_MEMBER_DOCS = YES
843+
844+# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief
845+# descriptions of file, namespace and class members alphabetically by member
846+# name. If set to NO the members will appear in declaration order. Note that
847+# this will also influence the order of the classes in the class list.
848+# The default value is: NO.
849+
850+SORT_BRIEF_DOCS = YES
851+
852+# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the
853+# (brief and detailed) documentation of class members so that constructors and
854+# destructors are listed first. If set to NO the constructors will appear in the
855+# respective orders defined by SORT_BRIEF_DOCS and SORT_MEMBER_DOCS.
856+# Note: If SORT_BRIEF_DOCS is set to NO this option is ignored for sorting brief
857+# member documentation.
858+# Note: If SORT_MEMBER_DOCS is set to NO this option is ignored for sorting
859+# detailed member documentation.
860+# The default value is: NO.
861+
862+SORT_MEMBERS_CTORS_1ST = YES
863+
864+# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the hierarchy
865+# of group names into alphabetical order. If set to NO the group names will
866+# appear in their defined order.
867+# The default value is: NO.
868+
869+SORT_GROUP_NAMES = NO
870+
871+# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be sorted by
872+# fully-qualified names, including namespaces. If set to NO, the class list will
873+# be sorted only by class name, not including the namespace part.
874+# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
875+# Note: This option applies only to the class list, not to the alphabetical
876+# list.
877+# The default value is: NO.
878+
879+SORT_BY_SCOPE_NAME = NO
880+
881+# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper
882+# type resolution of all parameters of a function it will reject a match between
883+# the prototype and the implementation of a member function even if there is
884+# only one candidate or it is obvious which candidate to choose by doing a
885+# simple string match. By disabling STRICT_PROTO_MATCHING doxygen will still
886+# accept a match between prototype and implementation in such cases.
887+# The default value is: NO.
888+
889+STRICT_PROTO_MATCHING = NO
890+
891+# The GENERATE_TODOLIST tag can be used to enable ( YES) or disable ( NO) the
892+# todo list. This list is created by putting \todo commands in the
893+# documentation.
894+# The default value is: YES.
895+
896+GENERATE_TODOLIST = YES
897+
898+# The GENERATE_TESTLIST tag can be used to enable ( YES) or disable ( NO) the
899+# test list. This list is created by putting \test commands in the
900+# documentation.
901+# The default value is: YES.
902+
903+GENERATE_TESTLIST = YES
904+
905+# The GENERATE_BUGLIST tag can be used to enable ( YES) or disable ( NO) the bug
906+# list. This list is created by putting \bug commands in the documentation.
907+# The default value is: YES.
908+
909+GENERATE_BUGLIST = YES
910+
911+# The GENERATE_DEPRECATEDLIST tag can be used to enable ( YES) or disable ( NO)
912+# the deprecated list. This list is created by putting \deprecated commands in
913+# the documentation.
914+# The default value is: YES.
915+
916+GENERATE_DEPRECATEDLIST= YES
917+
918+# The ENABLED_SECTIONS tag can be used to enable conditional documentation
919+# sections, marked by \if <section_label> ... \endif and \cond <section_label>
920+# ... \endcond blocks.
921+
922+ENABLED_SECTIONS =
923+
924+# The MAX_INITIALIZER_LINES tag determines the maximum number of lines that the
925+# initial value of a variable or macro / define can have for it to appear in the
926+# documentation. If the initializer consists of more lines than specified here
927+# it will be hidden. Use a value of 0 to hide initializers completely. The
928+# appearance of the value of individual variables and macros / defines can be
929+# controlled using \showinitializer or \hideinitializer command in the
930+# documentation regardless of this setting.
931+# Minimum value: 0, maximum value: 10000, default value: 30.
932+
933+MAX_INITIALIZER_LINES = 30
934+
935+# Set the SHOW_USED_FILES tag to NO to disable the list of files generated at
936+# the bottom of the documentation of classes and structs. If set to YES the list
937+# will mention the files that were used to generate the documentation.
938+# The default value is: YES.
939+
940+SHOW_USED_FILES = YES
941+
942+# Set the SHOW_FILES tag to NO to disable the generation of the Files page. This
943+# will remove the Files entry from the Quick Index and from the Folder Tree View
944+# (if specified).
945+# The default value is: YES.
946+
947+SHOW_FILES = YES
948+
949+# Set the SHOW_NAMESPACES tag to NO to disable the generation of the Namespaces
950+# page. This will remove the Namespaces entry from the Quick Index and from the
951+# Folder Tree View (if specified).
952+# The default value is: YES.
953+
954+SHOW_NAMESPACES = YES
955+
956+# The FILE_VERSION_FILTER tag can be used to specify a program or script that
957+# doxygen should invoke to get the current version for each file (typically from
958+# the version control system). Doxygen will invoke the program by executing (via
959+# popen()) the command command input-file, where command is the value of the
960+# FILE_VERSION_FILTER tag, and input-file is the name of an input file provided
961+# by doxygen. Whatever the program writes to standard output is used as the file
962+# version. For an example see the documentation.
963+
964+FILE_VERSION_FILTER =
965+
966+# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
967+# by doxygen. The layout file controls the global structure of the generated
968+# output files in an output format independent way. To create the layout file
969+# that represents doxygen's defaults, run doxygen with the -l option. You can
970+# optionally specify a file name after the option, if omitted DoxygenLayout.xml
971+# will be used as the name of the layout file.
972+#
973+# Note that if you run doxygen from a directory containing a file called
974+# DoxygenLayout.xml, doxygen will parse it automatically even if the LAYOUT_FILE
975+# tag is left empty.
976+
977+LAYOUT_FILE =
978+
979+# The CITE_BIB_FILES tag can be used to specify one or more bib files containing
980+# the reference definitions. This must be a list of .bib files. The .bib
981+# extension is automatically appended if omitted. This requires the bibtex tool
982+# to be installed. See also http://en.wikipedia.org/wiki/BibTeX for more info.
983+# For LaTeX the style of the bibliography can be controlled using
984+# LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the
985+# search path. Do not use file names with spaces, bibtex cannot handle them. See
986+# also \cite for info how to create references.
987+
988+CITE_BIB_FILES =
989+
990+#---------------------------------------------------------------------------
991+# Configuration options related to warning and progress messages
992+#---------------------------------------------------------------------------
993+
994+# The QUIET tag can be used to turn on/off the messages that are generated to
995+# standard output by doxygen. If QUIET is set to YES this implies that the
996+# messages are off.
997+# The default value is: NO.
998+
999+QUIET = NO
1000+
1001+# The WARNINGS tag can be used to turn on/off the warning messages that are
1002+# generated to standard error ( stderr) by doxygen. If WARNINGS is set to YES
1003+# this implies that the warnings are on.
1004+#
1005+# Tip: Turn warnings on while writing the documentation.
1006+# The default value is: YES.
1007+
1008+WARNINGS = YES
1009+
1010+# If the WARN_IF_UNDOCUMENTED tag is set to YES, then doxygen will generate
1011+# warnings for undocumented members. If EXTRACT_ALL is set to YES then this flag
1012+# will automatically be disabled.
1013+# The default value is: YES.
1014+
1015+WARN_IF_UNDOCUMENTED = YES
1016+
1017+# If the WARN_IF_DOC_ERROR tag is set to YES, doxygen will generate warnings for
1018+# potential errors in the documentation, such as not documenting some parameters
1019+# in a documented function, or documenting parameters that don't exist or using
1020+# markup commands wrongly.
1021+# The default value is: YES.
1022+
1023+WARN_IF_DOC_ERROR = YES
1024+
1025+# This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that
1026+# are documented, but have no documentation for their parameters or return
1027+# value. If set to NO doxygen will only warn about wrong or incomplete parameter
1028+# documentation, but not about the absence of documentation.
1029+# The default value is: NO.
1030+
1031+WARN_NO_PARAMDOC = YES
1032+
1033+# The WARN_FORMAT tag determines the format of the warning messages that doxygen
1034+# can produce. The string should contain the $file, $line, and $text tags, which
1035+# will be replaced by the file and line number from which the warning originated
1036+# and the warning text. Optionally the format may contain $version, which will
1037+# be replaced by the version of the file (if it could be obtained via
1038+# FILE_VERSION_FILTER)
1039+# The default value is: $file:$line: $text.
1040+
1041+WARN_FORMAT = "$file:$line: $text"
1042+
1043+# The WARN_LOGFILE tag can be used to specify a file to which warning and error
1044+# messages should be written. If left blank the output is written to standard
1045+# error (stderr).
1046+
1047+WARN_LOGFILE =
1048+
1049+#---------------------------------------------------------------------------
1050+# Configuration options related to the input files
1051+#---------------------------------------------------------------------------
1052+
1053+# The INPUT tag is used to specify the files and/or directories that contain
1054+# documented source files. You may enter file names like myfile.cpp or
1055+# directories like /usr/src/myproject. Separate the files or directories with
1056+# spaces.
1057+# Note: If this tag is empty the current directory is searched.
1058+
1059+INPUT = @CMAKE_SOURCE_DIR@/src/qt/include \
1060+ @CMAKE_CURRENT_SOURCE_DIR@/pages
1061+
1062+# This tag can be used to specify the character encoding of the source files
1063+# that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses
1064+# libiconv (or the iconv built into libc) for the transcoding. See the libiconv
1065+# documentation (see: http://www.gnu.org/software/libiconv) for the list of
1066+# possible encodings.
1067+# The default value is: UTF-8.
1068+
1069+INPUT_ENCODING = UTF-8
1070+
1071+# If the value of the INPUT tag contains directories, you can use the
1072+# FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and
1073+# *.h) to filter out the source-files in the directories. If left blank the
1074+# following patterns are tested:*.c, *.cc, *.cxx, *.cpp, *.c++, *.java, *.ii,
1075+# *.ixx, *.ipp, *.i++, *.inl, *.idl, *.ddl, *.odl, *.h, *.hh, *.hxx, *.hpp,
1076+# *.h++, *.cs, *.d, *.php, *.php4, *.php5, *.phtml, *.inc, *.m, *.markdown,
1077+# *.md, *.mm, *.dox, *.py, *.f90, *.f, *.for, *.tcl, *.vhd, *.vhdl, *.ucf,
1078+# *.qsf, *.as and *.js.
1079+
1080+FILE_PATTERNS =
1081+
1082+# The RECURSIVE tag can be used to specify whether or not subdirectories should
1083+# be searched for input files as well.
1084+# The default value is: NO.
1085+
1086+RECURSIVE = YES
1087+
1088+# The EXCLUDE tag can be used to specify files and/or directories that should be
1089+# excluded from the INPUT source files. This way you can easily exclude a
1090+# subdirectory from a directory tree whose root is specified with the INPUT tag.
1091+#
1092+# Note that relative paths are relative to the directory from which doxygen is
1093+# run.
1094+
1095+EXCLUDE =
1096+
1097+# The EXCLUDE_SYMLINKS tag can be used to select whether or not files or
1098+# directories that are symbolic links (a Unix file system feature) are excluded
1099+# from the input.
1100+# The default value is: NO.
1101+
1102+EXCLUDE_SYMLINKS = NO
1103+
1104+# If the value of the INPUT tag contains directories, you can use the
1105+# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
1106+# certain files from those directories.
1107+#
1108+# Note that the wildcards are matched against the file with absolute path, so to
1109+# exclude all test directories for example use the pattern */test/*
1110+
1111+EXCLUDE_PATTERNS =
1112+
1113+# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
1114+# (namespaces, classes, functions, etc.) that should be excluded from the
1115+# output. The symbol name can be a fully qualified name, a word, or if the
1116+# wildcard * is used, a substring. Examples: ANamespace, AClass,
1117+# AClass::ANamespace, ANamespace::*Test
1118+#
1119+# Note that the wildcards are matched against the file with absolute path, so to
1120+# exclude all test directories use the pattern */test/*
1121+
1122+EXCLUDE_SYMBOLS =
1123+
1124+# The EXAMPLE_PATH tag can be used to specify one or more files or directories
1125+# that contain example code fragments that are included (see the \include
1126+# command).
1127+
1128+EXAMPLE_PATH = @CMAKE_CURRENT_SOURCE_DIR@/examples
1129+
1130+# If the value of the EXAMPLE_PATH tag contains directories, you can use the
1131+# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp and
1132+# *.h) to filter out the source-files in the directories. If left blank all
1133+# files are included.
1134+
1135+EXAMPLE_PATTERNS =
1136+
1137+# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
1138+# searched for input files to be used with the \include or \dontinclude commands
1139+# irrespective of the value of the RECURSIVE tag.
1140+# The default value is: NO.
1141+
1142+EXAMPLE_RECURSIVE = YES
1143+
1144+# The IMAGE_PATH tag can be used to specify one or more files or directories
1145+# that contain images that are to be included in the documentation (see the
1146+# \image command).
1147+
1148+IMAGE_PATH =
1149+
1150+# The INPUT_FILTER tag can be used to specify a program that doxygen should
1151+# invoke to filter for each input file. Doxygen will invoke the filter program
1152+# by executing (via popen()) the command:
1153+#
1154+# <filter> <input-file>
1155+#
1156+# where <filter> is the value of the INPUT_FILTER tag, and <input-file> is the
1157+# name of an input file. Doxygen will then use the output that the filter
1158+# program writes to standard output. If FILTER_PATTERNS is specified, this tag
1159+# will be ignored.
1160+#
1161+# Note that the filter must not add or remove lines; it is applied before the
1162+# code is scanned, but not when the output code is generated. If lines are added
1163+# or removed, the anchors will not be placed correctly.
1164+
1165+INPUT_FILTER =
1166+
1167+# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
1168+# basis. Doxygen will compare the file name with each pattern and apply the
1169+# filter if there is a match. The filters are a list of the form: pattern=filter
1170+# (like *.cpp=my_cpp_filter). See INPUT_FILTER for further information on how
1171+# filters are used. If the FILTER_PATTERNS tag is empty or if none of the
1172+# patterns match the file name, INPUT_FILTER is applied.
1173+
1174+FILTER_PATTERNS =
1175+
1176+# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
1177+# INPUT_FILTER ) will also be used to filter the input files that are used for
1178+# producing the source files to browse (i.e. when SOURCE_BROWSER is set to YES).
1179+# The default value is: NO.
1180+
1181+FILTER_SOURCE_FILES = NO
1182+
1183+# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file
1184+# pattern. A pattern will override the setting for FILTER_PATTERN (if any) and
1185+# it is also possible to disable source filtering for a specific pattern using
1186+# *.ext= (so without naming a filter).
1187+# This tag requires that the tag FILTER_SOURCE_FILES is set to YES.
1188+
1189+FILTER_SOURCE_PATTERNS =
1190+
1191+# If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that
1192+# is part of the input, its contents will be placed on the main page
1193+# (index.html). This can be useful if you have a project on for instance GitHub
1194+# and want to reuse the introduction page also for the doxygen output.
1195+
1196+USE_MDFILE_AS_MAINPAGE =
1197+
1198+#---------------------------------------------------------------------------
1199+# Configuration options related to source browsing
1200+#---------------------------------------------------------------------------
1201+
1202+# If the SOURCE_BROWSER tag is set to YES then a list of source files will be
1203+# generated. Documented entities will be cross-referenced with these sources.
1204+#
1205+# Note: To get rid of all source code in the generated output, make sure that
1206+# also VERBATIM_HEADERS is set to NO.
1207+# The default value is: NO.
1208+
1209+SOURCE_BROWSER = YES
1210+
1211+# Setting the INLINE_SOURCES tag to YES will include the body of functions,
1212+# classes and enums directly into the documentation.
1213+# The default value is: NO.
1214+
1215+INLINE_SOURCES = NO
1216+
1217+# Setting the STRIP_CODE_COMMENTS tag to YES will instruct doxygen to hide any
1218+# special comment blocks from generated source code fragments. Normal C, C++ and
1219+# Fortran comments will always remain visible.
1220+# The default value is: YES.
1221+
1222+STRIP_CODE_COMMENTS = YES
1223+
1224+# If the REFERENCED_BY_RELATION tag is set to YES then for each documented
1225+# function all documented functions referencing it will be listed.
1226+# The default value is: NO.
1227+
1228+REFERENCED_BY_RELATION = YES
1229+
1230+# If the REFERENCES_RELATION tag is set to YES then for each documented function
1231+# all documented entities called/used by that function will be listed.
1232+# The default value is: NO.
1233+
1234+REFERENCES_RELATION = YES
1235+
1236+# If the REFERENCES_LINK_SOURCE tag is set to YES and SOURCE_BROWSER tag is set
1237+# to YES, then the hyperlinks from functions in REFERENCES_RELATION and
1238+# REFERENCED_BY_RELATION lists will link to the source code. Otherwise they will
1239+# link to the documentation.
1240+# The default value is: YES.
1241+
1242+REFERENCES_LINK_SOURCE = YES
1243+
1244+# If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the
1245+# source code will show a tooltip with additional information such as prototype,
1246+# brief description and links to the definition and documentation. Since this
1247+# will make the HTML file larger and loading of large files a bit slower, you
1248+# can opt to disable this feature.
1249+# The default value is: YES.
1250+# This tag requires that the tag SOURCE_BROWSER is set to YES.
1251+
1252+SOURCE_TOOLTIPS = YES
1253+
1254+# If the USE_HTAGS tag is set to YES then the references to source code will
1255+# point to the HTML generated by the htags(1) tool instead of doxygen built-in
1256+# source browser. The htags tool is part of GNU's global source tagging system
1257+# (see http://www.gnu.org/software/global/global.html). You will need version
1258+# 4.8.6 or higher.
1259+#
1260+# To use it do the following:
1261+# - Install the latest version of global
1262+# - Enable SOURCE_BROWSER and USE_HTAGS in the config file
1263+# - Make sure the INPUT points to the root of the source tree
1264+# - Run doxygen as normal
1265+#
1266+# Doxygen will invoke htags (and that will in turn invoke gtags), so these
1267+# tools must be available from the command line (i.e. in the search path).
1268+#
1269+# The result: instead of the source browser generated by doxygen, the links to
1270+# source code will now point to the output of htags.
1271+# The default value is: NO.
1272+# This tag requires that the tag SOURCE_BROWSER is set to YES.
1273+
1274+USE_HTAGS = NO
1275+
1276+# If the VERBATIM_HEADERS tag is set the YES then doxygen will generate a
1277+# verbatim copy of the header file for each class for which an include is
1278+# specified. Set to NO to disable this.
1279+# See also: Section \class.
1280+# The default value is: YES.
1281+
1282+VERBATIM_HEADERS = YES
1283+
1284+#---------------------------------------------------------------------------
1285+# Configuration options related to the alphabetical class index
1286+#---------------------------------------------------------------------------
1287+
1288+# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index of all
1289+# compounds will be generated. Enable this if the project contains a lot of
1290+# classes, structs, unions or interfaces.
1291+# The default value is: YES.
1292+
1293+ALPHABETICAL_INDEX = YES
1294+
1295+# The COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns in
1296+# which the alphabetical index list will be split.
1297+# Minimum value: 1, maximum value: 20, default value: 5.
1298+# This tag requires that the tag ALPHABETICAL_INDEX is set to YES.
1299+
1300+COLS_IN_ALPHA_INDEX = 5
1301+
1302+# In case all classes in a project start with a common prefix, all classes will
1303+# be put under the same header in the alphabetical index. The IGNORE_PREFIX tag
1304+# can be used to specify a prefix (or a list of prefixes) that should be ignored
1305+# while generating the index headers.
1306+# This tag requires that the tag ALPHABETICAL_INDEX is set to YES.
1307+
1308+IGNORE_PREFIX =
1309+
1310+#---------------------------------------------------------------------------
1311+# Configuration options related to the HTML output
1312+#---------------------------------------------------------------------------
1313+
1314+# If the GENERATE_HTML tag is set to YES doxygen will generate HTML output
1315+# The default value is: YES.
1316+
1317+GENERATE_HTML = YES
1318+
1319+# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. If a
1320+# relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1321+# it.
1322+# The default directory is: html.
1323+# This tag requires that the tag GENERATE_HTML is set to YES.
1324+
1325+HTML_OUTPUT = html
1326+
1327+# The HTML_FILE_EXTENSION tag can be used to specify the file extension for each
1328+# generated HTML page (for example: .htm, .php, .asp).
1329+# The default value is: .html.
1330+# This tag requires that the tag GENERATE_HTML is set to YES.
1331+
1332+HTML_FILE_EXTENSION = .html
1333+
1334+# The HTML_HEADER tag can be used to specify a user-defined HTML header file for
1335+# each generated HTML page. If the tag is left blank doxygen will generate a
1336+# standard header.
1337+#
1338+# To get valid HTML the header file that includes any scripts and style sheets
1339+# that doxygen needs, which is dependent on the configuration options used (e.g.
1340+# the setting GENERATE_TREEVIEW). It is highly recommended to start with a
1341+# default header using
1342+# doxygen -w html new_header.html new_footer.html new_stylesheet.css
1343+# YourConfigFile
1344+# and then modify the file new_header.html. See also section "Doxygen usage"
1345+# for information on how to generate the default header that doxygen normally
1346+# uses.
1347+# Note: The header is subject to change so you typically have to regenerate the
1348+# default header when upgrading to a newer version of doxygen. For a description
1349+# of the possible markers and block names see the documentation.
1350+# This tag requires that the tag GENERATE_HTML is set to YES.
1351+
1352+HTML_HEADER =
1353+
1354+# The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each
1355+# generated HTML page. If the tag is left blank doxygen will generate a standard
1356+# footer. See HTML_HEADER for more information on how to generate a default
1357+# footer and what special commands can be used inside the footer. See also
1358+# section "Doxygen usage" for information on how to generate the default footer
1359+# that doxygen normally uses.
1360+# This tag requires that the tag GENERATE_HTML is set to YES.
1361+
1362+HTML_FOOTER =
1363+
1364+# The HTML_STYLESHEET tag can be used to specify a user-defined cascading style
1365+# sheet that is used by each HTML page. It can be used to fine-tune the look of
1366+# the HTML output. If left blank doxygen will generate a default style sheet.
1367+# See also section "Doxygen usage" for information on how to generate the style
1368+# sheet that doxygen normally uses.
1369+# Note: It is recommended to use HTML_EXTRA_STYLESHEET instead of this tag, as
1370+# it is more robust and this tag (HTML_STYLESHEET) will in the future become
1371+# obsolete.
1372+# This tag requires that the tag GENERATE_HTML is set to YES.
1373+
1374+HTML_STYLESHEET =
1375+
1376+# The HTML_EXTRA_STYLESHEET tag can be used to specify an additional user-
1377+# defined cascading style sheet that is included after the standard style sheets
1378+# created by doxygen. Using this option one can overrule certain style aspects.
1379+# This is preferred over using HTML_STYLESHEET since it does not replace the
1380+# standard style sheet and is therefor more robust against future updates.
1381+# Doxygen will copy the style sheet file to the output directory. For an example
1382+# see the documentation.
1383+# This tag requires that the tag GENERATE_HTML is set to YES.
1384+
1385+HTML_EXTRA_STYLESHEET = @CMAKE_CURRENT_SOURCE_DIR@/extra.css
1386+
1387+# The HTML_EXTRA_FILES tag can be used to specify one or more extra images or
1388+# other source files which should be copied to the HTML output directory. Note
1389+# that these files will be copied to the base HTML output directory. Use the
1390+# $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these
1391+# files. In the HTML_STYLESHEET file, use the file name only. Also note that the
1392+# files will be copied as-is; there are no commands or markers available.
1393+# This tag requires that the tag GENERATE_HTML is set to YES.
1394+
1395+HTML_EXTRA_FILES =
1396+
1397+# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen
1398+# will adjust the colors in the stylesheet and background images according to
1399+# this color. Hue is specified as an angle on a colorwheel, see
1400+# http://en.wikipedia.org/wiki/Hue for more information. For instance the value
1401+# 0 represents red, 60 is yellow, 120 is green, 180 is cyan, 240 is blue, 300
1402+# purple, and 360 is red again.
1403+# Minimum value: 0, maximum value: 359, default value: 220.
1404+# This tag requires that the tag GENERATE_HTML is set to YES.
1405+
1406+HTML_COLORSTYLE_HUE = 220
1407+
1408+# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors
1409+# in the HTML output. For a value of 0 the output will use grayscales only. A
1410+# value of 255 will produce the most vivid colors.
1411+# Minimum value: 0, maximum value: 255, default value: 100.
1412+# This tag requires that the tag GENERATE_HTML is set to YES.
1413+
1414+HTML_COLORSTYLE_SAT = 100
1415+
1416+# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to the
1417+# luminance component of the colors in the HTML output. Values below 100
1418+# gradually make the output lighter, whereas values above 100 make the output
1419+# darker. The value divided by 100 is the actual gamma applied, so 80 represents
1420+# a gamma of 0.8, The value 220 represents a gamma of 2.2, and 100 does not
1421+# change the gamma.
1422+# Minimum value: 40, maximum value: 240, default value: 80.
1423+# This tag requires that the tag GENERATE_HTML is set to YES.
1424+
1425+HTML_COLORSTYLE_GAMMA = 80
1426+
1427+# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
1428+# page will contain the date and time when the page was generated. Setting this
1429+# to NO can help when comparing the output of multiple runs.
1430+# The default value is: YES.
1431+# This tag requires that the tag GENERATE_HTML is set to YES.
1432+
1433+HTML_TIMESTAMP = YES
1434+
1435+# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
1436+# documentation will contain sections that can be hidden and shown after the
1437+# page has loaded.
1438+# The default value is: NO.
1439+# This tag requires that the tag GENERATE_HTML is set to YES.
1440+
1441+HTML_DYNAMIC_SECTIONS = YES
1442+
1443+# With HTML_INDEX_NUM_ENTRIES one can control the preferred number of entries
1444+# shown in the various tree structured indices initially; the user can expand
1445+# and collapse entries dynamically later on. Doxygen will expand the tree to
1446+# such a level that at most the specified number of entries are visible (unless
1447+# a fully collapsed tree already exceeds this amount). So setting the number of
1448+# entries 1 will produce a full collapsed tree by default. 0 is a special value
1449+# representing an infinite number of entries and will result in a full expanded
1450+# tree by default.
1451+# Minimum value: 0, maximum value: 9999, default value: 100.
1452+# This tag requires that the tag GENERATE_HTML is set to YES.
1453+
1454+HTML_INDEX_NUM_ENTRIES = 100
1455+
1456+# If the GENERATE_DOCSET tag is set to YES, additional index files will be
1457+# generated that can be used as input for Apple's Xcode 3 integrated development
1458+# environment (see: http://developer.apple.com/tools/xcode/), introduced with
1459+# OSX 10.5 (Leopard). To create a documentation set, doxygen will generate a
1460+# Makefile in the HTML output directory. Running make will produce the docset in
1461+# that directory and running make install will install the docset in
1462+# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at
1463+# startup. See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
1464+# for more information.
1465+# The default value is: NO.
1466+# This tag requires that the tag GENERATE_HTML is set to YES.
1467+
1468+GENERATE_DOCSET = NO
1469+
1470+# This tag determines the name of the docset feed. A documentation feed provides
1471+# an umbrella under which multiple documentation sets from a single provider
1472+# (such as a company or product suite) can be grouped.
1473+# The default value is: Doxygen generated docs.
1474+# This tag requires that the tag GENERATE_DOCSET is set to YES.
1475+
1476+DOCSET_FEEDNAME = "Doxygen generated docs"
1477+
1478+# This tag specifies a string that should uniquely identify the documentation
1479+# set bundle. This should be a reverse domain-name style string, e.g.
1480+# com.mycompany.MyDocSet. Doxygen will append .docset to the name.
1481+# The default value is: org.doxygen.Project.
1482+# This tag requires that the tag GENERATE_DOCSET is set to YES.
1483+
1484+DOCSET_BUNDLE_ID = org.doxygen.Project
1485+
1486+# The DOCSET_PUBLISHER_ID tag specifies a string that should uniquely identify
1487+# the documentation publisher. This should be a reverse domain-name style
1488+# string, e.g. com.mycompany.MyDocSet.documentation.
1489+# The default value is: org.doxygen.Publisher.
1490+# This tag requires that the tag GENERATE_DOCSET is set to YES.
1491+
1492+DOCSET_PUBLISHER_ID = org.doxygen.Publisher
1493+
1494+# The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher.
1495+# The default value is: Publisher.
1496+# This tag requires that the tag GENERATE_DOCSET is set to YES.
1497+
1498+DOCSET_PUBLISHER_NAME = Publisher
1499+
1500+# If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three
1501+# additional HTML index files: index.hhp, index.hhc, and index.hhk. The
1502+# index.hhp is a project file that can be read by Microsoft's HTML Help Workshop
1503+# (see: http://www.microsoft.com/en-us/download/details.aspx?id=21138) on
1504+# Windows.
1505+#
1506+# The HTML Help Workshop contains a compiler that can convert all HTML output
1507+# generated by doxygen into a single compiled HTML file (.chm). Compiled HTML
1508+# files are now used as the Windows 98 help format, and will replace the old
1509+# Windows help format (.hlp) on all Windows platforms in the future. Compressed
1510+# HTML files also contain an index, a table of contents, and you can search for
1511+# words in the documentation. The HTML workshop also contains a viewer for
1512+# compressed HTML files.
1513+# The default value is: NO.
1514+# This tag requires that the tag GENERATE_HTML is set to YES.
1515+
1516+GENERATE_HTMLHELP = NO
1517+
1518+# The CHM_FILE tag can be used to specify the file name of the resulting .chm
1519+# file. You can add a path in front of the file if the result should not be
1520+# written to the html output directory.
1521+# This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1522+
1523+CHM_FILE =
1524+
1525+# The HHC_LOCATION tag can be used to specify the location (absolute path
1526+# including file name) of the HTML help compiler ( hhc.exe). If non-empty
1527+# doxygen will try to run the HTML help compiler on the generated index.hhp.
1528+# The file has to be specified with full path.
1529+# This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1530+
1531+HHC_LOCATION =
1532+
1533+# The GENERATE_CHI flag controls if a separate .chi index file is generated (
1534+# YES) or that it should be included in the master .chm file ( NO).
1535+# The default value is: NO.
1536+# This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1537+
1538+GENERATE_CHI = NO
1539+
1540+# The CHM_INDEX_ENCODING is used to encode HtmlHelp index ( hhk), content ( hhc)
1541+# and project file content.
1542+# This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1543+
1544+CHM_INDEX_ENCODING =
1545+
1546+# The BINARY_TOC flag controls whether a binary table of contents is generated (
1547+# YES) or a normal table of contents ( NO) in the .chm file. Furthermore it
1548+# enables the Previous and Next buttons.
1549+# The default value is: NO.
1550+# This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1551+
1552+BINARY_TOC = NO
1553+
1554+# The TOC_EXPAND flag can be set to YES to add extra items for group members to
1555+# the table of contents of the HTML help documentation and to the tree view.
1556+# The default value is: NO.
1557+# This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1558+
1559+TOC_EXPAND = NO
1560+
1561+# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and
1562+# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated that
1563+# can be used as input for Qt's qhelpgenerator to generate a Qt Compressed Help
1564+# (.qch) of the generated HTML documentation.
1565+# The default value is: NO.
1566+# This tag requires that the tag GENERATE_HTML is set to YES.
1567+
1568+GENERATE_QHP = NO
1569+
1570+# If the QHG_LOCATION tag is specified, the QCH_FILE tag can be used to specify
1571+# the file name of the resulting .qch file. The path specified is relative to
1572+# the HTML output folder.
1573+# This tag requires that the tag GENERATE_QHP is set to YES.
1574+
1575+QCH_FILE =
1576+
1577+# The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help
1578+# Project output. For more information please see Qt Help Project / Namespace
1579+# (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#namespace).
1580+# The default value is: org.doxygen.Project.
1581+# This tag requires that the tag GENERATE_QHP is set to YES.
1582+
1583+QHP_NAMESPACE = org.doxygen.Project
1584+
1585+# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating Qt
1586+# Help Project output. For more information please see Qt Help Project / Virtual
1587+# Folders (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#virtual-
1588+# folders).
1589+# The default value is: doc.
1590+# This tag requires that the tag GENERATE_QHP is set to YES.
1591+
1592+QHP_VIRTUAL_FOLDER = doc
1593+
1594+# If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom
1595+# filter to add. For more information please see Qt Help Project / Custom
1596+# Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-
1597+# filters).
1598+# This tag requires that the tag GENERATE_QHP is set to YES.
1599+
1600+QHP_CUST_FILTER_NAME =
1601+
1602+# The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the
1603+# custom filter to add. For more information please see Qt Help Project / Custom
1604+# Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-
1605+# filters).
1606+# This tag requires that the tag GENERATE_QHP is set to YES.
1607+
1608+QHP_CUST_FILTER_ATTRS =
1609+
1610+# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
1611+# project's filter section matches. Qt Help Project / Filter Attributes (see:
1612+# http://qt-project.org/doc/qt-4.8/qthelpproject.html#filter-attributes).
1613+# This tag requires that the tag GENERATE_QHP is set to YES.
1614+
1615+QHP_SECT_FILTER_ATTRS =
1616+
1617+# The QHG_LOCATION tag can be used to specify the location of Qt's
1618+# qhelpgenerator. If non-empty doxygen will try to run qhelpgenerator on the
1619+# generated .qhp file.
1620+# This tag requires that the tag GENERATE_QHP is set to YES.
1621+
1622+QHG_LOCATION =
1623+
1624+# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files will be
1625+# generated, together with the HTML files, they form an Eclipse help plugin. To
1626+# install this plugin and make it available under the help contents menu in
1627+# Eclipse, the contents of the directory containing the HTML and XML files needs
1628+# to be copied into the plugins directory of eclipse. The name of the directory
1629+# within the plugins directory should be the same as the ECLIPSE_DOC_ID value.
1630+# After copying Eclipse needs to be restarted before the help appears.
1631+# The default value is: NO.
1632+# This tag requires that the tag GENERATE_HTML is set to YES.
1633+
1634+GENERATE_ECLIPSEHELP = NO
1635+
1636+# A unique identifier for the Eclipse help plugin. When installing the plugin
1637+# the directory name containing the HTML and XML files should also have this
1638+# name. Each documentation set should have its own identifier.
1639+# The default value is: org.doxygen.Project.
1640+# This tag requires that the tag GENERATE_ECLIPSEHELP is set to YES.
1641+
1642+ECLIPSE_DOC_ID = org.doxygen.Project
1643+
1644+# If you want full control over the layout of the generated HTML pages it might
1645+# be necessary to disable the index and replace it with your own. The
1646+# DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) at top
1647+# of each HTML page. A value of NO enables the index and the value YES disables
1648+# it. Since the tabs in the index contain the same information as the navigation
1649+# tree, you can set this option to YES if you also set GENERATE_TREEVIEW to YES.
1650+# The default value is: NO.
1651+# This tag requires that the tag GENERATE_HTML is set to YES.
1652+
1653+DISABLE_INDEX = YES
1654+
1655+# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
1656+# structure should be generated to display hierarchical information. If the tag
1657+# value is set to YES, a side panel will be generated containing a tree-like
1658+# index structure (just like the one that is generated for HTML Help). For this
1659+# to work a browser that supports JavaScript, DHTML, CSS and frames is required
1660+# (i.e. any modern browser). Windows users are probably better off using the
1661+# HTML help feature. Via custom stylesheets (see HTML_EXTRA_STYLESHEET) one can
1662+# further fine-tune the look of the index. As an example, the default style
1663+# sheet generated by doxygen has an example that shows how to put an image at
1664+# the root of the tree instead of the PROJECT_NAME. Since the tree basically has
1665+# the same information as the tab index, you could consider setting
1666+# DISABLE_INDEX to YES when enabling this option.
1667+# The default value is: NO.
1668+# This tag requires that the tag GENERATE_HTML is set to YES.
1669+
1670+GENERATE_TREEVIEW = YES
1671+
1672+# The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values that
1673+# doxygen will group on one line in the generated HTML documentation.
1674+#
1675+# Note that a value of 0 will completely suppress the enum values from appearing
1676+# in the overview section.
1677+# Minimum value: 0, maximum value: 20, default value: 4.
1678+# This tag requires that the tag GENERATE_HTML is set to YES.
1679+
1680+ENUM_VALUES_PER_LINE = 1
1681+
1682+# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be used
1683+# to set the initial width (in pixels) of the frame in which the tree is shown.
1684+# Minimum value: 0, maximum value: 1500, default value: 250.
1685+# This tag requires that the tag GENERATE_HTML is set to YES.
1686+
1687+TREEVIEW_WIDTH = 250
1688+
1689+# When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open links to
1690+# external symbols imported via tag files in a separate window.
1691+# The default value is: NO.
1692+# This tag requires that the tag GENERATE_HTML is set to YES.
1693+
1694+EXT_LINKS_IN_WINDOW = NO
1695+
1696+# Use this tag to change the font size of LaTeX formulas included as images in
1697+# the HTML documentation. When you change the font size after a successful
1698+# doxygen run you need to manually remove any form_*.png images from the HTML
1699+# output directory to force them to be regenerated.
1700+# Minimum value: 8, maximum value: 50, default value: 10.
1701+# This tag requires that the tag GENERATE_HTML is set to YES.
1702+
1703+FORMULA_FONTSIZE = 10
1704+
1705+# Use the FORMULA_TRANPARENT tag to determine whether or not the images
1706+# generated for formulas are transparent PNGs. Transparent PNGs are not
1707+# supported properly for IE 6.0, but are supported on all modern browsers.
1708+#
1709+# Note that when changing this option you need to delete any form_*.png files in
1710+# the HTML output directory before the changes have effect.
1711+# The default value is: YES.
1712+# This tag requires that the tag GENERATE_HTML is set to YES.
1713+
1714+FORMULA_TRANSPARENT = YES
1715+
1716+# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax (see
1717+# http://www.mathjax.org) which uses client side Javascript for the rendering
1718+# instead of using prerendered bitmaps. Use this if you do not have LaTeX
1719+# installed or if you want to formulas look prettier in the HTML output. When
1720+# enabled you may also need to install MathJax separately and configure the path
1721+# to it using the MATHJAX_RELPATH option.
1722+# The default value is: NO.
1723+# This tag requires that the tag GENERATE_HTML is set to YES.
1724+
1725+USE_MATHJAX = NO
1726+
1727+# When MathJax is enabled you can set the default output format to be used for
1728+# the MathJax output. See the MathJax site (see:
1729+# http://docs.mathjax.org/en/latest/output.html) for more details.
1730+# Possible values are: HTML-CSS (which is slower, but has the best
1731+# compatibility), NativeMML (i.e. MathML) and SVG.
1732+# The default value is: HTML-CSS.
1733+# This tag requires that the tag USE_MATHJAX is set to YES.
1734+
1735+MATHJAX_FORMAT = HTML-CSS
1736+
1737+# When MathJax is enabled you need to specify the location relative to the HTML
1738+# output directory using the MATHJAX_RELPATH option. The destination directory
1739+# should contain the MathJax.js script. For instance, if the mathjax directory
1740+# is located at the same level as the HTML output directory, then
1741+# MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax
1742+# Content Delivery Network so you can quickly see the result without installing
1743+# MathJax. However, it is strongly recommended to install a local copy of
1744+# MathJax from http://www.mathjax.org before deployment.
1745+# The default value is: http://cdn.mathjax.org/mathjax/latest.
1746+# This tag requires that the tag USE_MATHJAX is set to YES.
1747+
1748+MATHJAX_RELPATH = http://cdn.mathjax.org/mathjax/latest
1749+
1750+# The MATHJAX_EXTENSIONS tag can be used to specify one or more MathJax
1751+# extension names that should be enabled during MathJax rendering. For example
1752+# MATHJAX_EXTENSIONS = TeX/AMSmath TeX/AMSsymbols
1753+# This tag requires that the tag USE_MATHJAX is set to YES.
1754+
1755+MATHJAX_EXTENSIONS =
1756+
1757+# The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces
1758+# of code that will be used on startup of the MathJax code. See the MathJax site
1759+# (see: http://docs.mathjax.org/en/latest/output.html) for more details. For an
1760+# example see the documentation.
1761+# This tag requires that the tag USE_MATHJAX is set to YES.
1762+
1763+MATHJAX_CODEFILE =
1764+
1765+# When the SEARCHENGINE tag is enabled doxygen will generate a search box for
1766+# the HTML output. The underlying search engine uses javascript and DHTML and
1767+# should work on any modern browser. Note that when using HTML help
1768+# (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets (GENERATE_DOCSET)
1769+# there is already a search function so this one should typically be disabled.
1770+# For large projects the javascript based search engine can be slow, then
1771+# enabling SERVER_BASED_SEARCH may provide a better solution. It is possible to
1772+# search using the keyboard; to jump to the search box use <access key> + S
1773+# (what the <access key> is depends on the OS and browser, but it is typically
1774+# <CTRL>, <ALT>/<option>, or both). Inside the search box use the <cursor down
1775+# key> to jump into the search results window, the results can be navigated
1776+# using the <cursor keys>. Press <Enter> to select an item or <escape> to cancel
1777+# the search. The filter options can be selected when the cursor is inside the
1778+# search box by pressing <Shift>+<cursor down>. Also here use the <cursor keys>
1779+# to select a filter and <Enter> or <escape> to activate or cancel the filter
1780+# option.
1781+# The default value is: YES.
1782+# This tag requires that the tag GENERATE_HTML is set to YES.
1783+
1784+SEARCHENGINE = NO
1785+
1786+# When the SERVER_BASED_SEARCH tag is enabled the search engine will be
1787+# implemented using a web server instead of a web client using Javascript. There
1788+# are two flavors of web server based searching depending on the EXTERNAL_SEARCH
1789+# setting. When disabled, doxygen will generate a PHP script for searching and
1790+# an index file used by the script. When EXTERNAL_SEARCH is enabled the indexing
1791+# and searching needs to be provided by external tools. See the section
1792+# "External Indexing and Searching" for details.
1793+# The default value is: NO.
1794+# This tag requires that the tag SEARCHENGINE is set to YES.
1795+
1796+SERVER_BASED_SEARCH = NO
1797+
1798+# When EXTERNAL_SEARCH tag is enabled doxygen will no longer generate the PHP
1799+# script for searching. Instead the search results are written to an XML file
1800+# which needs to be processed by an external indexer. Doxygen will invoke an
1801+# external search engine pointed to by the SEARCHENGINE_URL option to obtain the
1802+# search results.
1803+#
1804+# Doxygen ships with an example indexer ( doxyindexer) and search engine
1805+# (doxysearch.cgi) which are based on the open source search engine library
1806+# Xapian (see: http://xapian.org/).
1807+#
1808+# See the section "External Indexing and Searching" for details.
1809+# The default value is: NO.
1810+# This tag requires that the tag SEARCHENGINE is set to YES.
1811+
1812+EXTERNAL_SEARCH = NO
1813+
1814+# The SEARCHENGINE_URL should point to a search engine hosted by a web server
1815+# which will return the search results when EXTERNAL_SEARCH is enabled.
1816+#
1817+# Doxygen ships with an example indexer ( doxyindexer) and search engine
1818+# (doxysearch.cgi) which are based on the open source search engine library
1819+# Xapian (see: http://xapian.org/). See the section "External Indexing and
1820+# Searching" for details.
1821+# This tag requires that the tag SEARCHENGINE is set to YES.
1822+
1823+SEARCHENGINE_URL =
1824+
1825+# When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the unindexed
1826+# search data is written to a file for indexing by an external tool. With the
1827+# SEARCHDATA_FILE tag the name of this file can be specified.
1828+# The default file is: searchdata.xml.
1829+# This tag requires that the tag SEARCHENGINE is set to YES.
1830+
1831+SEARCHDATA_FILE = searchdata.xml
1832+
1833+# When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the
1834+# EXTERNAL_SEARCH_ID tag can be used as an identifier for the project. This is
1835+# useful in combination with EXTRA_SEARCH_MAPPINGS to search through multiple
1836+# projects and redirect the results back to the right project.
1837+# This tag requires that the tag SEARCHENGINE is set to YES.
1838+
1839+EXTERNAL_SEARCH_ID =
1840+
1841+# The EXTRA_SEARCH_MAPPINGS tag can be used to enable searching through doxygen
1842+# projects other than the one defined by this configuration file, but that are
1843+# all added to the same external search index. Each project needs to have a
1844+# unique id set via EXTERNAL_SEARCH_ID. The search mapping then maps the id of
1845+# to a relative location where the documentation can be found. The format is:
1846+# EXTRA_SEARCH_MAPPINGS = tagname1=loc1 tagname2=loc2 ...
1847+# This tag requires that the tag SEARCHENGINE is set to YES.
1848+
1849+EXTRA_SEARCH_MAPPINGS =
1850+
1851+#---------------------------------------------------------------------------
1852+# Configuration options related to the LaTeX output
1853+#---------------------------------------------------------------------------
1854+
1855+# If the GENERATE_LATEX tag is set to YES doxygen will generate LaTeX output.
1856+# The default value is: YES.
1857+
1858+GENERATE_LATEX = NO
1859+
1860+# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. If a
1861+# relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1862+# it.
1863+# The default directory is: latex.
1864+# This tag requires that the tag GENERATE_LATEX is set to YES.
1865+
1866+LATEX_OUTPUT = latex
1867+
1868+# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
1869+# invoked.
1870+#
1871+# Note that when enabling USE_PDFLATEX this option is only used for generating
1872+# bitmaps for formulas in the HTML output, but not in the Makefile that is
1873+# written to the output directory.
1874+# The default file is: latex.
1875+# This tag requires that the tag GENERATE_LATEX is set to YES.
1876+
1877+LATEX_CMD_NAME = latex
1878+
1879+# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to generate
1880+# index for LaTeX.
1881+# The default file is: makeindex.
1882+# This tag requires that the tag GENERATE_LATEX is set to YES.
1883+
1884+MAKEINDEX_CMD_NAME = makeindex
1885+
1886+# If the COMPACT_LATEX tag is set to YES doxygen generates more compact LaTeX
1887+# documents. This may be useful for small projects and may help to save some
1888+# trees in general.
1889+# The default value is: NO.
1890+# This tag requires that the tag GENERATE_LATEX is set to YES.
1891+
1892+COMPACT_LATEX = YES
1893+
1894+# The PAPER_TYPE tag can be used to set the paper type that is used by the
1895+# printer.
1896+# Possible values are: a4 (210 x 297 mm), letter (8.5 x 11 inches), legal (8.5 x
1897+# 14 inches) and executive (7.25 x 10.5 inches).
1898+# The default value is: a4.
1899+# This tag requires that the tag GENERATE_LATEX is set to YES.
1900+
1901+PAPER_TYPE = a4
1902+
1903+# The EXTRA_PACKAGES tag can be used to specify one or more LaTeX package names
1904+# that should be included in the LaTeX output. To get the times font for
1905+# instance you can specify
1906+# EXTRA_PACKAGES=times
1907+# If left blank no extra packages will be included.
1908+# This tag requires that the tag GENERATE_LATEX is set to YES.
1909+
1910+EXTRA_PACKAGES =
1911+
1912+# The LATEX_HEADER tag can be used to specify a personal LaTeX header for the
1913+# generated LaTeX document. The header should contain everything until the first
1914+# chapter. If it is left blank doxygen will generate a standard header. See
1915+# section "Doxygen usage" for information on how to let doxygen write the
1916+# default header to a separate file.
1917+#
1918+# Note: Only use a user-defined header if you know what you are doing! The
1919+# following commands have a special meaning inside the header: $title,
1920+# $datetime, $date, $doxygenversion, $projectname, $projectnumber. Doxygen will
1921+# replace them by respectively the title of the page, the current date and time,
1922+# only the current date, the version number of doxygen, the project name (see
1923+# PROJECT_NAME), or the project number (see PROJECT_NUMBER).
1924+# This tag requires that the tag GENERATE_LATEX is set to YES.
1925+
1926+LATEX_HEADER =
1927+
1928+# The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for the
1929+# generated LaTeX document. The footer should contain everything after the last
1930+# chapter. If it is left blank doxygen will generate a standard footer.
1931+#
1932+# Note: Only use a user-defined footer if you know what you are doing!
1933+# This tag requires that the tag GENERATE_LATEX is set to YES.
1934+
1935+LATEX_FOOTER =
1936+
1937+# The LATEX_EXTRA_FILES tag can be used to specify one or more extra images or
1938+# other source files which should be copied to the LATEX_OUTPUT output
1939+# directory. Note that the files will be copied as-is; there are no commands or
1940+# markers available.
1941+# This tag requires that the tag GENERATE_LATEX is set to YES.
1942+
1943+LATEX_EXTRA_FILES =
1944+
1945+# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated is
1946+# prepared for conversion to PDF (using ps2pdf or pdflatex). The PDF file will
1947+# contain links (just like the HTML output) instead of page references. This
1948+# makes the output suitable for online browsing using a PDF viewer.
1949+# The default value is: YES.
1950+# This tag requires that the tag GENERATE_LATEX is set to YES.
1951+
1952+PDF_HYPERLINKS = YES
1953+
1954+# If the LATEX_PDFLATEX tag is set to YES, doxygen will use pdflatex to generate
1955+# the PDF file directly from the LaTeX files. Set this option to YES to get a
1956+# higher quality PDF documentation.
1957+# The default value is: YES.
1958+# This tag requires that the tag GENERATE_LATEX is set to YES.
1959+
1960+USE_PDFLATEX = YES
1961+
1962+# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \batchmode
1963+# command to the generated LaTeX files. This will instruct LaTeX to keep running
1964+# if errors occur, instead of asking the user for help. This option is also used
1965+# when generating formulas in HTML.
1966+# The default value is: NO.
1967+# This tag requires that the tag GENERATE_LATEX is set to YES.
1968+
1969+LATEX_BATCHMODE = NO
1970+
1971+# If the LATEX_HIDE_INDICES tag is set to YES then doxygen will not include the
1972+# index chapters (such as File Index, Compound Index, etc.) in the output.
1973+# The default value is: NO.
1974+# This tag requires that the tag GENERATE_LATEX is set to YES.
1975+
1976+LATEX_HIDE_INDICES = NO
1977+
1978+# If the LATEX_SOURCE_CODE tag is set to YES then doxygen will include source
1979+# code with syntax highlighting in the LaTeX output.
1980+#
1981+# Note that which sources are shown also depends on other settings such as
1982+# SOURCE_BROWSER.
1983+# The default value is: NO.
1984+# This tag requires that the tag GENERATE_LATEX is set to YES.
1985+
1986+LATEX_SOURCE_CODE = NO
1987+
1988+# The LATEX_BIB_STYLE tag can be used to specify the style to use for the
1989+# bibliography, e.g. plainnat, or ieeetr. See
1990+# http://en.wikipedia.org/wiki/BibTeX and \cite for more info.
1991+# The default value is: plain.
1992+# This tag requires that the tag GENERATE_LATEX is set to YES.
1993+
1994+LATEX_BIB_STYLE = plain
1995+
1996+#---------------------------------------------------------------------------
1997+# Configuration options related to the RTF output
1998+#---------------------------------------------------------------------------
1999+
2000+# If the GENERATE_RTF tag is set to YES doxygen will generate RTF output. The
2001+# RTF output is optimized for Word 97 and may not look too pretty with other RTF
2002+# readers/editors.
2003+# The default value is: NO.
2004+
2005+GENERATE_RTF = NO
2006+
2007+# The RTF_OUTPUT tag is used to specify where the RTF docs will be put. If a
2008+# relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
2009+# it.
2010+# The default directory is: rtf.
2011+# This tag requires that the tag GENERATE_RTF is set to YES.
2012+
2013+RTF_OUTPUT = rtf
2014+
2015+# If the COMPACT_RTF tag is set to YES doxygen generates more compact RTF
2016+# documents. This may be useful for small projects and may help to save some
2017+# trees in general.
2018+# The default value is: NO.
2019+# This tag requires that the tag GENERATE_RTF is set to YES.
2020+
2021+COMPACT_RTF = NO
2022+
2023+# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated will
2024+# contain hyperlink fields. The RTF file will contain links (just like the HTML
2025+# output) instead of page references. This makes the output suitable for online
2026+# browsing using Word or some other Word compatible readers that support those
2027+# fields.
2028+#
2029+# Note: WordPad (write) and others do not support links.
2030+# The default value is: NO.
2031+# This tag requires that the tag GENERATE_RTF is set to YES.
2032+
2033+RTF_HYPERLINKS = NO
2034+
2035+# Load stylesheet definitions from file. Syntax is similar to doxygen's config
2036+# file, i.e. a series of assignments. You only have to provide replacements,
2037+# missing definitions are set to their default value.
2038+#
2039+# See also section "Doxygen usage" for information on how to generate the
2040+# default style sheet that doxygen normally uses.
2041+# This tag requires that the tag GENERATE_RTF is set to YES.
2042+
2043+RTF_STYLESHEET_FILE =
2044+
2045+# Set optional variables used in the generation of an RTF document. Syntax is
2046+# similar to doxygen's config file. A template extensions file can be generated
2047+# using doxygen -e rtf extensionFile.
2048+# This tag requires that the tag GENERATE_RTF is set to YES.
2049+
2050+RTF_EXTENSIONS_FILE =
2051+
2052+#---------------------------------------------------------------------------
2053+# Configuration options related to the man page output
2054+#---------------------------------------------------------------------------
2055+
2056+# If the GENERATE_MAN tag is set to YES doxygen will generate man pages for
2057+# classes and files.
2058+# The default value is: NO.
2059+
2060+GENERATE_MAN = NO
2061+
2062+# The MAN_OUTPUT tag is used to specify where the man pages will be put. If a
2063+# relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
2064+# it. A directory man3 will be created inside the directory specified by
2065+# MAN_OUTPUT.
2066+# The default directory is: man.
2067+# This tag requires that the tag GENERATE_MAN is set to YES.
2068+
2069+MAN_OUTPUT = man
2070+
2071+# The MAN_EXTENSION tag determines the extension that is added to the generated
2072+# man pages. In case the manual section does not start with a number, the number
2073+# 3 is prepended. The dot (.) at the beginning of the MAN_EXTENSION tag is
2074+# optional.
2075+# The default value is: .3.
2076+# This tag requires that the tag GENERATE_MAN is set to YES.
2077+
2078+MAN_EXTENSION = .3
2079+
2080+# The MAN_SUBDIR tag determines the name of the directory created within
2081+# MAN_OUTPUT in which the man pages are placed. If defaults to man followed by
2082+# MAN_EXTENSION with the initial . removed.
2083+# This tag requires that the tag GENERATE_MAN is set to YES.
2084+
2085+MAN_SUBDIR =
2086+
2087+# If the MAN_LINKS tag is set to YES and doxygen generates man output, then it
2088+# will generate one additional man file for each entity documented in the real
2089+# man page(s). These additional files only source the real man page, but without
2090+# them the man command would be unable to find the correct page.
2091+# The default value is: NO.
2092+# This tag requires that the tag GENERATE_MAN is set to YES.
2093+
2094+MAN_LINKS = NO
2095+
2096+#---------------------------------------------------------------------------
2097+# Configuration options related to the XML output
2098+#---------------------------------------------------------------------------
2099+
2100+# If the GENERATE_XML tag is set to YES doxygen will generate an XML file that
2101+# captures the structure of the code including all documentation.
2102+# The default value is: NO.
2103+
2104+GENERATE_XML = YES
2105+
2106+# The XML_OUTPUT tag is used to specify where the XML pages will be put. If a
2107+# relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
2108+# it.
2109+# The default directory is: xml.
2110+# This tag requires that the tag GENERATE_XML is set to YES.
2111+
2112+XML_OUTPUT = xml
2113+
2114+# If the XML_PROGRAMLISTING tag is set to YES doxygen will dump the program
2115+# listings (including syntax highlighting and cross-referencing information) to
2116+# the XML output. Note that enabling this will significantly increase the size
2117+# of the XML output.
2118+# The default value is: YES.
2119+# This tag requires that the tag GENERATE_XML is set to YES.
2120+
2121+XML_PROGRAMLISTING = YES
2122+
2123+#---------------------------------------------------------------------------
2124+# Configuration options related to the DOCBOOK output
2125+#---------------------------------------------------------------------------
2126+
2127+# If the GENERATE_DOCBOOK tag is set to YES doxygen will generate Docbook files
2128+# that can be used to generate PDF.
2129+# The default value is: NO.
2130+
2131+GENERATE_DOCBOOK = NO
2132+
2133+# The DOCBOOK_OUTPUT tag is used to specify where the Docbook pages will be put.
2134+# If a relative path is entered the value of OUTPUT_DIRECTORY will be put in
2135+# front of it.
2136+# The default directory is: docbook.
2137+# This tag requires that the tag GENERATE_DOCBOOK is set to YES.
2138+
2139+DOCBOOK_OUTPUT = docbook
2140+
2141+#---------------------------------------------------------------------------
2142+# Configuration options for the AutoGen Definitions output
2143+#---------------------------------------------------------------------------
2144+
2145+# If the GENERATE_AUTOGEN_DEF tag is set to YES doxygen will generate an AutoGen
2146+# Definitions (see http://autogen.sf.net) file that captures the structure of
2147+# the code including all documentation. Note that this feature is still
2148+# experimental and incomplete at the moment.
2149+# The default value is: NO.
2150+
2151+GENERATE_AUTOGEN_DEF = NO
2152+
2153+#---------------------------------------------------------------------------
2154+# Configuration options related to the Perl module output
2155+#---------------------------------------------------------------------------
2156+
2157+# If the GENERATE_PERLMOD tag is set to YES doxygen will generate a Perl module
2158+# file that captures the structure of the code including all documentation.
2159+#
2160+# Note that this feature is still experimental and incomplete at the moment.
2161+# The default value is: NO.
2162+
2163+GENERATE_PERLMOD = NO
2164+
2165+# If the PERLMOD_LATEX tag is set to YES doxygen will generate the necessary
2166+# Makefile rules, Perl scripts and LaTeX code to be able to generate PDF and DVI
2167+# output from the Perl module output.
2168+# The default value is: NO.
2169+# This tag requires that the tag GENERATE_PERLMOD is set to YES.
2170+
2171+PERLMOD_LATEX = NO
2172+
2173+# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be nicely
2174+# formatted so it can be parsed by a human reader. This is useful if you want to
2175+# understand what is going on. On the other hand, if this tag is set to NO the
2176+# size of the Perl module output will be much smaller and Perl will parse it
2177+# just the same.
2178+# The default value is: YES.
2179+# This tag requires that the tag GENERATE_PERLMOD is set to YES.
2180+
2181+PERLMOD_PRETTY = YES
2182+
2183+# The names of the make variables in the generated doxyrules.make file are
2184+# prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. This is useful
2185+# so different doxyrules.make files included by the same Makefile don't
2186+# overwrite each other's variables.
2187+# This tag requires that the tag GENERATE_PERLMOD is set to YES.
2188+
2189+PERLMOD_MAKEVAR_PREFIX =
2190+
2191+#---------------------------------------------------------------------------
2192+# Configuration options related to the preprocessor
2193+#---------------------------------------------------------------------------
2194+
2195+# If the ENABLE_PREPROCESSING tag is set to YES doxygen will evaluate all
2196+# C-preprocessor directives found in the sources and include files.
2197+# The default value is: YES.
2198+
2199+ENABLE_PREPROCESSING = YES
2200+
2201+# If the MACRO_EXPANSION tag is set to YES doxygen will expand all macro names
2202+# in the source code. If set to NO only conditional compilation will be
2203+# performed. Macro expansion can be done in a controlled way by setting
2204+# EXPAND_ONLY_PREDEF to YES.
2205+# The default value is: NO.
2206+# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2207+
2208+MACRO_EXPANSION = YES
2209+
2210+# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES then
2211+# the macro expansion is limited to the macros specified with the PREDEFINED and
2212+# EXPAND_AS_DEFINED tags.
2213+# The default value is: NO.
2214+# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2215+
2216+EXPAND_ONLY_PREDEF = YES
2217+
2218+# If the SEARCH_INCLUDES tag is set to YES the includes files in the
2219+# INCLUDE_PATH will be searched if a #include is found.
2220+# The default value is: YES.
2221+# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2222+
2223+SEARCH_INCLUDES = YES
2224+
2225+# The INCLUDE_PATH tag can be used to specify one or more directories that
2226+# contain include files that are not input files but should be processed by the
2227+# preprocessor.
2228+# This tag requires that the tag SEARCH_INCLUDES is set to YES.
2229+
2230+INCLUDE_PATH =
2231+
2232+# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
2233+# patterns (like *.h and *.hpp) to filter out the header-files in the
2234+# directories. If left blank, the patterns specified with FILE_PATTERNS will be
2235+# used.
2236+# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2237+
2238+INCLUDE_FILE_PATTERNS =
2239+
2240+# The PREDEFINED tag can be used to specify one or more macro names that are
2241+# defined before the preprocessor is started (similar to the -D option of e.g.
2242+# gcc). The argument of the tag is a list of macros of the form: name or
2243+# name=definition (no spaces). If the definition and the "=" are omitted, "=1"
2244+# is assumed. To prevent a macro definition from being undefined via #undef or
2245+# recursively expanded use the := operator instead of the = operator.
2246+# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2247+
2248+PREDEFINED = Q_DECL_EXPORT:= \
2249+ Q_DECL_PRIVATE:=
2250+
2251+# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then this
2252+# tag can be used to specify a list of macro names that should be expanded. The
2253+# macro definition that is found in the sources will be used. Use the PREDEFINED
2254+# tag if you want to use a different macro definition that overrules the
2255+# definition found in the source code.
2256+# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2257+
2258+EXPAND_AS_DEFINED =
2259+
2260+# If the SKIP_FUNCTION_MACROS tag is set to YES then doxygen's preprocessor will
2261+# remove all references to function-like macros that are alone on a line, have
2262+# an all uppercase name, and do not end with a semicolon. Such function macros
2263+# are typically used for boiler-plate code, and will confuse the parser if not
2264+# removed.
2265+# The default value is: YES.
2266+# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2267+
2268+SKIP_FUNCTION_MACROS = YES
2269+
2270+#---------------------------------------------------------------------------
2271+# Configuration options related to external references
2272+#---------------------------------------------------------------------------
2273+
2274+# The TAGFILES tag can be used to specify one or more tag files. For each tag
2275+# file the location of the external documentation should be added. The format of
2276+# a tag file without this location is as follows:
2277+# TAGFILES = file1 file2 ...
2278+# Adding location for the tag files is done as follows:
2279+# TAGFILES = file1=loc1 "file2 = loc2" ...
2280+# where loc1 and loc2 can be relative or absolute paths or URLs. See the
2281+# section "Linking to external documentation" for more information about the use
2282+# of tag files.
2283+# Note: Each tag file must have a unique name (where the name does NOT include
2284+# the path). If a tag file is not located in the directory in which doxygen is
2285+# run, you must also specify the path to the tagfile here.
2286+
2287+TAGFILES =
2288+
2289+# When a file name is specified after GENERATE_TAGFILE, doxygen will create a
2290+# tag file that is based on the input files it reads. See section "Linking to
2291+# external documentation" for more information about the usage of tag files.
2292+
2293+GENERATE_TAGFILE =
2294+
2295+# If the ALLEXTERNALS tag is set to YES all external class will be listed in the
2296+# class index. If set to NO only the inherited external classes will be listed.
2297+# The default value is: NO.
2298+
2299+ALLEXTERNALS = NO
2300+
2301+# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed in
2302+# the modules index. If set to NO, only the current project's groups will be
2303+# listed.
2304+# The default value is: YES.
2305+
2306+EXTERNAL_GROUPS = YES
2307+
2308+# If the EXTERNAL_PAGES tag is set to YES all external pages will be listed in
2309+# the related pages index. If set to NO, only the current project's pages will
2310+# be listed.
2311+# The default value is: YES.
2312+
2313+EXTERNAL_PAGES = YES
2314+
2315+# The PERL_PATH should be the absolute path and name of the perl script
2316+# interpreter (i.e. the result of 'which perl').
2317+# The default file (with absolute path) is: /usr/bin/perl.
2318+
2319+PERL_PATH = /usr/bin/perl
2320+
2321+#---------------------------------------------------------------------------
2322+# Configuration options related to the dot tool
2323+#---------------------------------------------------------------------------
2324+
2325+# If the CLASS_DIAGRAMS tag is set to YES doxygen will generate a class diagram
2326+# (in HTML and LaTeX) for classes with base or super classes. Setting the tag to
2327+# NO turns the diagrams off. Note that this option also works with HAVE_DOT
2328+# disabled, but it is recommended to install and use dot, since it yields more
2329+# powerful graphs.
2330+# The default value is: YES.
2331+
2332+CLASS_DIAGRAMS = YES
2333+
2334+# You can define message sequence charts within doxygen comments using the \msc
2335+# command. Doxygen will then run the mscgen tool (see:
2336+# http://www.mcternan.me.uk/mscgen/)) to produce the chart and insert it in the
2337+# documentation. The MSCGEN_PATH tag allows you to specify the directory where
2338+# the mscgen tool resides. If left empty the tool is assumed to be found in the
2339+# default search path.
2340+
2341+MSCGEN_PATH =
2342+
2343+# You can include diagrams made with dia in doxygen documentation. Doxygen will
2344+# then run dia to produce the diagram and insert it in the documentation. The
2345+# DIA_PATH tag allows you to specify the directory where the dia binary resides.
2346+# If left empty dia is assumed to be found in the default search path.
2347+
2348+DIA_PATH =
2349+
2350+# If set to YES, the inheritance and collaboration graphs will hide inheritance
2351+# and usage relations if the target is undocumented or is not a class.
2352+# The default value is: YES.
2353+
2354+HIDE_UNDOC_RELATIONS = NO
2355+
2356+# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
2357+# available from the path. This tool is part of Graphviz (see:
2358+# http://www.graphviz.org/), a graph visualization toolkit from AT&T and Lucent
2359+# Bell Labs. The other options in this section have no effect if this option is
2360+# set to NO
2361+# The default value is: YES.
2362+
2363+HAVE_DOT = YES
2364+
2365+# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is allowed
2366+# to run in parallel. When set to 0 doxygen will base this on the number of
2367+# processors available in the system. You can set it explicitly to a value
2368+# larger than 0 to get control over the balance between CPU load and processing
2369+# speed.
2370+# Minimum value: 0, maximum value: 32, default value: 0.
2371+# This tag requires that the tag HAVE_DOT is set to YES.
2372+
2373+DOT_NUM_THREADS = 0
2374+
2375+# When you want a differently looking font n the dot files that doxygen
2376+# generates you can specify the font name using DOT_FONTNAME. You need to make
2377+# sure dot is able to find the font, which can be done by putting it in a
2378+# standard location or by setting the DOTFONTPATH environment variable or by
2379+# setting DOT_FONTPATH to the directory containing the font.
2380+# The default value is: Helvetica.
2381+# This tag requires that the tag HAVE_DOT is set to YES.
2382+
2383+DOT_FONTNAME = Helvetica
2384+
2385+# The DOT_FONTSIZE tag can be used to set the size (in points) of the font of
2386+# dot graphs.
2387+# Minimum value: 4, maximum value: 24, default value: 10.
2388+# This tag requires that the tag HAVE_DOT is set to YES.
2389+
2390+DOT_FONTSIZE = 10
2391+
2392+# By default doxygen will tell dot to use the default font as specified with
2393+# DOT_FONTNAME. If you specify a different font using DOT_FONTNAME you can set
2394+# the path where dot can find it using this tag.
2395+# This tag requires that the tag HAVE_DOT is set to YES.
2396+
2397+DOT_FONTPATH =
2398+
2399+# If the CLASS_GRAPH tag is set to YES then doxygen will generate a graph for
2400+# each documented class showing the direct and indirect inheritance relations.
2401+# Setting this tag to YES will force the CLASS_DIAGRAMS tag to NO.
2402+# The default value is: YES.
2403+# This tag requires that the tag HAVE_DOT is set to YES.
2404+
2405+CLASS_GRAPH = YES
2406+
2407+# If the COLLABORATION_GRAPH tag is set to YES then doxygen will generate a
2408+# graph for each documented class showing the direct and indirect implementation
2409+# dependencies (inheritance, containment, and class references variables) of the
2410+# class with other documented classes.
2411+# The default value is: YES.
2412+# This tag requires that the tag HAVE_DOT is set to YES.
2413+
2414+COLLABORATION_GRAPH = YES
2415+
2416+# If the GROUP_GRAPHS tag is set to YES then doxygen will generate a graph for
2417+# groups, showing the direct groups dependencies.
2418+# The default value is: YES.
2419+# This tag requires that the tag HAVE_DOT is set to YES.
2420+
2421+GROUP_GRAPHS = YES
2422+
2423+# If the UML_LOOK tag is set to YES doxygen will generate inheritance and
2424+# collaboration diagrams in a style similar to the OMG's Unified Modeling
2425+# Language.
2426+# The default value is: NO.
2427+# This tag requires that the tag HAVE_DOT is set to YES.
2428+
2429+UML_LOOK = YES
2430+
2431+# If the UML_LOOK tag is enabled, the fields and methods are shown inside the
2432+# class node. If there are many fields or methods and many nodes the graph may
2433+# become too big to be useful. The UML_LIMIT_NUM_FIELDS threshold limits the
2434+# number of items for each type to make the size more manageable. Set this to 0
2435+# for no limit. Note that the threshold may be exceeded by 50% before the limit
2436+# is enforced. So when you set the threshold to 10, up to 15 fields may appear,
2437+# but if the number exceeds 15, the total amount of fields shown is limited to
2438+# 10.
2439+# Minimum value: 0, maximum value: 100, default value: 10.
2440+# This tag requires that the tag HAVE_DOT is set to YES.
2441+
2442+UML_LIMIT_NUM_FIELDS = 10
2443+
2444+# If the TEMPLATE_RELATIONS tag is set to YES then the inheritance and
2445+# collaboration graphs will show the relations between templates and their
2446+# instances.
2447+# The default value is: NO.
2448+# This tag requires that the tag HAVE_DOT is set to YES.
2449+
2450+TEMPLATE_RELATIONS = NO
2451+
2452+# If the INCLUDE_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are set to
2453+# YES then doxygen will generate a graph for each documented file showing the
2454+# direct and indirect include dependencies of the file with other documented
2455+# files.
2456+# The default value is: YES.
2457+# This tag requires that the tag HAVE_DOT is set to YES.
2458+
2459+INCLUDE_GRAPH = YES
2460+
2461+# If the INCLUDED_BY_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are
2462+# set to YES then doxygen will generate a graph for each documented file showing
2463+# the direct and indirect include dependencies of the file with other documented
2464+# files.
2465+# The default value is: YES.
2466+# This tag requires that the tag HAVE_DOT is set to YES.
2467+
2468+INCLUDED_BY_GRAPH = YES
2469+
2470+# If the CALL_GRAPH tag is set to YES then doxygen will generate a call
2471+# dependency graph for every global function or class method.
2472+#
2473+# Note that enabling this option will significantly increase the time of a run.
2474+# So in most cases it will be better to enable call graphs for selected
2475+# functions only using the \callgraph command.
2476+# The default value is: NO.
2477+# This tag requires that the tag HAVE_DOT is set to YES.
2478+
2479+CALL_GRAPH = YES
2480+
2481+# If the CALLER_GRAPH tag is set to YES then doxygen will generate a caller
2482+# dependency graph for every global function or class method.
2483+#
2484+# Note that enabling this option will significantly increase the time of a run.
2485+# So in most cases it will be better to enable caller graphs for selected
2486+# functions only using the \callergraph command.
2487+# The default value is: NO.
2488+# This tag requires that the tag HAVE_DOT is set to YES.
2489+
2490+CALLER_GRAPH = NO
2491+
2492+# If the GRAPHICAL_HIERARCHY tag is set to YES then doxygen will graphical
2493+# hierarchy of all classes instead of a textual one.
2494+# The default value is: YES.
2495+# This tag requires that the tag HAVE_DOT is set to YES.
2496+
2497+GRAPHICAL_HIERARCHY = YES
2498+
2499+# If the DIRECTORY_GRAPH tag is set to YES then doxygen will show the
2500+# dependencies a directory has on other directories in a graphical way. The
2501+# dependency relations are determined by the #include relations between the
2502+# files in the directories.
2503+# The default value is: YES.
2504+# This tag requires that the tag HAVE_DOT is set to YES.
2505+
2506+DIRECTORY_GRAPH = YES
2507+
2508+# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
2509+# generated by dot.
2510+# Note: If you choose svg you need to set HTML_FILE_EXTENSION to xhtml in order
2511+# to make the SVG files visible in IE 9+ (other browsers do not have this
2512+# requirement).
2513+# Possible values are: png, png:cairo, png:cairo:cairo, png:cairo:gd, png:gd,
2514+# png:gd:gd, jpg, jpg:cairo, jpg:cairo:gd, jpg:gd, jpg:gd:gd, gif, gif:cairo,
2515+# gif:cairo:gd, gif:gd, gif:gd:gd and svg.
2516+# The default value is: png.
2517+# This tag requires that the tag HAVE_DOT is set to YES.
2518+
2519+DOT_IMAGE_FORMAT = png
2520+
2521+# If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to
2522+# enable generation of interactive SVG images that allow zooming and panning.
2523+#
2524+# Note that this requires a modern browser other than Internet Explorer. Tested
2525+# and working are Firefox, Chrome, Safari, and Opera.
2526+# Note: For IE 9+ you need to set HTML_FILE_EXTENSION to xhtml in order to make
2527+# the SVG files visible. Older versions of IE do not have SVG support.
2528+# The default value is: NO.
2529+# This tag requires that the tag HAVE_DOT is set to YES.
2530+
2531+INTERACTIVE_SVG = YES
2532+
2533+# The DOT_PATH tag can be used to specify the path where the dot tool can be
2534+# found. If left blank, it is assumed the dot tool can be found in the path.
2535+# This tag requires that the tag HAVE_DOT is set to YES.
2536+
2537+DOT_PATH =
2538+
2539+# The DOTFILE_DIRS tag can be used to specify one or more directories that
2540+# contain dot files that are included in the documentation (see the \dotfile
2541+# command).
2542+# This tag requires that the tag HAVE_DOT is set to YES.
2543+
2544+DOTFILE_DIRS =
2545+
2546+# The MSCFILE_DIRS tag can be used to specify one or more directories that
2547+# contain msc files that are included in the documentation (see the \mscfile
2548+# command).
2549+
2550+MSCFILE_DIRS =
2551+
2552+# The DIAFILE_DIRS tag can be used to specify one or more directories that
2553+# contain dia files that are included in the documentation (see the \diafile
2554+# command).
2555+
2556+DIAFILE_DIRS =
2557+
2558+# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of nodes
2559+# that will be shown in the graph. If the number of nodes in a graph becomes
2560+# larger than this value, doxygen will truncate the graph, which is visualized
2561+# by representing a node as a red box. Note that doxygen if the number of direct
2562+# children of the root node in a graph is already larger than
2563+# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note that
2564+# the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
2565+# Minimum value: 0, maximum value: 10000, default value: 50.
2566+# This tag requires that the tag HAVE_DOT is set to YES.
2567+
2568+DOT_GRAPH_MAX_NODES = 50
2569+
2570+# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the graphs
2571+# generated by dot. A depth value of 3 means that only nodes reachable from the
2572+# root by following a path via at most 3 edges will be shown. Nodes that lay
2573+# further from the root node will be omitted. Note that setting this option to 1
2574+# or 2 may greatly reduce the computation time needed for large code bases. Also
2575+# note that the size of a graph can be further restricted by
2576+# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
2577+# Minimum value: 0, maximum value: 1000, default value: 0.
2578+# This tag requires that the tag HAVE_DOT is set to YES.
2579+
2580+MAX_DOT_GRAPH_DEPTH = 0
2581+
2582+# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
2583+# background. This is disabled by default, because dot on Windows does not seem
2584+# to support this out of the box.
2585+#
2586+# Warning: Depending on the platform used, enabling this option may lead to
2587+# badly anti-aliased labels on the edges of a graph (i.e. they become hard to
2588+# read).
2589+# The default value is: NO.
2590+# This tag requires that the tag HAVE_DOT is set to YES.
2591+
2592+DOT_TRANSPARENT = YES
2593+
2594+# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
2595+# files in one run (i.e. multiple -o and -T options on the command line). This
2596+# makes dot run faster, but since only newer versions of dot (>1.8.10) support
2597+# this, this feature is disabled by default.
2598+# The default value is: NO.
2599+# This tag requires that the tag HAVE_DOT is set to YES.
2600+
2601+DOT_MULTI_TARGETS = YES
2602+
2603+# If the GENERATE_LEGEND tag is set to YES doxygen will generate a legend page
2604+# explaining the meaning of the various boxes and arrows in the dot generated
2605+# graphs.
2606+# The default value is: YES.
2607+# This tag requires that the tag HAVE_DOT is set to YES.
2608+
2609+GENERATE_LEGEND = YES
2610+
2611+# If the DOT_CLEANUP tag is set to YES doxygen will remove the intermediate dot
2612+# files that are used to generate the various graphs.
2613+# The default value is: YES.
2614+# This tag requires that the tag HAVE_DOT is set to YES.
2615+
2616+DOT_CLEANUP = YES
2617
2618=== added directory 'doc/qt/cpp/css'
2619=== added file 'doc/qt/cpp/css/base.css'
2620--- doc/qt/cpp/css/base.css 1970-01-01 00:00:00 +0000
2621+++ doc/qt/cpp/css/base.css 2014-08-19 17:36:21 +0000
2622@@ -0,0 +1,638 @@
2623+/**
2624+* Ubuntu Developer base stylesheet
2625+*
2626+* A base stylesheet containing site-wide styles
2627+*
2628+* @project Ubuntu Developer
2629+* @version 1.0
2630+* @author Canonical Web Team: Steve Edwards
2631+* @copyright 2011 Canonical Ltd.
2632+*/
2633+
2634+/**
2635+* @section Global
2636+*/
2637+
2638+body {
2639+ font-family: 'Ubuntu', 'Ubuntu Beta', UbuntuBeta, Ubuntu, 'Bitstream Vera Sans', 'DejaVu Sans', Tahoma, sans-serif;
2640+ font-size: 13px;
2641+ line-height: 1.4;
2642+ color: #333;
2643+}
2644+a {
2645+ color: #dd4814;
2646+ text-decoration: none;
2647+ outline: 0;
2648+}
2649+p, dl {
2650+ margin-bottom: 10px;
2651+}
2652+strong {
2653+ font-weight: bold;
2654+}
2655+em {
2656+ font-style: italic;
2657+}
2658+code{
2659+ padding: 10px;
2660+ font-family: 'Ubuntu Mono', 'Consolas', 'Monaco', 'DejaVu Sans Mono', Courier, monospace;
2661+ background-color: #fdf6f2;
2662+ display: block;
2663+ margin-bottom: 10px;
2664+ -moz-border-radius: 4px;
2665+ -webkit-border-radius: 4px;
2666+ border-radius: 4px;
2667+}
2668+h1 {
2669+ font-size: 36px;
2670+ line-height: 1.1;
2671+ margin-bottom: 20px;
2672+}
2673+article h1,
2674+h2 {
2675+ font-size: 24px;
2676+ line-height: 1.2;
2677+ margin-bottom: 14px;
2678+}
2679+h3 {
2680+ font-size: 16px;
2681+ line-height: 1.3;
2682+ margin-bottom: 8px;
2683+}
2684+h4 {
2685+ font-weight: bold;
2686+}
2687+
2688+time {
2689+ color:#999;
2690+}
2691+
2692+/**
2693+* @section Structure
2694+*/
2695+
2696+.header-login,
2697+.header-navigation div,
2698+.header-content div {
2699+ margin: 0 auto;
2700+ width: 940px;
2701+}
2702+
2703+.header-content h1{
2704+ background-color:#ffffff;
2705+ display:inline-block;
2706+}
2707+
2708+.header-content h2{
2709+ background-color:#ffffff;
2710+ display:table;
2711+}
2712+
2713+.header-login ul {
2714+ margin: 4px 0;
2715+ float: right;
2716+}
2717+.header-login li {
2718+ margin-right: 10px;
2719+ float: left;
2720+}
2721+.header-login a {
2722+ color: #333;
2723+}
2724+.header-navigation {
2725+ border-top: 2px solid #dd4814;
2726+ border-bottom: 2px solid #dd4814;
2727+ background-color: #fff;
2728+ height: 54px;
2729+ clear: right;
2730+ overflow: hidden;
2731+}
2732+.header-navigation nav ul {
2733+ border-right: 1px solid #dd4814;
2734+ float: right;
2735+}
2736+.header-navigation nav li {
2737+ border-left: 1px solid #dd4814;
2738+ float: left;
2739+ height: 54px;
2740+}
2741+.header-navigation nav a {
2742+ padding: 18px 14px 0;
2743+ font-size: 14px;
2744+ display: block;
2745+ height: 36px;
2746+}
2747+.header-navigation nav a:hover {
2748+ background-color: #fcece7;
2749+}
2750+.header-navigation nav .current_page_item a,
2751+.header-navigation nav .current_page_parent a,
2752+.header-navigation nav .current_page_ancestor a {
2753+ background-color: #dd4814;
2754+ color: #fff;
2755+}
2756+.header-navigation input {
2757+ margin: 12px 10px 0 10px;
2758+ padding: 5px;
2759+ border-top: 1px solid #a1a1a1;
2760+ border-right: 1px solid #e0e0e0;
2761+ border-bottom: 1px solid #fff;
2762+ border-left: 1px solid #e0e0e0;
2763+ width: 90px;
2764+ font-style: italic;
2765+ color: #ccc;
2766+ -moz-border-radius: 3px;
2767+ -webkit-border-radius: 3px;
2768+ border-radius: 3px;
2769+ -moz-box-shadow: inset 0 1px 1px #e0e0e0;
2770+ -webkit-box-shadow: inset 0 1px 1px #e0e0e0;
2771+ box-shadow: inset 0 1px 1px #e0e0e0;
2772+}
2773+.header-navigation h2 {
2774+ margin: 18px 0 0 6px;
2775+ text-transform: lowercase;
2776+ font-size: 22px;
2777+ color: #dd4814;
2778+ float: left;
2779+}
2780+.header-navigation .logo-ubuntu {
2781+ margin-top: 12px;
2782+ float: left;
2783+}
2784+.header-content .header-navigation-secondary {
2785+ margin-bottom: 40px;
2786+ padding: 0;
2787+ position: relative;
2788+ z-index: 2;
2789+}
2790+.header-navigation-secondary div {
2791+ padding: 0;
2792+ border: 2px solid #dd4814;
2793+ -moz-border-radius: 0px 0px 4px 4px;
2794+ -webkit-border-radius: 0px 0px 4px 4px;
2795+ border-radius: 0px 0px 4px 4px;
2796+ background: #fff;
2797+ border-top: 0px;
2798+ width: 936px;
2799+}
2800+.header-navigation-secondary nav li {
2801+ float: left;
2802+}
2803+.header-navigation-secondary nav li a {
2804+ color: #333;
2805+ display: block;
2806+ height: 25px;
2807+ padding: 8px 8px 0;
2808+}
2809+.header-navigation-secondary nav li:hover,
2810+.header-navigation-secondary nav .current_page_item a {
2811+ background: url("../img/sec-nav-hover.gif");
2812+}
2813+.header-content {
2814+ padding-bottom: 30px;
2815+ border-bottom: 1px solid #e0e0e0;
2816+ -moz-box-shadow: 0 1px 3px #e0e0e0;
2817+ -webkit-box-shadow: 0 1px 3px #e0e0e0;
2818+ box-shadow: 0 1px 3px #e0e0e0;
2819+ margin-bottom: 3px;
2820+ position: relative;
2821+ overflow: hidden;
2822+}
2823+footer {
2824+ padding: 10px 10px 40px 10px;
2825+ position: relative;
2826+ -moz-border-radius: 0 0 4px 4px;
2827+ -webkit-border-radius: 0 0 4px 4px;
2828+ border-radius: 0 0 4px 4px;
2829+ font-size: 12px;
2830+ background: url("../img/background-footer.png") repeat scroll 0 0 #f7f6f5;
2831+}
2832+footer div {
2833+ margin: 0 auto;
2834+ padding: 0 10px;
2835+ width: 940px;
2836+}
2837+footer a {
2838+ color: #000;
2839+}
2840+footer nav ul {
2841+ margin: 10px 17px 30px 0;
2842+ width: 172px;
2843+ display: inline-block;
2844+ vertical-align: top;
2845+ height: auto;
2846+ zoom: 1;
2847+ *display: inline;
2848+}
2849+footer nav ul.last {
2850+ margin-right: 0;
2851+}
2852+footer nav li {
2853+ margin-bottom: 8px;
2854+}
2855+footer nav li:first-child {
2856+ font-weight: bold;
2857+}
2858+footer p {
2859+ margin-bottom: 0;
2860+}
2861+#content {
2862+ padding-top: 35px;
2863+}
2864+.arrow-nav {
2865+ display: none;
2866+ position: absolute;
2867+ top: -1px;
2868+ z-index: 3;
2869+}
2870+.shadow {
2871+ margin: 30px 0 3px 0;
2872+ border-bottom: 1px solid #e0e0e0;
2873+ -moz-box-shadow: 0 2px 3px #e0e0e0;
2874+ -webkit-box-shadow: 0 2px 3px #e0e0e0;
2875+ box-shadow: 0 2px 3px #e0e0e0;
2876+ height: 3px;
2877+}
2878+
2879+/**
2880+* @section Site-wide
2881+*/
2882+
2883+#content h2{
2884+ font-size:24px;
2885+}
2886+
2887+.box-orange {
2888+ padding: 10px;
2889+ border: 3px solid #dd4814;
2890+ -moz-border-radius: 4px;
2891+ -webkit-border-radius: 4px;
2892+ border-radius: 4px;
2893+}
2894+.box-orange .link-action-small {
2895+ float: right;
2896+ margin: 0 0 0 20px;
2897+}
2898+.link-bug {
2899+ margin-left: 10px;
2900+ color: #999;
2901+}
2902+.link-action {
2903+ float: left;
2904+ margin-bottom: 20px;
2905+ padding: 8px 12px;
2906+ display: block;
2907+ background-color: #dd4814;
2908+ color: #fff;
2909+ -moz-border-radius: 20px;
2910+ -webkit-border-radius: 20px;
2911+ border-radius: 20px;
2912+ font-size: 16px;
2913+ line-height: 1.3;
2914+ border-top: 3px solid #e6633a;
2915+ border-bottom: 3px solid #c03d14;
2916+}
2917+.link-action2 {
2918+ float: left;
2919+ display: block;
2920+ color: #fff;
2921+ font-size: 16px;
2922+ line-height: 1.3;
2923+}
2924+.link-action2 span{
2925+ display:block;
2926+ float:left;
2927+}
2928+.link-action2 .cta-left{
2929+ background:url(../img/button-cta-left.png) no-repeat;
2930+ width:22px;
2931+ height:48px;
2932+}
2933+.link-action2 .cta-center{
2934+ background:url(../img/button-cta-slice.png) repeat-x;
2935+ line-height:45px;
2936+ height:48px;
2937+}
2938+.link-action2 .cta-right{
2939+ background:url(../img/button-cta-right.png) no-repeat;
2940+ width:22px;
2941+ height:48px;
2942+}
2943+
2944+.link-action-small {
2945+ float: left;
2946+ display: block;
2947+ color: #fff;
2948+ font-size: 16px;
2949+}
2950+.link-action-small span{
2951+ display:block;
2952+ float:left;
2953+ height:42px;
2954+}
2955+.link-action-small .cta-left{
2956+ background:url(../img/button-cta-left-small.png) no-repeat;
2957+ width:19px;
2958+}
2959+.link-action-small .cta-center{
2960+ background:url(../img/button-cta-slice-small.png) repeat-x;
2961+ line-height:42px;
2962+}
2963+.link-action-small .cta-right{
2964+ background:url(../img/button-cta-right-small.png) no-repeat;
2965+ width:19px;
2966+}
2967+
2968+.link-action:active {
2969+ position: relative;
2970+ top: 1px;
2971+}
2972+.link-action2:active {
2973+ position: relative;
2974+ top: 1px;
2975+}
2976+.link-action-small:active {
2977+ position: relative;
2978+ top: 1px;
2979+}
2980+.list-bullets li {
2981+ margin-bottom: 10px;
2982+ list-style: disc;
2983+ list-style-position: inside;
2984+}
2985+.box {
2986+ margin-bottom: 30px;
2987+ padding: 15px;
2988+ border: 1px solid #aea79f;
2989+ -moz-border-radius: 4px;
2990+ -webkit-border-radius: 4px;
2991+ border-radius: 4px;
2992+}
2993+.box-padded {
2994+ margin-bottom: 30px;
2995+ padding: 5px;
2996+ border: 2px solid #aea79f;
2997+ -moz-border-radius: 4px;
2998+ -webkit-border-radius: 4px;
2999+ border-radius: 4px;
3000+ background: url("../img/pattern-featured.gif") repeat scroll 0 0 #ebe9e7;
3001+ overflow: hidden;
3002+}
3003+.box-padded h3 {
3004+ margin: 5px 0 10px 5px;
3005+}
3006+.box-padded div {
3007+ padding: 10px;
3008+ border: 1px solid #aea79f;
3009+ -moz-border-radius: 4px;
3010+ -webkit-border-radius: 4px;
3011+ border-radius: 4px;
3012+ background-color: #fff;
3013+ overflow: hidden;
3014+}
3015+.box-padded li {
3016+ padding: 0 10px;
3017+ float: left;
3018+ width: 211px;
3019+ border-right: 1px dotted #aea79f;
3020+}
3021+.box-padded li.first {
3022+ padding: 0;
3023+ margin-bottom: 0;
3024+}
3025+.box-padded li.last {
3026+ border: 0;
3027+ width: 217px;
3028+}
3029+.box-padded img {
3030+ margin: 0 10px 50px 0;
3031+ float: left;
3032+ -moz-border-radius: 8px;
3033+ -webkit-border-radius: 8px;
3034+ border-radius: 8px;
3035+}
3036+.box-clear {
3037+ margin-bottom: 40px;
3038+}
3039+.box-clear .grid-4.first {
3040+ margin-right: 15px;
3041+ padding-right: 15px;
3042+}
3043+.box-clear .grid-4 {
3044+ margin-left: 0;
3045+ margin-right: 10px;
3046+ padding-right: 10px;
3047+ width: 298px;
3048+}
3049+.box-clear time {
3050+ display: block;
3051+ border-bottom: 1px dotted #aea79f;
3052+ padding-bottom: 10px;
3053+ margin-bottom: 10px;
3054+}
3055+.box-clear div.first {
3056+ border-right: 1px dotted #aea79f;
3057+}
3058+.box-clear a {
3059+ display: block;
3060+}
3061+.box-clear .rss {
3062+ background: url("../img/rss.jpg") no-repeat scroll 0 center;
3063+ padding-left: 20px;
3064+}
3065+.box-clear .location {
3066+ display: block;
3067+ margin-bottom: 1px;
3068+}
3069+.box-clear .last {
3070+ margin: 0;
3071+ padding-right: 0;
3072+ -moz-border-radius: 4px;
3073+ -webkit-border-radius: 4px;
3074+ border-radius: 4px;
3075+ width: 293px;
3076+}
3077+
3078+/* Widgets */
3079+
3080+.ui-state-focus {
3081+ outline: none;
3082+}
3083+.ui-accordion {
3084+ border-bottom: 1px dotted #aea79f;
3085+}
3086+.ui-accordion a {
3087+ display: block;
3088+}
3089+.ui-accordion h3 {
3090+ margin-bottom: 0;
3091+ border-top: 1px dotted #aea79f;
3092+ position: relative;
3093+ font-size: 13px;
3094+ font-weight: bold;
3095+}
3096+.ui-accordion h3 a {
3097+ padding: 10px 0;
3098+ color: #333;
3099+}
3100+.ui-accordion h4 {
3101+ margin-bottom: 5px;
3102+}
3103+.ui-accordion div fieldset {
3104+ padding-bottom: 5px;
3105+}
3106+.ui-accordion div li,
3107+.ui-accordion div input {
3108+ margin-bottom: 10px;
3109+}
3110+.ui-accordion .ui-icon {
3111+ position: absolute;
3112+ top: 15px;
3113+ right: 0;
3114+ display: block;
3115+ width: 8px;
3116+ height: 8px;
3117+ background: url("../img/icon-accordion-inactive.png") 0 0 no-repeat transparent;
3118+}
3119+.ui-accordion .ui-state-active .ui-icon {
3120+ background-image: url("../img/icon-accordion-active.png");
3121+}
3122+.ui-accordion .current_page_item a {
3123+ color: #333;
3124+}
3125+.container-tweet {
3126+ -moz-border-radius: 4px 4px 4px 4px;
3127+ -webkit-border-radius: 4px 4px 4px 4px;
3128+ border-radius: 4px 4px 4px 4px;
3129+ padding: 10px 10px 10px;
3130+ background-color: #f7f7f7;
3131+}
3132+.container-tweet .tweet-follow {
3133+ margin-top: 10px;
3134+ margin-bottom: -10px;
3135+ padding-left: 55px;
3136+ padding-bottom: 6px;
3137+ background: url("../img/tweet-follow.png") 0 5px no-repeat;
3138+ display: block;
3139+}
3140+.container-tweet .tweet-follow span {
3141+ font-size: 16px;
3142+ font-weight: bold;
3143+ line-height: 1.2;
3144+ display: block;
3145+}
3146+.tweet a {
3147+ display: inline;
3148+}
3149+.tweet .tweet_text {
3150+ padding: 10px;
3151+ background-color: #fff;
3152+ -moz-border-radius: 4px 4px 4px 4px;
3153+ -webkit-border-radius: 4px 4px 4px 4px;
3154+ border-radius: 4px 4px 4px 4px;
3155+ border: 1px solid #dd4814;
3156+ font-size: 16px;
3157+ display: block;
3158+ clear: both;
3159+}
3160+.tweet.tweet-small .tweet_text {
3161+ font-size: inherit;
3162+}
3163+.tweet .tweet_text a {
3164+ color: #333;
3165+}
3166+.tweet .tweet_time,
3167+.tweet .tweet_user_and_time {
3168+ padding: 15px 0 10px 0;
3169+ position: relative;
3170+ top: -2px;
3171+ background: url("../img/tweet-arrow.png") no-repeat;
3172+ display: block;
3173+}
3174+.tweet .tweet_odd .tweet_time,
3175+.tweet .tweet_odd .tweet_user_and_time {
3176+ background-position: right 0;
3177+ float: right;
3178+}
3179+.tweet .tweet_even .tweet_time,
3180+.tweet .tweet_even .tweet_user_and_time {
3181+ background-position: left 0;
3182+ float: left;
3183+}
3184+
3185+/* Search */
3186+
3187+#content .list-search li {
3188+ list-style-type:none;
3189+ border:0px;
3190+ margin-bottom: 15px;
3191+ padding-top: 15px;
3192+}
3193+
3194+/* Blog */
3195+
3196+.blog-article #nav-single {
3197+ margin-top: 30px;
3198+ margin-bottom: 30px;
3199+}
3200+.blog-article #nav-single .nav-next {
3201+ float: right;
3202+}
3203+.blog-article article header .entry-meta {
3204+ margin-bottom: 20px;
3205+}
3206+.blog-article article .entry-meta {
3207+ color: #999;
3208+}
3209+.blog-article #respond form input[type="submit"] {
3210+ float: left;
3211+ cursor: pointer;
3212+ margin-bottom: 20px;
3213+ padding: 8px 12px;
3214+ display: block;
3215+ background-color: #dd4814;
3216+ color: #fff;
3217+ -moz-border-radius: 20px;
3218+ -webkit-border-radius: 20px;
3219+ border-radius: 20px;
3220+ font-size: 16px;
3221+ line-height: 1.3;
3222+ border-top: 3px solid #e6633a;
3223+ border-left: 3px solid #e6633a;
3224+ border-right: 3px solid #e6633a;
3225+ border-bottom: 3px solid #c03d14;
3226+}
3227+.blog-article #respond form input[type="submit"]:active {
3228+ position: relative;
3229+ top: 1px;
3230+}
3231+
3232+.alignnone{
3233+ float:left;
3234+ margin:10px 20px 10px 0;
3235+}
3236+.alignleft{
3237+ float:left;
3238+ margin:10px 20px 10px 0;
3239+}
3240+.alignright{
3241+ float:right;
3242+ margin:10px 0 10px 20px;
3243+}
3244+
3245+.aligncenter{
3246+ float:left;
3247+ margin:10px 20px 10px 0;
3248+}
3249+.entry-content h2, .entry-content h3{
3250+ margin-top:20px;
3251+}
3252+.entry-content ul li{
3253+ list-style-type: circle;
3254+ margin-left:16px;
3255+}
3256+
3257+.entry-content hr{
3258+ border:none;
3259+ border-top: 1px dotted #AEA79F;
3260+}
3261
3262=== added file 'doc/qt/cpp/css/qtquick.css'
3263--- doc/qt/cpp/css/qtquick.css 1970-01-01 00:00:00 +0000
3264+++ doc/qt/cpp/css/qtquick.css 2014-08-19 17:36:21 +0000
3265@@ -0,0 +1,772 @@
3266+@media screen
3267+{
3268+
3269+/* basic elements */
3270+ html
3271+ {
3272+ color: #000000;
3273+ background: #FFFFFF;
3274+ }
3275+ table
3276+ {
3277+ border-collapse: collapse;
3278+ border-spacing: 0;
3279+ }
3280+ fieldset, img
3281+ {
3282+ border: 0;
3283+ max-width:100%;
3284+ }
3285+ address, caption, cite, code, dfn, em, strong, th, var, optgroup
3286+ {
3287+ font-style: inherit;
3288+ font-weight: inherit;
3289+ }
3290+ del, ins
3291+ {
3292+ text-decoration: none;
3293+ }
3294+ ol li
3295+ {
3296+ list-style: decimal;
3297+ }
3298+ ul li
3299+ {
3300+ list-style: none;
3301+ }
3302+ caption, th
3303+ {
3304+ text-align: left;
3305+ }
3306+ h1.title
3307+ {
3308+ font-weight: bold;
3309+ font-size: 150%;
3310+ }
3311+ h0
3312+ {
3313+ font-weight: bold;
3314+ font-size: 130%;
3315+ }
3316+ h1, h2, h3, h4, h5, h6
3317+ {
3318+ font-size: 100%;
3319+ }
3320+ q:before, q:after
3321+ {
3322+ content: '';
3323+ }
3324+ abbr, acronym
3325+ {
3326+ border: 0;
3327+ font-variant: normal;
3328+ }
3329+ sup, sub
3330+ {
3331+ vertical-align: baseline;
3332+ }
3333+ tt, .qmlreadonly span, .qmldefault span
3334+ {
3335+ word-spacing:0.5em;
3336+ }
3337+ legend
3338+ {
3339+ color: #000000;
3340+ }
3341+ strong
3342+ {
3343+ font-weight: bold;
3344+ }
3345+ em
3346+ {
3347+ font-style: italic;
3348+ }
3349+
3350+ body
3351+ {
3352+ margin: 0 1.5em 0 1.5em;
3353+ font-family: ubuntu;
3354+ line-height: normal
3355+ }
3356+ a
3357+ {
3358+ color: #00732F;
3359+ text-decoration: none;
3360+ }
3361+ hr
3362+ {
3363+ background-color: #E6E6E6;
3364+ border: 1px solid #E6E6E6;
3365+ height: 1px;
3366+ width: 100%;
3367+ text-align: left;
3368+ margin: 1.5em 0 1.5em 0;
3369+ }
3370+
3371+ pre
3372+ {
3373+ border: 1px solid #DDDDDD;
3374+ -moz-border-radius: 0.7em 0.7em 0.7em 0.7em;
3375+ -webkit-border-radius: 0.7em 0.7em 0.7em 0.7em;
3376+ border-radius: 0.7em 0.7em 0.7em 0.7em;
3377+ padding: 1em 1em 1em 1em;
3378+ overflow-x: auto;
3379+ }
3380+ table, pre
3381+ {
3382+ -moz-border-radius: 0.7em 0.7em 0.7em 0.7em;
3383+ -webkit-border-radius: 0.7em 0.7em 0.7em 0.7em;
3384+ border-radius: 0.7em 0.7em 0.7em 0.7em;
3385+ background-color: #F6F6F6;
3386+ border: 1px solid #E6E6E6;
3387+ border-collapse: separate;
3388+ margin-bottom: 2.5em;
3389+ }
3390+ pre {
3391+ font-size: 90%;
3392+ display: block;
3393+ overflow:hidden;
3394+ }
3395+ thead
3396+ {
3397+ margin-top: 0.5em;
3398+ font-weight: bold
3399+ }
3400+ th
3401+ {
3402+ padding: 0.5em 1.5em 0.5em 1em;
3403+ background-color: #E1E1E1;
3404+ border-left: 1px solid #E6E6E6;
3405+ }
3406+ td
3407+ {
3408+ padding: 0.25em 1.5em 0.25em 1em;
3409+ }
3410+
3411+ td.rightAlign
3412+ {
3413+ padding: 0.25em 0.5em 0.25em 1em;
3414+ }
3415+ table tr.odd
3416+ {
3417+ border-left: 1px solid #E6E6E6;
3418+ background-color: #F6F6F6;
3419+ color: black;
3420+ }
3421+ table tr.even
3422+ {
3423+ border-left: 1px solid #E6E6E6;
3424+ background-color: #ffffff;
3425+ color: #202020;
3426+ }
3427+
3428+ div.float-left
3429+ {
3430+ float: left; margin-right: 2em
3431+ }
3432+ div.float-right
3433+ {
3434+ float: right; margin-left: 2em
3435+ }
3436+
3437+ span.comment
3438+ {
3439+ color: #008B00;
3440+ }
3441+ span.string, span.char
3442+ {
3443+ color: #000084;
3444+ }
3445+ span.number
3446+ {
3447+ color: #a46200;
3448+ }
3449+ span.operator
3450+ {
3451+ color: #202020;
3452+ }
3453+ span.keyword
3454+ {
3455+ color: #840000;
3456+ }
3457+ span.name
3458+ {
3459+ color: black
3460+ }
3461+ span.type
3462+ {
3463+ font-weight: bold
3464+ }
3465+ span.type a:visited
3466+ {
3467+ color: #0F5300;
3468+ }
3469+ span.preprocessor
3470+ {
3471+ color: #404040
3472+ }
3473+/* end basic elements */
3474+
3475+/* font style elements */
3476+ .heading
3477+ {
3478+ font-weight: bold;
3479+ font-size: 125%;
3480+ }
3481+ .subtitle
3482+ {
3483+ font-size: 110%
3484+ }
3485+ .small-subtitle
3486+ {
3487+ font-size: 100%
3488+ }
3489+ .red
3490+ {
3491+ color:red;
3492+ }
3493+/* end font style elements */
3494+
3495+/* global settings*/
3496+ .header, .footer
3497+ {
3498+ display: block;
3499+ clear: both;
3500+ overflow: hidden;
3501+ }
3502+/* end global settings*/
3503+
3504+/* header elements */
3505+ .header .qtref
3506+ {
3507+ color: #00732F;
3508+ font-weight: bold;
3509+ font-size: 130%;
3510+ }
3511+
3512+ .header .content
3513+ {
3514+ margin-left: 5px;
3515+ margin-top: 5px;
3516+ margin-bottom: 0.5em;
3517+ }
3518+
3519+ .header .breadcrumb
3520+ {
3521+ font-size: 90%;
3522+ padding: 0.5em 0 0.5em 1em;
3523+ margin: 0;
3524+ background-color: #fafafa;
3525+ height: 1.35em;
3526+ border-bottom: 1px solid #d1d1d1;
3527+ }
3528+
3529+ .header .breadcrumb ul
3530+ {
3531+ margin: 0;
3532+ padding: 0;
3533+ }
3534+
3535+ .header .content
3536+ {
3537+ word-wrap: break-word;
3538+ }
3539+
3540+ .header .breadcrumb ul li
3541+ {
3542+ float: left;
3543+ background: url(../images/breadcrumb.png) no-repeat 0 3px;
3544+ padding-left: 1.5em;
3545+ margin-left: 1.5em;
3546+ }
3547+
3548+ .header .breadcrumb ul li.last
3549+ {
3550+ font-weight: normal;
3551+ }
3552+
3553+ .header .breadcrumb ul li a
3554+ {
3555+ color: #00732F;
3556+ }
3557+
3558+ .header .breadcrumb ul li.first
3559+ {
3560+ background-image: none;
3561+ padding-left: 0;
3562+ margin-left: 0;
3563+ }
3564+
3565+ .header .content ol li {
3566+ background: none;
3567+ margin-bottom: 1.0em;
3568+ margin-left: 1.2em;
3569+ padding-left: 0
3570+ }
3571+
3572+ .header .content li
3573+ {
3574+ background: url(../images/bullet_sq.png) no-repeat 0 5px;
3575+ margin-bottom: 1em;
3576+ padding-left: 1.2em;
3577+ }
3578+
3579+/* end header elements */
3580+
3581+/* content elements */
3582+ .content h1
3583+ {
3584+ font-weight: bold;
3585+ font-size: 130%
3586+ }
3587+
3588+ .content h2
3589+ {
3590+ font-weight: bold;
3591+ font-size: 120%;
3592+ width: 100%;
3593+ }
3594+ .content h3
3595+ {
3596+ font-weight: bold;
3597+ font-size: 110%;
3598+ width: 100%;
3599+ }
3600+ .content table p
3601+ {
3602+ margin: 0
3603+ }
3604+ .content ul
3605+ {
3606+ padding-left: 2.5em;
3607+ }
3608+ .content li
3609+ {
3610+ padding-top: 0.25em;
3611+ padding-bottom: 0.25em;
3612+ }
3613+ .content ul img {
3614+ vertical-align: middle;
3615+ }
3616+
3617+ .content a:visited
3618+ {
3619+ color: #4c0033;
3620+ text-decoration: none;
3621+ }
3622+
3623+ .content a:visited:hover
3624+ {
3625+ color: #4c0033;
3626+ text-decoration: underline;
3627+ }
3628+
3629+ a:hover
3630+ {
3631+ color: #4c0033;
3632+ text-decoration: underline;
3633+ }
3634+ descr p a
3635+ {
3636+ text-decoration: underline;
3637+ }
3638+
3639+ .descr p a:visited
3640+ {
3641+ text-decoration: underline;
3642+ }
3643+
3644+ .alphaChar{
3645+ width:95%;
3646+ background-color:#F6F6F6;
3647+ border:1px solid #E6E6E6;
3648+ -moz-border-radius: 7px 7px 7px 7px;
3649+ border-radius: 7px 7px 7px 7px;
3650+ -webkit-border-radius: 7px 7px 7px 7px;
3651+ font-size:12pt;
3652+ padding-left:10px;
3653+ margin-top:10px;
3654+ margin-bottom:10px;
3655+ }
3656+ .flowList{
3657+ /*vertical-align:top;*/
3658+ /*margin:20px auto;*/
3659+
3660+ column-count:3;
3661+ -webkit-column-count:3;
3662+ -moz-column-count:3;
3663+/*
3664+ column-width:100%;
3665+ -webkit-column-width:200px;
3666+ -col-column-width:200px;
3667+*/
3668+ column-gap:41px;
3669+ -webkit-column-gap:41px;
3670+ -moz-column-gap:41px;
3671+
3672+ column-rule: 1px dashed #ccc;
3673+ -webkit-column-rule: 1px dashed #ccc;
3674+ -moz-column-rule: 1px dashed #ccc;
3675+ }
3676+
3677+ .flowList dl{
3678+ }
3679+ .flowList dd{
3680+ /*display:inline-block;*/
3681+ margin-left:10px;
3682+ min-width:250px;
3683+ line-height: 1.5;
3684+ min-width:100%;
3685+ min-height:15px;
3686+ }
3687+
3688+ .flowList dd a{
3689+ }
3690+
3691+ .mainContent
3692+ {
3693+ padding-left:5px;
3694+ }
3695+
3696+ .content .flowList p{
3697+ padding:0px;
3698+ }
3699+
3700+ .content .alignedsummary
3701+ {
3702+ margin: 15px;
3703+ }
3704+
3705+
3706+ .qmltype
3707+ {
3708+ text-align: center;
3709+ font-size: 120%;
3710+ }
3711+ .qmlreadonly
3712+ {
3713+ padding-left: 5px;
3714+ float: right;
3715+ color: #254117;
3716+ }
3717+
3718+ .qmldefault
3719+ {
3720+ padding-left: 5px;
3721+ float: right;
3722+ color: red;
3723+ }
3724+
3725+ .qmldoc
3726+ {
3727+ }
3728+
3729+ .generic .alphaChar{
3730+ margin-top:5px;
3731+ }
3732+
3733+ .generic .odd .alphaChar{
3734+ background-color: #F6F6F6;
3735+ }
3736+
3737+ .generic .even .alphaChar{
3738+ background-color: #FFFFFF;
3739+ }
3740+
3741+ .memItemRight{
3742+ padding: 0.25em 1.5em 0.25em 0;
3743+ }
3744+ .highlightedCode
3745+ {
3746+ margin: 1.0em;
3747+ }
3748+ .annotated td {
3749+ padding: 0.25em 0.5em 0.25em 0.5em;
3750+ }
3751+
3752+ .toc
3753+ {
3754+ font-size: 80%
3755+ }
3756+
3757+ .header .content .toc ul
3758+ {
3759+ padding-left: 0px;
3760+ }
3761+
3762+ .content .toc h3 {
3763+ border-bottom: 0px;
3764+ margin-top: 0px;
3765+ }
3766+
3767+ .content .toc h3 a:hover {
3768+ color: #00732F;
3769+ text-decoration: none;
3770+ }
3771+
3772+ .content .toc .level2
3773+ {
3774+ margin-left: 1.5em;
3775+ }
3776+
3777+ .content .toc .level3
3778+ {
3779+ margin-left: 3.0em;
3780+ }
3781+
3782+ .content ul li
3783+ {
3784+ background: url(../images/bullet_sq.png) no-repeat 0 0.7em;
3785+ padding-left: 1em
3786+ }
3787+
3788+ .content .toc li
3789+ {
3790+ background: url(../images/bullet_dn.png) no-repeat 0 5px;
3791+ padding-left: 1em
3792+ }
3793+
3794+ .relpage
3795+ {
3796+ -moz-border-radius: 7px 7px 7px 7px;
3797+ -webkit-border-radius: 7px 7px 7px 7px;
3798+ border-radius: 7px 7px 7px 7px;
3799+ border: 1px solid #DDDDDD;
3800+ padding: 25px 25px;
3801+ clear: both;
3802+ }
3803+ .relpage ul
3804+ {
3805+ float: none;
3806+ padding: 1.5em;
3807+ }
3808+
3809+ h3.fn, span.fn
3810+ {
3811+ -moz-border-radius:7px 7px 7px 7px;
3812+ -webkit-border-radius:7px 7px 7px 7px;
3813+ border-radius:7px 7px 7px 7px;
3814+ background-color: #F6F6F6;
3815+ border-width: 1px;
3816+ border-style: solid;
3817+ border-color: #E6E6E6;
3818+ font-weight: bold;
3819+ word-spacing:3px;
3820+ padding:3px 5px;
3821+ }
3822+
3823+ .functionIndex {
3824+ font-size:12pt;
3825+ word-spacing:10px;
3826+ margin-bottom:10px;
3827+ background-color: #F6F6F6;
3828+ border-width: 1px;
3829+ border-style: solid;
3830+ border-color: #E6E6E6;
3831+ -moz-border-radius: 7px 7px 7px 7px;
3832+ -webkit-border-radius: 7px 7px 7px 7px;
3833+ border-radius: 7px 7px 7px 7px;
3834+ width:100%;
3835+ }
3836+
3837+ .centerAlign
3838+ {
3839+ text-align:center;
3840+ }
3841+
3842+ .rightAlign
3843+ {
3844+ text-align:right;
3845+ }
3846+
3847+ .leftAlign
3848+ {
3849+ text-align:left;
3850+ }
3851+
3852+ .topAlign{
3853+ vertical-align:top
3854+ }
3855+
3856+ .functionIndex a{
3857+ display:inline-block;
3858+ }
3859+
3860+/* end content elements */
3861+/* footer elements */
3862+
3863+ .footer
3864+ {
3865+ color: #393735;
3866+ font-size: 0.75em;
3867+ text-align: center;
3868+ padding-top: 1.5em;
3869+ padding-bottom: 1em;
3870+ background-color: #E6E7E8;
3871+ margin: 0;
3872+ }
3873+ .footer p
3874+ {
3875+ margin: 0.25em
3876+ }
3877+ .small
3878+ {
3879+ font-size: 0.5em;
3880+ }
3881+/* end footer elements */
3882+
3883+ .item {
3884+ float: left;
3885+ position: relative;
3886+ width: 100%;
3887+ overflow: hidden;
3888+ }
3889+
3890+
3891+ .item .primary {
3892+ margin-right: 220px;
3893+ position: relative;
3894+ }
3895+
3896+ .item hr {
3897+ margin-left: -220px;
3898+ }
3899+
3900+ .item .secondary {
3901+ float: right;
3902+ width: 200px;
3903+ position: relative;
3904+ }
3905+
3906+ .item .cols {
3907+ clear: both;
3908+ display: block;
3909+ }
3910+
3911+ .item .cols .col {
3912+ float: left;
3913+ margin-left: 1.5%;
3914+ }
3915+
3916+ .item .cols .col.first {
3917+ margin-left: 0;
3918+ }
3919+
3920+ .item .cols.two .col {
3921+ width: 45%;
3922+ }
3923+
3924+ .item .box {
3925+ margin: 0 0 10px 0;
3926+ }
3927+
3928+ .item .box h3 {
3929+ margin: 0 0 10px 0;
3930+ }
3931+
3932+ .cols.unclear {
3933+ clear:none;
3934+ }
3935+}
3936+
3937+/* end of screen media */
3938+
3939+/* start of print media */
3940+
3941+@media print
3942+{
3943+ input, textarea, .header, .footer, .toolbar, .feedback, .wrapper .hd, .wrapper .bd .sidebar, .wrapper .ft, #feedbackBox, #blurpage, .toc, .breadcrumb, .toolbar, .floatingResult
3944+ {
3945+ display: none;
3946+ background: none;
3947+ }
3948+ .content
3949+ {
3950+ background: none;
3951+ display: block;
3952+ width: 100%; margin: 0; float: none;
3953+ }
3954+}
3955+/* end of print media */
3956+
3957+
3958+/* modify the TOC layouts */
3959+div.toc ul {
3960+ padding-left: 20px;
3961+}
3962+div.toc li {
3963+ padding-left: 4px;
3964+}
3965+/* Remove the border around images*/
3966+a img
3967+{
3968+ border:none;
3969+}
3970+
3971+/*Add styling to the front pages*/
3972+
3973+.threecolumn_area
3974+{
3975+ padding-top: 20px;
3976+ padding-bottom: 20px;
3977+}
3978+.threecolumn_piece
3979+{
3980+ display: inline-block;
3981+ margin-left: 78px;
3982+ margin-top: 8px;
3983+ padding: 0;
3984+ vertical-align: top;
3985+ width: 25.5%;
3986+}
3987+div.threecolumn_piece ul {
3988+ list-style-type: none;
3989+ padding-left: 0px;
3990+ margin-top: 2px;
3991+}
3992+div.threecolumn_piece p {
3993+ margin-bottom: 7px;
3994+ color: #5C626E;
3995+ text-decoration: none;
3996+ font-weight: bold;
3997+}
3998+div.threecolumn_piece li {
3999+ padding-left: 0px;
4000+ margin-bottom: 5px;
4001+}
4002+div.threecolumn_piece a {
4003+ font-weight: normal;
4004+}
4005+/* Add style to guide page*/
4006+.fourcolumn_area
4007+{
4008+ padding-top: 20px;
4009+ padding-bottom: 20px;
4010+}
4011+.fourcolumn_piece
4012+{
4013+ display: inline-block;
4014+ margin-left: 35px;
4015+ margin-top: 8px;
4016+ padding: 0;
4017+ vertical-align: top;
4018+ width: 21.3%;
4019+}
4020+div.fourcolumn_piece ul {
4021+ list-style-type: none;
4022+ padding-left: 0px;
4023+ margin-top: 2px;
4024+}
4025+div.fourcolumn_piece p {
4026+ margin-bottom: 7px;
4027+ color: #40444D;
4028+ text-decoration: none;
4029+ font-weight: bold;
4030+}
4031+div.fourcolumn_piece li {
4032+ padding-left: 0px;
4033+ margin-bottom: 5px;
4034+}
4035+div.fourcolumn_piece a {
4036+ font-weight: normal;
4037+}
4038
4039=== added file 'doc/qt/cpp/css/reset.css'
4040--- doc/qt/cpp/css/reset.css 1970-01-01 00:00:00 +0000
4041+++ doc/qt/cpp/css/reset.css 2014-08-19 17:36:21 +0000
4042@@ -0,0 +1,8 @@
4043+/*
4044+Copyright (c) 2010, Yahoo! Inc. All rights reserved.
4045+Code licensed under the BSD License:
4046+http://developer.yahoo.com/yui/license.html
4047+version: 3.3.0
4048+build: 3167
4049+*/
4050+html{color:#000;background:#FFF;}body,div,dl,dt,dd,ul,ol,li,h1,h2,h3,h4,h5,h6,pre,code,form,fieldset,legend,input,textarea,p,blockquote,th,td{margin:0;padding:0;}table{border-collapse:collapse;border-spacing:0;}fieldset,img{border:0;}address,caption,cite,code,dfn,em,strong,th,var{font-style:normal;font-weight:normal;}li{list-style:none;}caption,th{text-align:left;}h1,h2,h3,h4,h5,h6{font-size:100%;font-weight:normal;}q:before,q:after{content:'';}abbr,acronym{border:0;font-variant:normal;}sup{vertical-align:text-top;}sub{vertical-align:text-bottom;}input,textarea,select{font-family:inherit;font-size:inherit;font-weight:inherit;}input,textarea,select{*font-size:100%;}legend{color:#000;}
4051\ No newline at end of file
4052
4053=== added file 'doc/qt/cpp/css/scratch.css'
4054--- doc/qt/cpp/css/scratch.css 1970-01-01 00:00:00 +0000
4055+++ doc/qt/cpp/css/scratch.css 2014-08-19 17:36:21 +0000
4056@@ -0,0 +1,61 @@
4057+body {
4058+ margin: 0;
4059+}
4060+
4061+
4062+div.toc ul {
4063+ padding: 0;
4064+}
4065+
4066+div.toc li {
4067+ margin-bottom: 3px;
4068+}
4069+
4070+h1.title {
4071+ font-size: 36px;
4072+ line-height: 1.1;
4073+ font-weight: normal;
4074+}
4075+h0, h2 {
4076+ font-size: 24px;
4077+ line-height: 1.2;
4078+ margin: 14px 0;
4079+ font-weight: normal;
4080+ display: block;
4081+}
4082+a:hover {
4083+ color: #dd4814;
4084+ text-decoration: underline;
4085+ outline: 0;
4086+}
4087+table, pre {
4088+ border-radius: 0;
4089+}
4090+
4091+.annotated td {
4092+ padding: 0.8em 1em 0.3em;
4093+}
4094+.wrapper {
4095+ width: 940px;
4096+ margin: 0 auto;
4097+}
4098+.main-content {
4099+ width: 668px;
4100+ position: relative;
4101+ left: 270px;
4102+}
4103+.title {
4104+ margin-left: -270px;
4105+ margin-top: 30px;
4106+ margin-bottom: 50px;
4107+}
4108+.toc {
4109+ margin-left: -270px;
4110+ font-size: 100%;
4111+ margin-bottom: 40px;
4112+ padding: 0;
4113+ z-index: 2;
4114+ position: absolute;
4115+ top: 100px;
4116+ width: 250px;
4117+}
4118
4119=== added directory 'doc/qt/cpp/examples'
4120=== added file 'doc/qt/cpp/examples/CMakeLists.txt'
4121--- doc/qt/cpp/examples/CMakeLists.txt 1970-01-01 00:00:00 +0000
4122+++ doc/qt/cpp/examples/CMakeLists.txt 2014-08-19 17:36:21 +0000
4123@@ -0,0 +1,6 @@
4124+include_directories(${CMAKE_SOURCE_DIR}/src/qt/include)
4125+add_executable(
4126+ networking_status
4127+ example_networking_status.cpp
4128+)
4129+target_link_libraries(networking_status ${CONNECTIVITY_QT_LIB_TARGET})
4130
4131=== added file 'doc/qt/cpp/examples/example_networking_status.cpp'
4132--- doc/qt/cpp/examples/example_networking_status.cpp 1970-01-01 00:00:00 +0000
4133+++ doc/qt/cpp/examples/example_networking_status.cpp 2014-08-19 17:36:21 +0000
4134@@ -0,0 +1,86 @@
4135+/*
4136+ * Copyright © 2014 Canonical Ltd.
4137+ *
4138+ * This program is free software: you can redistribute it and/or modify it
4139+ * under the terms of the GNU Lesser General Public License version 3,
4140+ * as published by the Free Software Foundation.
4141+ *
4142+ * This program is distributed in the hope that it will be useful,
4143+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
4144+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
4145+ * GNU Lesser General Public License for more details.
4146+ *
4147+ * You should have received a copy of the GNU Lesser General Public License
4148+ * along with this program. If not, see <http://www.gnu.org/licenses/>.
4149+ *
4150+ * Authors:
4151+ * Antti Kaijanmäki <antti.kaijanmaki@canonical.com>
4152+ */
4153+
4154+#include <QCoreApplication>
4155+#include <QScopedPointer>
4156+#include <QDebug>
4157+
4158+//! [include]
4159+#include <ubuntu/connectivity/networking-status.h>
4160+using ubuntu::connectivity::NetworkingStatus;
4161+//! [include]
4162+
4163+int
4164+main(int argc, char *argv[])
4165+{
4166+ QCoreApplication app(argc, argv);
4167+
4168+ //! [create networkingstatus]
4169+ QScopedPointer<NetworkingStatus> ns(new NetworkingStatus());
4170+ //! [create networkingstatus]
4171+
4172+ //! [status]
4173+ // normal getter
4174+ if (ns->status() == NetworkingStatus::Online)
4175+ qDebug() << "We are online.";
4176+
4177+ // Subscribe to system networking changes
4178+ QObject::connect(ns.data(),
4179+ &NetworkingStatus::statusChanged,
4180+ [](NetworkingStatus::Status value)
4181+ {
4182+ switch(value) {
4183+ case NetworkingStatus::Offline:
4184+ qDebug() << "System networking status changed to: Offline";
4185+ break;
4186+ case NetworkingStatus::Connecting:
4187+ qDebug() << "System networking status changed to: Connecting";
4188+ break;
4189+ case NetworkingStatus::Online:
4190+ qDebug() << "System networking status changed to: Online";
4191+ break;
4192+ }
4193+ });
4194+ //! [status]
4195+
4196+ //! [limitations]
4197+ // normal getter
4198+ if (ns->limitations().isEmpty())
4199+ qDebug() << "No limitations";
4200+
4201+ // Subscribe to limitation changes
4202+ QObject::connect(ns.data(),
4203+ &NetworkingStatus::limitationsChanged,
4204+ [&ns](){
4205+ if (ns->limitations().isEmpty()) {
4206+ qDebug() << "No limitations.";
4207+ return;
4208+ }
4209+
4210+ qDebug() << "Limitations:";
4211+ if (ns->limitations().contains(NetworkingStatus::Limitations::Bandwith)) {
4212+ qDebug() << " - Bandwith";
4213+ }
4214+ });
4215+ //! [limitations]
4216+
4217+ app.exec();
4218+
4219+ return 0;
4220+}
4221
4222=== added directory 'doc/qt/cpp/pages'
4223=== added file 'doc/qt/cpp/pages/mainpage.dox'
4224--- doc/qt/cpp/pages/mainpage.dox 1970-01-01 00:00:00 +0000
4225+++ doc/qt/cpp/pages/mainpage.dox 2014-08-19 17:36:21 +0000
4226@@ -0,0 +1,18 @@
4227+/*!
4228+\mainpage Ubuntu Connectivity API
4229+
4230+\tableofcontents
4231+
4232+\section sec_introduction Introduction
4233+
4234+Ubuntu Connectivity API offers a way to access the connectivity related information of the system.
4235+
4236+\section sec_general General Topics
4237+
4238+ - \ref using-cpp "Using this C++ API"
4239+ - \ref networking-status "Getting the networking status."
4240+
4241+\section sec_bug_reports Reporting Bugs
4242+If you find any problems with the or this documentation,
4243+please file a bug in Connectivity API [Launchpad page](https://bugs.launchpad.net/connectivity-api).
4244+*/
4245
4246=== added file 'doc/qt/cpp/pages/networking-status.dox'
4247--- doc/qt/cpp/pages/networking-status.dox 1970-01-01 00:00:00 +0000
4248+++ doc/qt/cpp/pages/networking-status.dox 2014-08-19 17:36:21 +0000
4249@@ -0,0 +1,35 @@
4250+/*!
4251+\page networking-status Networking Status
4252+
4253+Applications needing to access the overall system networking status must access the
4254+ubuntu::connectivity::NetworkingStatus class. The class has properties
4255+for the networking status and connection limitations of the system networking.
4256+
4257+Accessing the networking status from confined applications requires
4258+the <i>connectivity</i> policy group.
4259+
4260+\section Setup
4261+
4262+Manager is accessed by including the appropriate header:
4263+\snippet example_networking_status.cpp include
4264+
4265+and then creating an instance of the NetworkingStatus:
4266+\snippet example_networking_status.cpp create networkingstatus
4267+
4268+\section sec_networking_status Networking Status
4269+
4270+\subsection sec_networking_status_status Status
4271+
4272+The status of the system networking can be accessed through the ubuntu::connectivity::NetworkingStatus::status property:
4273+\snippet example_networking_status.cpp status
4274+
4275+\subsection sec_networking_status_limitations Limitations
4276+
4277+The limitations can be accessed through the ubuntu::connectivity::NetworkingStatus::limitations property:
4278+\snippet example_networking_status.cpp limitations
4279+
4280+---
4281+The complete example (found in <i>examples/example_networking_status.cpp</i>):
4282+\include example_networking_status.cpp
4283+
4284+*/
4285
4286=== added file 'doc/qt/cpp/pages/using.dox'
4287--- doc/qt/cpp/pages/using.dox 1970-01-01 00:00:00 +0000
4288+++ doc/qt/cpp/pages/using.dox 2014-08-19 17:36:21 +0000
4289@@ -0,0 +1,26 @@
4290+/*!
4291+\page using-cpp Using the C++ API
4292+
4293+Install the development headers:
4294+
4295+\code{.txt}
4296+sudo apt-get install libconnectivity-qt1-dev
4297+\endcode
4298+
4299+Enable c++11 and use pkg-config to get the necessary compilation flags:
4300+
4301+\code{.txt}
4302+$ g++ myapp.cpp -std=c++11 `pkg-config --cflags --libs connectivity-qt1` -o myapp
4303+\endcode
4304+
4305+The headers can then be included as:
4306+
4307+\code{.cpp}
4308+// includes the ubuntu::connectivity::NetworkingStatus class
4309+#include <ubuntu/connectivity/networking-status.h>
4310+\endcode
4311+
4312+<b>note:</b><br />
4313+Accessing the networking status from confined applications requires the <i>connectivity</i> policy group.
4314+
4315+*/
4316
4317=== added file 'doc/qt/cpp/ubuntu-appdev-site-footer.html'
4318--- doc/qt/cpp/ubuntu-appdev-site-footer.html 1970-01-01 00:00:00 +0000
4319+++ doc/qt/cpp/ubuntu-appdev-site-footer.html 2014-08-19 17:36:21 +0000
4320@@ -0,0 +1,53 @@
4321+</div></div>
4322+<div class="shadow"></div>
4323+<footer>
4324+ <div>
4325+ <nav role="navigation" class="clearfix">
4326+ <ul>
4327+ <li><a href="/get-started">Get started</a></li>
4328+ <li class="page_item page-item-16"><a href="http://developer.ubuntu.com/get-started/quickly-workflow/">Quickly workflow</a></li>
4329+ <li class="page_item page-item-18"><a href="http://developer.ubuntu.com/get-started/qt-creator/">Qt Creator</a></li>
4330+ <li class="page_item page-item-20"><a href="http://developer.ubuntu.com/get-started/eclipse/">Eclipse</a></li>
4331+ <li class="page_item page-item-22"><a href="http://developer.ubuntu.com/get-started/monodevelop/">MonoDevelop</a></li>
4332+ </ul>
4333+ <ul>
4334+ <li><a href="/resources">Resources</a></li>
4335+ <li><a href="/resources/tools/quickly">Quickly</a></li>
4336+ <li><a href="/resources/platform/api">API</a></li>
4337+ <li><a href="/resources/platform/documentation/platform-diagram">Platform overview</a></li>
4338+ </ul>
4339+ <ul>
4340+ <li><a href="/publish">Publish</a></li>
4341+ <li class="page_item page-item-24"><a href="http://developer.ubuntu.com/publish/commercial-software-faqs/">Commercial software FAQs</a></li>
4342+ <li class="page_item page-item-34"><a href="http://developer.ubuntu.com/publish/application-states/">Application states</a></li>
4343+ <li class="page_item page-item-577"><a href="http://developer.ubuntu.com/publish/my-apps-packages/">Uploading your app</a></li>
4344+ <li class="page_item page-item-404"><a href="http://developer.ubuntu.com/publish/ubuntu-software-centre/">Ubuntu Software Centre</a></li>
4345+ <li class="page_item page-item-427"><a href="http://developer.ubuntu.com/publish/licence-key-infrastructure/">Licence key infrastructure</a></li>
4346+ <li class="page_item page-item-1230"><a href="http://developer.ubuntu.com/publish/updating-your-app/">Updating your app</a></li>
4347+ </ul>
4348+ <ul>
4349+ <li><a href="/community">Community</a></li>
4350+ <li class="page_item page-item-28"><a href="http://developer.ubuntu.com/community/app-developer-blog/">App Developer Blog</a></li>
4351+ <li class="page_item page-item-30"><a href="http://developer.ubuntu.com/community/submit-a-tutorial/">Submit a tutorial</a></li>
4352+ <li class="page_item page-item-32"><a href="http://developer.ubuntu.com/community/app-review-board-charter/">App Review Board charter</a></li>
4353+ <li class="page_item page-item-2987"><a href="http://developer.ubuntu.com/community/on-air/">On air</a>
4354+ <ul class='children'>
4355+ <li class="page_item page-item-3066"><a href="http://developer.ubuntu.com/community/on-air/recordings/">Recordings</a></li>
4356+ </ul>
4357+ </li>
4358+ </ul>
4359+ <ul class="last">
4360+ <li><a href="https://myapps.developer.ubuntu.com/dev">My Apps</a></li>
4361+ <li><a href="https://myapps.developer.ubuntu.com/openid/login/?next=/dev">Sign in or register</a></li>
4362+ <li><a href="https://myapps.developer.ubuntu.com/dev/account">My account</a></li>
4363+ </ul>
4364+ </nav>
4365+ <p>&copy; 2013 Canonical Ltd. Ubuntu and Canonical are registered trademarks of Canonical Ltd.
4366+ <a class="link-bug" href="https://bugs.launchpad.net/ubuntudeveloperportal/+filebug">
4367+ Report a bug on this site
4368+ </a>
4369+ </p>
4370+ </div>
4371+</footer>
4372+<script type="text/javascript" src="https://ajax.googleapis.com/ajax/libs/jquery/1.6.2/jquery.min.js"></script>
4373+<script type="text/javascript" src="http://developer.ubuntu.com/wp-content/themes/wordpress-theme-ubuntudeveloper/js/base.js"></script>\n"
4374
4375=== added file 'doc/qt/cpp/ubuntu-appdev-site-header.html'
4376--- doc/qt/cpp/ubuntu-appdev-site-header.html 1970-01-01 00:00:00 +0000
4377+++ doc/qt/cpp/ubuntu-appdev-site-header.html 2014-08-19 17:36:21 +0000
4378@@ -0,0 +1,35 @@
4379+<header>
4380+ <div class="header-login">
4381+ <ul>
4382+ <li><a href="https://myapps.developer.ubuntu.com/openid/login/?next\=/dev">Sign in or register</a></li>
4383+ </ul>
4384+ </div>
4385+ <div class="header-navigation">
4386+ <div>
4387+ <nav role="navigation">
4388+ <ul>
4389+ <li class="page_item page-item-5"><a href="http://developer.ubuntu.com/">Home</a></li>
4390+ <li class="page_item page-item-7"><a href="http://developer.ubuntu.com/get-started/">Get started</a></li>
4391+ <li class="page_item page-item-9"><a href="http://developer.ubuntu.com/resources/">Resources</a></li>
4392+ <li class="page_item page-item-11"><a href="http://developer.ubuntu.com/publish/">Publish</a></li>
4393+ <li class="page_item page-item-13"><a href="http://developer.ubuntu.com/community/">Community</a></li>
4394+ <li><a href="https://myapps.developer.ubuntu.com/dev">My Apps</a></li>
4395+ <li>
4396+ <form id="form-search" method="get" action="/">
4397+ <fieldset>
4398+ <input id="input-search" type="text" name="s" value="Search" />
4399+ </fieldset>
4400+ </form>
4401+ </li>
4402+ </ul>
4403+ </nav>
4404+ <a class="logo-ubuntu" href="/"><img src="http://developer.ubuntu.com/wp-content/themes/wordpress-theme-ubuntudeveloper/img/logo-ubuntu.png" width="119" height="27" alt="Ubuntu logo" /></a>
4405+ <h2><a href="/">App Developer</a></h2>
4406+ </div>
4407+ </div>
4408+
4409+</header>
4410+<div class="wrapper">
4411+ <div class="main-content">\n"
4412+
4413+
4414
4415=== added directory 'doc/qt/qml'
4416=== added file 'doc/qt/qml/CMakeLists.txt'
4417--- doc/qt/qml/CMakeLists.txt 1970-01-01 00:00:00 +0000
4418+++ doc/qt/qml/CMakeLists.txt 2014-08-19 17:36:21 +0000
4419@@ -0,0 +1,41 @@
4420+set(DOC_SOURCES
4421+ examples/example_networking_status.qml
4422+ qml-api/NetworkingStatus.qml
4423+ pages/mainpage.qdoc)
4424+
4425+# add a target to generate API documentation with qdoc
4426+FIND_PROGRAM(QDOC_EXECUTABLE qdoc)
4427+if(QDOC_EXECUTABLE)
4428+configure_file(${CMAKE_CURRENT_SOURCE_DIR}/connectivity-qml.qdocconf.in ${CMAKE_CURRENT_BINARY_DIR}/connectivity-qml.qdocconf @ONLY)
4429+add_custom_target(qmldoc
4430+${QDOC_EXECUTABLE} ${CMAKE_CURRENT_BINARY_DIR}/connectivity-qml.qdocconf
4431+WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}
4432+COMMENT "Generating QML API documentation with qdoc" VERBATIM
4433+SOURCES ${DOC_SOURCES}
4434+)
4435+
4436+# copy stylesheet files into build directory for shadow builds
4437+file(COPY "${CMAKE_CURRENT_SOURCE_DIR}/css"
4438+ DESTINATION ${CMAKE_CURRENT_BINARY_DIR}
4439+ )
4440+
4441+# copy the API files over ot the build directery as there is a
4442+# bug in qt5.2 qdoc for handling absolute paths
4443+file(COPY "${CMAKE_CURRENT_SOURCE_DIR}/qml-api"
4444+ DESTINATION ${CMAKE_CURRENT_BINARY_DIR}
4445+ )
4446+file(COPY "${CMAKE_CURRENT_SOURCE_DIR}/pages"
4447+ DESTINATION ${CMAKE_CURRENT_BINARY_DIR}
4448+ )
4449+file(COPY "${CMAKE_CURRENT_SOURCE_DIR}/examples"
4450+ DESTINATION ${CMAKE_CURRENT_BINARY_DIR}
4451+ )
4452+
4453+install(
4454+ DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}/html/
4455+ DESTINATION ${INSTALL_DOCDIR}/qml/html/
4456+)
4457+
4458+endif(QDOC_EXECUTABLE)
4459+
4460+
4461
4462=== added file 'doc/qt/qml/connectivity-qml.qdocconf.in'
4463--- doc/qt/qml/connectivity-qml.qdocconf.in 1970-01-01 00:00:00 +0000
4464+++ doc/qt/qml/connectivity-qml.qdocconf.in 2014-08-19 17:36:21 +0000
4465@@ -0,0 +1,55 @@
4466+project = Connectivity
4467+description = Ubuntu Connectivity QML API
4468+version = CONNECTIVITY_QT_VERSION_MAJOR@.@CONNECTIVITY_QT_VERSION_MINOR@
4469+
4470+outputencoding = UTF-8
4471+sourceencoding = UTF-8
4472+
4473+# Bug in Qt5.2 qdoc, does not support absolute paths
4474+# just have to hack this over and copy the files to BINARY_DIR
4475+#sourcedirs = @CMAKE_CURRENT_SOURCE_DIR@/pages @CMAKE_CURRENT_SOURCE_DIR@/qml-api
4476+#exampledirs = @CMAKE_SOURCE_DIR@/examples/
4477+#imagedirs = @CMAKE_CURRENT_SOURCE_DIR@/../images
4478+sourcedirs = pages qml-api
4479+exampledirs = examples/
4480+
4481+sources.fileextensions = "*.qdoc *.qml"
4482+headers.fileextensions = "*.h"
4483+examples.fileextensions = "*.js *.qml"
4484+examples.imageextensions = "*.png *.jpeg *.jpg"
4485+
4486+outputdir = @CMAKE_CURRENT_BINARY_DIR@/html
4487+outputformat = HTML
4488+
4489+outputprefixes = QML
4490+outputprefixes.QML = qml-
4491+
4492+HTML.templatedir = @CMAKE_CURRENT_SOURCE_DIR@/
4493+HTML.nobreadcrumbs = "true"
4494+
4495+HTML.stylesheets = \
4496+ css/reset.css \
4497+ css/qtquick.css \
4498+ css/base.css \
4499+ css/scratch.css
4500+
4501+HTML.headerstyles = \
4502+ "<link rel=\"stylesheet\" type=\"text/css\" href=\"style/reset.css\" />\n" \
4503+ "<link rel=\"stylesheet\" type=\"text/css\" href=\"style/qtquick.css\" />\n" \
4504+ "<link rel=\"stylesheet\" type=\"text/css\" href=\"style/base.css\" />\n" \
4505+ "<link rel=\"stylesheet\" type=\"text/css\" href=\"style/scratch.css\" />\n"
4506+
4507+HTML.postheader = \
4508+ " <div class=\"wrapper\">\n" \
4509+ " <div class=\"main-content\">\n"
4510+
4511+HTML.footer = \
4512+ "</div></div>\n" \
4513+ "<div class=\"shadow\"></div>\n" \
4514+ "<footer>\n" \
4515+ " <div>\n" \
4516+ " <nav role=\"navigation\" class=\"clearfix\">\n" \
4517+ " </nav>\n" \
4518+ " <p>&copy; 2014 Canonical Ltd. Ubuntu and Canonical are registered trademarks of Canonical Ltd.</p>\n" \
4519+ " </div>\n" \
4520+ "</footer>\n"
4521
4522=== added directory 'doc/qt/qml/css'
4523=== added file 'doc/qt/qml/css/base.css'
4524--- doc/qt/qml/css/base.css 1970-01-01 00:00:00 +0000
4525+++ doc/qt/qml/css/base.css 2014-08-19 17:36:21 +0000
4526@@ -0,0 +1,638 @@
4527+/**
4528+* Ubuntu Developer base stylesheet
4529+*
4530+* A base stylesheet containing site-wide styles
4531+*
4532+* @project Ubuntu Developer
4533+* @version 1.0
4534+* @author Canonical Web Team: Steve Edwards
4535+* @copyright 2011 Canonical Ltd.
4536+*/
4537+
4538+/**
4539+* @section Global
4540+*/
4541+
4542+body {
4543+ font-family: 'Ubuntu', 'Ubuntu Beta', UbuntuBeta, Ubuntu, 'Bitstream Vera Sans', 'DejaVu Sans', Tahoma, sans-serif;
4544+ font-size: 13px;
4545+ line-height: 1.4;
4546+ color: #333;
4547+}
4548+a {
4549+ color: #dd4814;
4550+ text-decoration: none;
4551+ outline: 0;
4552+}
4553+p, dl {
4554+ margin-bottom: 10px;
4555+}
4556+strong {
4557+ font-weight: bold;
4558+}
4559+em {
4560+ font-style: italic;
4561+}
4562+code{
4563+ padding: 10px;
4564+ font-family: 'Ubuntu Mono', 'Consolas', 'Monaco', 'DejaVu Sans Mono', Courier, monospace;
4565+ background-color: #fdf6f2;
4566+ display: block;
4567+ margin-bottom: 10px;
4568+ -moz-border-radius: 4px;
4569+ -webkit-border-radius: 4px;
4570+ border-radius: 4px;
4571+}
4572+h1 {
4573+ font-size: 36px;
4574+ line-height: 1.1;
4575+ margin-bottom: 20px;
4576+}
4577+article h1,
4578+h2 {
4579+ font-size: 24px;
4580+ line-height: 1.2;
4581+ margin-bottom: 14px;
4582+}
4583+h3 {
4584+ font-size: 16px;
4585+ line-height: 1.3;
4586+ margin-bottom: 8px;
4587+}
4588+h4 {
4589+ font-weight: bold;
4590+}
4591+
4592+time {
4593+ color:#999;
4594+}
4595+
4596+/**
4597+* @section Structure
4598+*/
4599+
4600+.header-login,
4601+.header-navigation div,
4602+.header-content div {
4603+ margin: 0 auto;
4604+ width: 940px;
4605+}
4606+
4607+.header-content h1{
4608+ background-color:#ffffff;
4609+ display:inline-block;
4610+}
4611+
4612+.header-content h2{
4613+ background-color:#ffffff;
4614+ display:table;
4615+}
4616+
4617+.header-login ul {
4618+ margin: 4px 0;
4619+ float: right;
4620+}
4621+.header-login li {
4622+ margin-right: 10px;
4623+ float: left;
4624+}
4625+.header-login a {
4626+ color: #333;
4627+}
4628+.header-navigation {
4629+ border-top: 2px solid #dd4814;
4630+ border-bottom: 2px solid #dd4814;
4631+ background-color: #fff;
4632+ height: 54px;
4633+ clear: right;
4634+ overflow: hidden;
4635+}
4636+.header-navigation nav ul {
4637+ border-right: 1px solid #dd4814;
4638+ float: right;
4639+}
4640+.header-navigation nav li {
4641+ border-left: 1px solid #dd4814;
4642+ float: left;
4643+ height: 54px;
4644+}
4645+.header-navigation nav a {
4646+ padding: 18px 14px 0;
4647+ font-size: 14px;
4648+ display: block;
4649+ height: 36px;
4650+}
4651+.header-navigation nav a:hover {
4652+ background-color: #fcece7;
4653+}
4654+.header-navigation nav .current_page_item a,
4655+.header-navigation nav .current_page_parent a,
4656+.header-navigation nav .current_page_ancestor a {
4657+ background-color: #dd4814;
4658+ color: #fff;
4659+}
4660+.header-navigation input {
4661+ margin: 12px 10px 0 10px;
4662+ padding: 5px;
4663+ border-top: 1px solid #a1a1a1;
4664+ border-right: 1px solid #e0e0e0;
4665+ border-bottom: 1px solid #fff;
4666+ border-left: 1px solid #e0e0e0;
4667+ width: 90px;
4668+ font-style: italic;
4669+ color: #ccc;
4670+ -moz-border-radius: 3px;
4671+ -webkit-border-radius: 3px;
4672+ border-radius: 3px;
4673+ -moz-box-shadow: inset 0 1px 1px #e0e0e0;
4674+ -webkit-box-shadow: inset 0 1px 1px #e0e0e0;
4675+ box-shadow: inset 0 1px 1px #e0e0e0;
4676+}
4677+.header-navigation h2 {
4678+ margin: 18px 0 0 6px;
4679+ text-transform: lowercase;
4680+ font-size: 22px;
4681+ color: #dd4814;
4682+ float: left;
4683+}
4684+.header-navigation .logo-ubuntu {
4685+ margin-top: 12px;
4686+ float: left;
4687+}
4688+.header-content .header-navigation-secondary {
4689+ margin-bottom: 40px;
4690+ padding: 0;
4691+ position: relative;
4692+ z-index: 2;
4693+}
4694+.header-navigation-secondary div {
4695+ padding: 0;
4696+ border: 2px solid #dd4814;
4697+ -moz-border-radius: 0px 0px 4px 4px;
4698+ -webkit-border-radius: 0px 0px 4px 4px;
4699+ border-radius: 0px 0px 4px 4px;
4700+ background: #fff;
4701+ border-top: 0px;
4702+ width: 936px;
4703+}
4704+.header-navigation-secondary nav li {
4705+ float: left;
4706+}
4707+.header-navigation-secondary nav li a {
4708+ color: #333;
4709+ display: block;
4710+ height: 25px;
4711+ padding: 8px 8px 0;
4712+}
4713+.header-navigation-secondary nav li:hover,
4714+.header-navigation-secondary nav .current_page_item a {
4715+ background: url("../img/sec-nav-hover.gif");
4716+}
4717+.header-content {
4718+ padding-bottom: 30px;
4719+ border-bottom: 1px solid #e0e0e0;
4720+ -moz-box-shadow: 0 1px 3px #e0e0e0;
4721+ -webkit-box-shadow: 0 1px 3px #e0e0e0;
4722+ box-shadow: 0 1px 3px #e0e0e0;
4723+ margin-bottom: 3px;
4724+ position: relative;
4725+ overflow: hidden;
4726+}
4727+footer {
4728+ padding: 10px 10px 40px 10px;
4729+ position: relative;
4730+ -moz-border-radius: 0 0 4px 4px;
4731+ -webkit-border-radius: 0 0 4px 4px;
4732+ border-radius: 0 0 4px 4px;
4733+ font-size: 12px;
4734+ background: url("../img/background-footer.png") repeat scroll 0 0 #f7f6f5;
4735+}
4736+footer div {
4737+ margin: 0 auto;
4738+ padding: 0 10px;
4739+ width: 940px;
4740+}
4741+footer a {
4742+ color: #000;
4743+}
4744+footer nav ul {
4745+ margin: 10px 17px 30px 0;
4746+ width: 172px;
4747+ display: inline-block;
4748+ vertical-align: top;
4749+ height: auto;
4750+ zoom: 1;
4751+ *display: inline;
4752+}
4753+footer nav ul.last {
4754+ margin-right: 0;
4755+}
4756+footer nav li {
4757+ margin-bottom: 8px;
4758+}
4759+footer nav li:first-child {
4760+ font-weight: bold;
4761+}
4762+footer p {
4763+ margin-bottom: 0;
4764+}
4765+#content {
4766+ padding-top: 35px;
4767+}
4768+.arrow-nav {
4769+ display: none;
4770+ position: absolute;
4771+ top: -1px;
4772+ z-index: 3;
4773+}
4774+.shadow {
4775+ margin: 30px 0 3px 0;
4776+ border-bottom: 1px solid #e0e0e0;
4777+ -moz-box-shadow: 0 2px 3px #e0e0e0;
4778+ -webkit-box-shadow: 0 2px 3px #e0e0e0;
4779+ box-shadow: 0 2px 3px #e0e0e0;
4780+ height: 3px;
4781+}
4782+
4783+/**
4784+* @section Site-wide
4785+*/
4786+
4787+#content h2{
4788+ font-size:24px;
4789+}
4790+
4791+.box-orange {
4792+ padding: 10px;
4793+ border: 3px solid #dd4814;
4794+ -moz-border-radius: 4px;
4795+ -webkit-border-radius: 4px;
4796+ border-radius: 4px;
4797+}
4798+.box-orange .link-action-small {
4799+ float: right;
4800+ margin: 0 0 0 20px;
4801+}
4802+.link-bug {
4803+ margin-left: 10px;
4804+ color: #999;
4805+}
4806+.link-action {
4807+ float: left;
4808+ margin-bottom: 20px;
4809+ padding: 8px 12px;
4810+ display: block;
4811+ background-color: #dd4814;
4812+ color: #fff;
4813+ -moz-border-radius: 20px;
4814+ -webkit-border-radius: 20px;
4815+ border-radius: 20px;
4816+ font-size: 16px;
4817+ line-height: 1.3;
4818+ border-top: 3px solid #e6633a;
4819+ border-bottom: 3px solid #c03d14;
4820+}
4821+.link-action2 {
4822+ float: left;
4823+ display: block;
4824+ color: #fff;
4825+ font-size: 16px;
4826+ line-height: 1.3;
4827+}
4828+.link-action2 span{
4829+ display:block;
4830+ float:left;
4831+}
4832+.link-action2 .cta-left{
4833+ background:url(../img/button-cta-left.png) no-repeat;
4834+ width:22px;
4835+ height:48px;
4836+}
4837+.link-action2 .cta-center{
4838+ background:url(../img/button-cta-slice.png) repeat-x;
4839+ line-height:45px;
4840+ height:48px;
4841+}
4842+.link-action2 .cta-right{
4843+ background:url(../img/button-cta-right.png) no-repeat;
4844+ width:22px;
4845+ height:48px;
4846+}
4847+
4848+.link-action-small {
4849+ float: left;
4850+ display: block;
4851+ color: #fff;
4852+ font-size: 16px;
4853+}
4854+.link-action-small span{
4855+ display:block;
4856+ float:left;
4857+ height:42px;
4858+}
4859+.link-action-small .cta-left{
4860+ background:url(../img/button-cta-left-small.png) no-repeat;
4861+ width:19px;
4862+}
4863+.link-action-small .cta-center{
4864+ background:url(../img/button-cta-slice-small.png) repeat-x;
4865+ line-height:42px;
4866+}
4867+.link-action-small .cta-right{
4868+ background:url(../img/button-cta-right-small.png) no-repeat;
4869+ width:19px;
4870+}
4871+
4872+.link-action:active {
4873+ position: relative;
4874+ top: 1px;
4875+}
4876+.link-action2:active {
4877+ position: relative;
4878+ top: 1px;
4879+}
4880+.link-action-small:active {
4881+ position: relative;
4882+ top: 1px;
4883+}
4884+.list-bullets li {
4885+ margin-bottom: 10px;
4886+ list-style: disc;
4887+ list-style-position: inside;
4888+}
4889+.box {
4890+ margin-bottom: 30px;
4891+ padding: 15px;
4892+ border: 1px solid #aea79f;
4893+ -moz-border-radius: 4px;
4894+ -webkit-border-radius: 4px;
4895+ border-radius: 4px;
4896+}
4897+.box-padded {
4898+ margin-bottom: 30px;
4899+ padding: 5px;
4900+ border: 2px solid #aea79f;
4901+ -moz-border-radius: 4px;
4902+ -webkit-border-radius: 4px;
4903+ border-radius: 4px;
4904+ background: url("../img/pattern-featured.gif") repeat scroll 0 0 #ebe9e7;
4905+ overflow: hidden;
4906+}
4907+.box-padded h3 {
4908+ margin: 5px 0 10px 5px;
4909+}
4910+.box-padded div {
4911+ padding: 10px;
4912+ border: 1px solid #aea79f;
4913+ -moz-border-radius: 4px;
4914+ -webkit-border-radius: 4px;
4915+ border-radius: 4px;
4916+ background-color: #fff;
4917+ overflow: hidden;
4918+}
4919+.box-padded li {
4920+ padding: 0 10px;
4921+ float: left;
4922+ width: 211px;
4923+ border-right: 1px dotted #aea79f;
4924+}
4925+.box-padded li.first {
4926+ padding: 0;
4927+ margin-bottom: 0;
4928+}
4929+.box-padded li.last {
4930+ border: 0;
4931+ width: 217px;
4932+}
4933+.box-padded img {
4934+ margin: 0 10px 50px 0;
4935+ float: left;
4936+ -moz-border-radius: 8px;
4937+ -webkit-border-radius: 8px;
4938+ border-radius: 8px;
4939+}
4940+.box-clear {
4941+ margin-bottom: 40px;
4942+}
4943+.box-clear .grid-4.first {
4944+ margin-right: 15px;
4945+ padding-right: 15px;
4946+}
4947+.box-clear .grid-4 {
4948+ margin-left: 0;
4949+ margin-right: 10px;
4950+ padding-right: 10px;
4951+ width: 298px;
4952+}
4953+.box-clear time {
4954+ display: block;
4955+ border-bottom: 1px dotted #aea79f;
4956+ padding-bottom: 10px;
4957+ margin-bottom: 10px;
4958+}
4959+.box-clear div.first {
4960+ border-right: 1px dotted #aea79f;
4961+}
4962+.box-clear a {
4963+ display: block;
4964+}
4965+.box-clear .rss {
4966+ background: url("../img/rss.jpg") no-repeat scroll 0 center;
4967+ padding-left: 20px;
4968+}
4969+.box-clear .location {
4970+ display: block;
4971+ margin-bottom: 1px;
4972+}
4973+.box-clear .last {
4974+ margin: 0;
4975+ padding-right: 0;
4976+ -moz-border-radius: 4px;
4977+ -webkit-border-radius: 4px;
4978+ border-radius: 4px;
4979+ width: 293px;
4980+}
4981+
4982+/* Widgets */
4983+
4984+.ui-state-focus {
4985+ outline: none;
4986+}
4987+.ui-accordion {
4988+ border-bottom: 1px dotted #aea79f;
4989+}
4990+.ui-accordion a {
4991+ display: block;
4992+}
4993+.ui-accordion h3 {
4994+ margin-bottom: 0;
4995+ border-top: 1px dotted #aea79f;
4996+ position: relative;
4997+ font-size: 13px;
4998+ font-weight: bold;
4999+}
5000+.ui-accordion h3 a {
The diff has been truncated for viewing.

Subscribers

People subscribed via source and target branches