Merge lp:~phablet-team/messaging-framework/add-dummy-protocol into lp:messaging-framework

[Tiago Salem Herrmann]

Add dummy protocol implementation.

Add dummy protocol implementation.

[system-apps-ci-bot (system-apps-ci-bot)]

FAILED: Continuous integration, rev:78
https://jenkins.canonical.com/system-apps/job/lp-messaging-framework-ci/1/
Executed test runs:
    FAILURE: https://jenkins.canonical.com/system-apps/job/build/2331/console
    SUCCESS: https://jenkins.canonical.com/system-apps/job/build-0-fetch/2330
    FAILURE: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=amd64,release=xenial+overlay/2152/console
    FAILURE: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=amd64,release=zesty/2152/console
    FAILURE: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=armhf,release=xenial+overlay/2152/console
    FAILURE: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=armhf,release=zesty/2152/console
    FAILURE: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=i386,release=xenial+overlay/2152/console
    FAILURE: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=i386,release=zesty/2152/console

Click here to trigger a rebuild:
https://jenkins.canonical.com/system-apps/job/lp-messaging-framework-ci/1/rebuild

review: Needs Fixing (continuous-integration)

[lp:~phablet-team/messaging-framework/add-dummy-protocol]

79. By Tiago Salem Herrmann on 2017-03-21

add missing png files

[system-apps-ci-bot (system-apps-ci-bot)]

PASSED: Continuous integration, rev:79
https://jenkins.canonical.com/system-apps/job/lp-messaging-framework-ci/2/
Executed test runs:
    SUCCESS: https://jenkins.canonical.com/system-apps/job/build/2333
    SUCCESS: https://jenkins.canonical.com/system-apps/job/build-0-fetch/2332
    SUCCESS: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=amd64,release=xenial+overlay/2154
        deb: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=amd64,release=xenial+overlay/2154/artifact/output/*zip*/output.zip
    SUCCESS: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=amd64,release=zesty/2154
        deb: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=amd64,release=zesty/2154/artifact/output/*zip*/output.zip
    SUCCESS: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=armhf,release=xenial+overlay/2154
        deb: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=armhf,release=xenial+overlay/2154/artifact/output/*zip*/output.zip
    SUCCESS: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=armhf,release=zesty/2154
        deb: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=armhf,release=zesty/2154/artifact/output/*zip*/output.zip
    SUCCESS: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=i386,release=xenial+overlay/2154
        deb: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=i386,release=xenial+overlay/2154/artifact/output/*zip*/output.zip
    SUCCESS: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=i386,release=zesty/2154
        deb: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=i386,release=zesty/2154/artifact/output/*zip*/output.zip

Click here to trigger a rebuild:
https://jenkins.canonical.com/system-apps/job/lp-messaging-framework-ci/2/rebuild

review: Approve (continuous-integration)

[lp:~phablet-team/messaging-framework/add-dummy-protocol]

80. By Tiago Salem Herrmann on 2017-03-22

move share objects to a separate directory

[system-apps-ci-bot (system-apps-ci-bot)]

PASSED: Continuous integration, rev:80
https://jenkins.canonical.com/system-apps/job/lp-messaging-framework-ci/3/
Executed test runs:
    SUCCESS: https://jenkins.canonical.com/system-apps/job/build/2338
    SUCCESS: https://jenkins.canonical.com/system-apps/job/build-0-fetch/2337
    SUCCESS: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=amd64,release=xenial+overlay/2159
        deb: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=amd64,release=xenial+overlay/2159/artifact/output/*zip*/output.zip
    SUCCESS: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=amd64,release=zesty/2159
        deb: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=amd64,release=zesty/2159/artifact/output/*zip*/output.zip
    SUCCESS: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=armhf,release=xenial+overlay/2159
        deb: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=armhf,release=xenial+overlay/2159/artifact/output/*zip*/output.zip
    SUCCESS: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=armhf,release=zesty/2159
        deb: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=armhf,release=zesty/2159/artifact/output/*zip*/output.zip
    SUCCESS: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=i386,release=xenial+overlay/2159
        deb: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=i386,release=xenial+overlay/2159/artifact/output/*zip*/output.zip
    SUCCESS: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=i386,release=zesty/2159
        deb: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=i386,release=zesty/2159/artifact/output/*zip*/output.zip

Click here to trigger a rebuild:
https://jenkins.canonical.com/system-apps/job/lp-messaging-framework-ci/3/rebuild

review: Approve (continuous-integration)

[lp:~phablet-team/messaging-framework/add-dummy-protocol]

81. By Gustavo Pichorim Boiko on 2017-03-22

Merge parent branch

[Gustavo Pichorim Boiko (boiko)]

Looks good!

review: Approve

[system-apps-ci-bot (system-apps-ci-bot)]

FAILED: Continuous integration, rev:81
https://jenkins.canonical.com/system-apps/job/lp-messaging-framework-ci/4/
Executed test runs:
    FAILURE: https://jenkins.canonical.com/system-apps/job/build/2347/console
    SUCCESS: https://jenkins.canonical.com/system-apps/job/build-0-fetch/2347
    SUCCESS: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=amd64,release=xenial+overlay/2165
        deb: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=amd64,release=xenial+overlay/2165/artifact/output/*zip*/output.zip
    SUCCESS: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=amd64,release=zesty/2165
        deb: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=amd64,release=zesty/2165/artifact/output/*zip*/output.zip
    FAILURE: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=armhf,release=xenial+overlay/2165/console
    SUCCESS: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=armhf,release=zesty/2165
        deb: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=armhf,release=zesty/2165/artifact/output/*zip*/output.zip
    SUCCESS: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=i386,release=xenial+overlay/2165
        deb: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=i386,release=xenial+overlay/2165/artifact/output/*zip*/output.zip
    SUCCESS: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=i386,release=zesty/2165
        deb: https://jenkins.canonical.com/system-apps/job/build-2-binpkg/arch=i386,release=zesty/2165/artifact/output/*zip*/output.zip

Click here to trigger a rebuild:
https://jenkins.canonical.com/system-apps/job/lp-messaging-framework-ci/4/rebuild

review: Needs Fixing (continuous-integration)

Unmerged revisions

81. By Gustavo Pichorim Boiko on 2017-03-22

Merge parent branch

80. By Tiago Salem Herrmann on 2017-03-22

move share objects to a separate directory

79. By Tiago Salem Herrmann on 2017-03-21

add missing png files

78. By Tiago Salem Herrmann on 2017-03-21

Add dummy protocol implementation

77. By Tiago Salem Herrmann on 2017-03-21

merge parent branch

=== modified file 'CMakeLists.txt'
--- CMakeLists.txt	2016-12-06 20:24:14 +0000
+++ CMakeLists.txt	2017-03-22 21:22:50 +0000
@@ -1,6 +1,7 @@
 cmake_minimum_required(VERSION 3.0.2)
 project(messaging-framework VERSION "0.1" LANGUAGES C CXX)
 set(CMAKE_MODULE_PATH ${CMAKE_CURRENT_SOURCE_DIR}/cmake)
+set(IS_MF_BUILD "1")
 
 # Select a pedantic set of compiler flags and enable C++11 support.
 set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -Wall -Wextra -Wno-deprecated-register -Wno-extra-semi -Wno-gnu-zero-variadic-macro-arguments -fvisibility=hidden")
@@ -97,4 +98,5 @@
 add_subdirectory(doc)
 add_subdirectory(include)
 add_subdirectory(src)
+add_subdirectory(examples)
 add_subdirectory(tests)

=== modified file 'debian/control.in'
--- debian/control.in	2017-03-22 21:22:50 +0000
+++ debian/control.in	2017-03-22 21:22:50 +0000
@@ -46,3 +46,9 @@
  This layer communicates third party plugins with systems like
  telepathy allowing changing the system by other without having
  to modify the plugins
+
+Package: mfw-plugin-dummy
+Architecture: any
+Depends: ${misc:Depends}, ${shlibs:Depends}
+Description: Ubuntu Messaging Framework Dummy Plugin
+ A plugin for messaging fw implementing Dummy protocol

=== added file 'debian/mfw-plugin-dummy.install'
--- debian/mfw-plugin-dummy.install	1970-01-01 00:00:00 +0000
+++ debian/mfw-plugin-dummy.install	2017-03-22 21:22:50 +0000
@@ -0,0 +1,6 @@
+usr/lib/*/messaging-framework/libmfw-plugin-dummy.so* 
+usr/share/dbus-1/services/org.freedesktop.Telepathy.ConnectionManager.dummy.service
+usr/share/telephony-service/protocols/dummy.protocol
+usr/share/dummy/assets/dummy-background.png
+usr/share/dummy/assets/dummy.png
+usr/share/telepathy/managers/dummy.manager

=== added directory 'examples'
=== added file 'examples/CMakeLists.txt'
--- examples/CMakeLists.txt	1970-01-01 00:00:00 +0000
+++ examples/CMakeLists.txt	2017-03-22 21:22:50 +0000
@@ -0,0 +1,1 @@
+add_subdirectory(mfw-plugin-dummy)

=== added directory 'examples/mfw-plugin-dummy'
=== added file 'examples/mfw-plugin-dummy/CMakeLists.txt'
--- examples/mfw-plugin-dummy/CMakeLists.txt	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/CMakeLists.txt	2017-03-22 21:22:50 +0000
@@ -0,0 +1,61 @@
+if (NOT IS_MF_BUILD)
+    project(mfw-plugin-dummy C CXX)
+    cmake_minimum_required(VERSION 2.8.10)
+    set(CMAKE_MODULE_PATH ${CMAKE_CURRENT_SOURCE_DIR}/cmake)
+
+    # Select a pedantic set of compiler flags and enable C++11 support.
+    set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -Wall -Wextra -Wno-deprecated-register -Wno-extra-semi -Wno-gnu-zero-variadic-macro-arguments -fvisibility=hidden")
+    set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++11 -Wall -fno-strict-aliasing -fvisibility=hidden -fvisibility-inlines-hidden -Wextra -Wno-deprecated-register -Wno-extra-semi -Wno-gnu-zero-variadic-macro-arguments -ggdb -O0")
+    set(CMAKE_SHARED_LINKER_FLAGS "${CMAKE_SHARED_LINKER_FLAGS} -Wl,--no-undefined")
+    set(CMAKE_POSITION_INDEPENDENT_CODE ON)
+
+    # Store in CMAKE_DEB_HOST_ARCH var the current build architecture
+    execute_process(COMMAND
+      dpkg-architecture
+        -qDEB_HOST_ARCH
+      OUTPUT_VARIABLE
+        CMAKE_DEB_HOST_ARCH
+      OUTPUT_STRIP_TRAILING_WHITESPACE
+    )
+
+    # Include the entire CTest functionality, specifically for MakeNightlyMemCheck.
+    include(CTest)
+    include(GNUInstallDirs)
+
+    find_package(Boost COMPONENTS filesystem program_options system REQUIRED)
+    find_package(GLog)
+    find_package(PkgConfig)
+    find_package(Qt5Core REQUIRED)
+    find_package(Qt5DBus REQUIRED)
+    find_package(Threads)
+    pkg_check_modules(PROCESS_CPP process-cpp REQUIRED)
+    pkg_check_modules(MESSAGING_FW REQUIRED messaging-framework1)
+endif()
+
+set(CMAKE_INCLUDE_CURRENT_DIR ON)
+
+set(SO_VERSION_MAJOR "1")
+set(SO_VERSION_MINOR "1")
+set(SO_VERSION_PATCH "0")
+set(SO_VERSION "${SO_VERSION_MAJOR}.${SO_VERSION_MINOR}.${SO_VERSION_PATCH}")
+
+option(CLICK_MODE "Installs to a contained location" on)
+option(ACCEPTANCE_MODE "Enables the acceptance tests" off)
+
+if (${ACCEPTANCE_MODE})
+    set(CTEST_CONFIGURATION_TYPE acceptance)
+endif()
+include_directories(
+  ${MESSAGING_FW_INCLUDE_DIRS}
+  ${CMAKE_CURRENT_SOURCE_DIR}/include
+  ${CMAKE_SOURCE_DIR}/include
+  ${Boost_INCLUDE_DIRS}
+  ${GLog_INCLUDE_DIR}
+  ${CPPNETLIB_INCLUDE_DIRS}
+)
+
+add_subdirectory(data)
+add_subdirectory(doc)
+add_subdirectory(include)
+add_subdirectory(src)
+

=== added directory 'examples/mfw-plugin-dummy/cmake'
=== added file 'examples/mfw-plugin-dummy/cmake/EnableCoverageReport.cmake'
--- examples/mfw-plugin-dummy/cmake/EnableCoverageReport.cmake	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/cmake/EnableCoverageReport.cmake	2017-03-22 21:22:50 +0000
@@ -0,0 +1,153 @@
+# - Creates a special coverage build type and target on GCC.
+#
+# Defines a function ENABLE_COVERAGE_REPORT which generates the coverage target
+# for selected targets. Optional arguments to this function are used to filter
+# unwanted results using globbing expressions. Moreover targets with tests for
+# the source code can be specified to trigger regenerating the report if the
+# test has changed
+#
+# ENABLE_COVERAGE_REPORT(TARGETS target... [FILTER filter...] [TESTS test targets...])
+#
+# To generate a coverage report first build the project with
+# CMAKE_BUILD_TYPE=coverage, then call make test and afterwards make coverage.
+#
+# The coverage report is based on gcov. Depending on the availability of lcov
+# a HTML report will be generated and/or an XML report of gcovr is found.
+# The generated coverage target executes all found solutions. Special targets
+# exist to create e.g. only the xml report: coverage-xml. 
+#
+# Copyright (C) 2010 by Johannes Wienke <jwienke at techfak dot uni-bielefeld dot de>
+#
+# This program is free software; you can redistribute it
+# and/or modify it under the terms of the GNU General
+# Public License as published by the Free Software Foundation;
+# either version 2, or (at your option)
+# any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+
+INCLUDE(ParseArguments)
+
+FIND_PACKAGE(Lcov)
+FIND_PACKAGE(gcovr)
+
+FUNCTION(ENABLE_COVERAGE_REPORT)
+    
+    # argument parsing
+    PARSE_ARGUMENTS(ARG "FILTER;TARGETS;TESTS" "" ${ARGN})
+    
+    SET(COVERAGE_RAW_FILE "${CMAKE_BINARY_DIR}/coverage.raw.info")
+    SET(COVERAGE_FILTERED_FILE "${CMAKE_BINARY_DIR}/coverage.info")
+    SET(COVERAGE_REPORT_DIR "${CMAKE_BINARY_DIR}/coveragereport")
+    SET(COVERAGE_XML_FILE "${CMAKE_BINARY_DIR}/coverage.xml")
+    SET(COVERAGE_XML_COMMAND_FILE "${CMAKE_BINARY_DIR}/coverage-xml.cmake")
+    
+    # decide if there is any tool to create coverage data
+    SET(TOOL_FOUND FALSE)
+    IF(LCOV_FOUND OR GCOVR_FOUND)
+        SET(TOOL_FOUND TRUE)
+    ENDIF()
+    IF(NOT TOOL_FOUND)
+        MESSAGE(STATUS "Cannot enable coverage targets because neither lcov nor gcovr are found.")
+    ENDIF()
+    
+    STRING(TOLOWER "${CMAKE_BUILD_TYPE}" COVERAGE_BUILD_TYPE)
+    IF(CMAKE_COMPILER_IS_GNUCXX AND TOOL_FOUND AND "${COVERAGE_BUILD_TYPE}" MATCHES "coverage")
+    
+        MESSAGE(STATUS "Coverage support enabled for targets: ${ARG_TARGETS}")
+    
+        # create coverage build type
+        SET(CMAKE_CXX_FLAGS_COVERAGE ${CMAKE_CXX_FLAGS_DEBUG} PARENT_SCOPE)
+        SET(CMAKE_C_FLAGS_COVERAGE ${CMAKE_C_FLAGS_DEBUG} PARENT_SCOPE)
+        SET(CMAKE_CONFIGURATION_TYPES ${CMAKE_CONFIGURATION_TYPES} coverage PARENT_SCOPE)
+    
+        # instrument targets
+        SET_TARGET_PROPERTIES(${ARG_TARGETS} PROPERTIES COMPILE_FLAGS --coverage
+                                                        LINK_FLAGS --coverage)
+    
+        # html report
+        IF (LCOV_FOUND)
+        
+            MESSAGE(STATUS "Enabling HTML coverage report")
+    
+            # set up coverage target
+            
+            ADD_CUSTOM_COMMAND(OUTPUT ${COVERAGE_RAW_FILE}
+                               COMMAND ${LCOV_EXECUTABLE} -c -d ${CMAKE_BINARY_DIR} -o ${COVERAGE_RAW_FILE}
+                               WORKING_DIRECTORY ${CMAKE_BINARY_DIR}
+                               COMMENT "Collecting coverage data"
+                               DEPENDS ${ARG_TARGETS} ${ARG_TESTS}
+                               VERBATIM)
+            
+            # filter unwanted stuff
+            LIST(LENGTH ARG_FILTER FILTER_LENGTH)
+            IF(${FILTER_LENGTH} GREATER 0)
+                SET(FILTER COMMAND ${LCOV_EXECUTABLE})
+                FOREACH(F ${ARG_FILTER})
+                    SET(FILTER ${FILTER} -r ${COVERAGE_FILTERED_FILE} ${F})
+                ENDFOREACH()
+                SET(FILTER ${FILTER} -o ${COVERAGE_FILTERED_FILE})
+            ELSE()
+                SET(FILTER "")
+            ENDIF()
+            
+            ADD_CUSTOM_COMMAND(OUTPUT ${COVERAGE_FILTERED_FILE}
+                               COMMAND ${LCOV_EXECUTABLE} -e ${COVERAGE_RAW_FILE} "${CMAKE_SOURCE_DIR}*"  -o ${COVERAGE_FILTERED_FILE}
+                               ${FILTER}
+                               DEPENDS ${COVERAGE_RAW_FILE}
+                               COMMENT "Filtering recorded coverage data for project-relevant entries"
+                               VERBATIM)
+            ADD_CUSTOM_COMMAND(OUTPUT ${COVERAGE_REPORT_DIR}
+                               COMMAND ${CMAKE_COMMAND} -E make_directory ${COVERAGE_REPORT_DIR}
+                               COMMAND ${GENHTML_EXECUTABLE} --legend --show-details -t "${PROJECT_NAME} test coverage" -o ${COVERAGE_REPORT_DIR} ${COVERAGE_FILTERED_FILE}
+                               DEPENDS ${COVERAGE_FILTERED_FILE}
+                               COMMENT "Generating HTML coverage report in ${COVERAGE_REPORT_DIR}"
+                               VERBATIM)
+                               
+            ADD_CUSTOM_TARGET(coverage-html
+                              DEPENDS ${COVERAGE_REPORT_DIR})
+                              
+        ENDIF()
+        
+        # xml coverage report
+        IF(GCOVR_FOUND)
+        
+            MESSAGE(STATUS "Enabling XML coverage report")
+        
+            # gcovr cannot write directly to a file so the execution needs to
+            # be wrapped in a cmake file that generates the file output
+            FILE(WRITE ${COVERAGE_XML_COMMAND_FILE}
+                 "SET(ENV{LANG} en)\n")
+            FILE(APPEND ${COVERAGE_XML_COMMAND_FILE}
+                "EXECUTE_PROCESS(COMMAND \"${GCOVR_EXECUTABLE}\" --exclude=tests.* --exclude=obj-.* --exclude=cmake.* -x -r \"${CMAKE_SOURCE_DIR}\" OUTPUT_FILE \"${COVERAGE_XML_FILE}\" WORKING_DIRECTORY \"${CMAKE_BINARY_DIR}\")\n")
+        
+            ADD_CUSTOM_COMMAND(OUTPUT ${COVERAGE_XML_FILE}
+                               COMMAND ${CMAKE_COMMAND} ARGS -P ${COVERAGE_XML_COMMAND_FILE}
+                               COMMENT "Generating coverage XML report"
+                               VERBATIM)
+                               
+            ADD_CUSTOM_TARGET(coverage-xml
+                              DEPENDS ${COVERAGE_XML_FILE})
+        
+        ENDIF()
+        
+        # provide a global coverage target executing both steps if available
+        SET(GLOBAL_DEPENDS "")
+        IF(LCOV_FOUND)
+            LIST(APPEND GLOBAL_DEPENDS ${COVERAGE_REPORT_DIR})
+        ENDIF()
+        IF(GCOVR_FOUND)
+            LIST(APPEND GLOBAL_DEPENDS ${COVERAGE_XML_FILE})
+        ENDIF()
+        IF(LCOV_FOUND OR GCOVR_FOUND)
+            ADD_CUSTOM_TARGET(coverage
+                              DEPENDS ${GLOBAL_DEPENDS})
+        ENDIF()
+                          
+    ENDIF()
+
+ENDFUNCTION()   

=== added file 'examples/mfw-plugin-dummy/cmake/FindGLog.cmake'
--- examples/mfw-plugin-dummy/cmake/FindGLog.cmake	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/cmake/FindGLog.cmake	2017-03-22 21:22:50 +0000
@@ -0,0 +1,14 @@
+if (GLog_INCLUDE_DIR)
+  # Already in cache, be silent
+  set(GLog_FIND_QUIETLY TRUE)
+endif ()
+
+find_path(GLog_INCLUDE_DIR glog/logging.h)
+
+find_library(GLog_LIBRARY libglog.so
+             HINTS /usr/lib/arm-linux-gnueabihf/)
+
+include(FindPackageHandleStandardArgs)
+find_package_handle_standard_args(GLog DEFAULT_MSG GLog_LIBRARY GLog_INCLUDE_DIR)
+
+mark_as_advanced(GLog_LIBRARY GLog_INCLUDE_DIR)

=== added file 'examples/mfw-plugin-dummy/cmake/FindLcov.cmake'
--- examples/mfw-plugin-dummy/cmake/FindLcov.cmake	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/cmake/FindLcov.cmake	2017-03-22 21:22:50 +0000
@@ -0,0 +1,29 @@
+# - Find lcov 
+# Will define:
+#
+# LCOV_EXECUTABLE - the lcov binary
+# GENHTML_EXECUTABLE - the genhtml executable
+#
+# Copyright (C) 2010 by Johannes Wienke <jwienke at techfak dot uni-bielefeld dot de>
+#
+# This program is free software; you can redistribute it
+# and/or modify it under the terms of the GNU General
+# Public License as published by the Free Software Foundation;
+# either version 2, or (at your option)
+# any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+
+INCLUDE(FindPackageHandleStandardArgs)
+
+FIND_PROGRAM(LCOV_EXECUTABLE lcov)
+FIND_PROGRAM(GENHTML_EXECUTABLE genhtml)
+
+FIND_PACKAGE_HANDLE_STANDARD_ARGS(Lcov DEFAULT_MSG LCOV_EXECUTABLE GENHTML_EXECUTABLE)
+
+# only visible in advanced view
+MARK_AS_ADVANCED(LCOV_EXECUTABLE GENHTML_EXECUTABLE)

=== added file 'examples/mfw-plugin-dummy/cmake/Findgcovr.cmake'
--- examples/mfw-plugin-dummy/cmake/Findgcovr.cmake	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/cmake/Findgcovr.cmake	2017-03-22 21:22:50 +0000
@@ -0,0 +1,31 @@
+# - Find gcovr scrip 
+# Will define:
+#
+# GCOVR_EXECUTABLE - the gcovr script
+#
+# Uses:
+#
+# GCOVR_ROOT - root to search for the script
+#
+# Copyright (C) 2011 by Johannes Wienke <jwienke at techfak dot uni-bielefeld dot de>
+#
+# This program is free software; you can redistribute it
+# and/or modify it under the terms of the GNU General
+# Public License as published by the Free Software Foundation;
+# either version 2, or (at your option)
+# any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+
+INCLUDE(FindPackageHandleStandardArgs)
+
+FIND_PROGRAM(GCOVR_EXECUTABLE gcovr HINTS ${GCOVR_ROOT} "${GCOVR_ROOT}/bin")
+
+FIND_PACKAGE_HANDLE_STANDARD_ARGS(gcovr DEFAULT_MSG GCOVR_EXECUTABLE)
+
+# only visible in advanced view
+MARK_AS_ADVANCED(GCOVR_EXECUTABLE)

=== added file 'examples/mfw-plugin-dummy/cmake/LibFindMacros.cmake'
--- examples/mfw-plugin-dummy/cmake/LibFindMacros.cmake	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/cmake/LibFindMacros.cmake	2017-03-22 21:22:50 +0000
@@ -0,0 +1,112 @@
+# Version 1.0 (2013-04-12)
+# Public Domain, originally written by Lasse Kärkkäinen <[e-mail]>
+# Published at http://www.cmake.org/Wiki/CMake:How_To_Find_Libraries
+
+# If you improve the script, please modify the forementioned wiki page because
+# I no longer maintain my scripts (hosted as static files at zi.fi). Feel free
+# to remove this entire header if you use real version control instead.
+
+# Changelog:
+# 2013-04-12  Added version number (1.0) and this header, no other changes
+# 2009-10-08  Originally published
+
+
+# Works the same as find_package, but forwards the "REQUIRED" and "QUIET" arguments
+# used for the current package. For this to work, the first parameter must be the
+# prefix of the current package, then the prefix of the new package etc, which are
+# passed to find_package.
+macro (libfind_package PREFIX)
+  set (LIBFIND_PACKAGE_ARGS ${ARGN})
+  if (${PREFIX}_FIND_QUIETLY)
+    set (LIBFIND_PACKAGE_ARGS ${LIBFIND_PACKAGE_ARGS} QUIET)
+  endif (${PREFIX}_FIND_QUIETLY)
+  if (${PREFIX}_FIND_REQUIRED)
+    set (LIBFIND_PACKAGE_ARGS ${LIBFIND_PACKAGE_ARGS} REQUIRED)
+  endif (${PREFIX}_FIND_REQUIRED)
+  find_package(${LIBFIND_PACKAGE_ARGS})
+endmacro (libfind_package)
+
+# CMake developers made the UsePkgConfig system deprecated in the same release (2.6)
+# where they added pkg_check_modules. Consequently I need to support both in my scripts
+# to avoid those deprecated warnings. Here's a helper that does just that.
+# Works identically to pkg_check_modules, except that no checks are needed prior to use.
+macro (libfind_pkg_check_modules PREFIX PKGNAME)
+  if (${CMAKE_MAJOR_VERSION} EQUAL 2 AND ${CMAKE_MINOR_VERSION} EQUAL 4)
+    include(UsePkgConfig)
+    pkgconfig(${PKGNAME} ${PREFIX}_INCLUDE_DIRS ${PREFIX}_LIBRARY_DIRS ${PREFIX}_LDFLAGS ${PREFIX}_CFLAGS)
+  else (${CMAKE_MAJOR_VERSION} EQUAL 2 AND ${CMAKE_MINOR_VERSION} EQUAL 4)
+    find_package(PkgConfig)
+    if (PKG_CONFIG_FOUND)
+      pkg_check_modules(${PREFIX} ${PKGNAME})
+    endif (PKG_CONFIG_FOUND)
+  endif (${CMAKE_MAJOR_VERSION} EQUAL 2 AND ${CMAKE_MINOR_VERSION} EQUAL 4)
+endmacro (libfind_pkg_check_modules)
+
+# Do the final processing once the paths have been detected.
+# If include dirs are needed, ${PREFIX}_PROCESS_INCLUDES should be set to contain
+# all the variables, each of which contain one include directory.
+# Ditto for ${PREFIX}_PROCESS_LIBS and library files.
+# Will set ${PREFIX}_FOUND, ${PREFIX}_INCLUDE_DIRS and ${PREFIX}_LIBRARIES.
+# Also handles errors in case library detection was required, etc.
+macro (libfind_process PREFIX)
+  # Skip processing if already processed during this run
+  if (NOT ${PREFIX}_FOUND)
+    # Start with the assumption that the library was found
+    set (${PREFIX}_FOUND TRUE)
+
+    # Process all includes and set _FOUND to false if any are missing
+    foreach (i ${${PREFIX}_PROCESS_INCLUDES})
+      if (${i})
+        set (${PREFIX}_INCLUDE_DIRS ${${PREFIX}_INCLUDE_DIRS} ${${i}})
+        mark_as_advanced(${i})
+      else (${i})
+        set (${PREFIX}_FOUND FALSE)
+      endif (${i})
+    endforeach (i)
+
+    # Process all libraries and set _FOUND to false if any are missing
+    foreach (i ${${PREFIX}_PROCESS_LIBS})
+      if (${i})
+        set (${PREFIX}_LIBRARIES ${${PREFIX}_LIBRARIES} ${${i}})
+        mark_as_advanced(${i})
+      else (${i})
+        set (${PREFIX}_FOUND FALSE)
+      endif (${i})
+    endforeach (i)
+
+    # Print message and/or exit on fatal error
+    if (${PREFIX}_FOUND)
+      if (NOT ${PREFIX}_FIND_QUIETLY)
+        message (STATUS "Found ${PREFIX} ${${PREFIX}_VERSION}")
+      endif (NOT ${PREFIX}_FIND_QUIETLY)
+    else (${PREFIX}_FOUND)
+      if (${PREFIX}_FIND_REQUIRED)
+        foreach (i ${${PREFIX}_PROCESS_INCLUDES} ${${PREFIX}_PROCESS_LIBS})
+          message("${i}=${${i}}")
+        endforeach (i)
+        message (FATAL_ERROR "Required library ${PREFIX} NOT FOUND.\nInstall the library (dev version) and try again. If the library is already installed, use ccmake to set the missing variables manually.")
+      endif (${PREFIX}_FIND_REQUIRED)
+    endif (${PREFIX}_FOUND)
+  endif (NOT ${PREFIX}_FOUND)
+endmacro (libfind_process)
+
+macro(libfind_library PREFIX basename)
+  set(TMP "")
+  if(MSVC80)
+    set(TMP -vc80)
+  endif(MSVC80)
+  if(MSVC90)
+    set(TMP -vc90)
+  endif(MSVC90)
+  set(${PREFIX}_LIBNAMES ${basename}${TMP})
+  if(${ARGC} GREATER 2)
+    set(${PREFIX}_LIBNAMES ${basename}${TMP}-${ARGV2})
+    string(REGEX REPLACE "\\." "_" TMP ${${PREFIX}_LIBNAMES})
+    set(${PREFIX}_LIBNAMES ${${PREFIX}_LIBNAMES} ${TMP})
+  endif(${ARGC} GREATER 2)
+  find_library(${PREFIX}_LIBRARY
+    NAMES ${${PREFIX}_LIBNAMES}
+    PATHS ${${PREFIX}_PKGCONF_LIBRARY_DIRS}
+  )
+endmacro(libfind_library)
+

=== added file 'examples/mfw-plugin-dummy/cmake/ParseArguments.cmake'
--- examples/mfw-plugin-dummy/cmake/ParseArguments.cmake	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/cmake/ParseArguments.cmake	2017-03-22 21:22:50 +0000
@@ -0,0 +1,52 @@
+# Parse arguments passed to a function into several lists separated by
+# upper-case identifiers and options that do not have an associated list e.g.:
+#
+# SET(arguments
+#   hello OPTION3 world
+#   LIST3 foo bar
+#   OPTION2
+#   LIST1 fuz baz
+#   )
+# PARSE_ARGUMENTS(ARG "LIST1;LIST2;LIST3" "OPTION1;OPTION2;OPTION3" ${arguments})
+#
+# results in 7 distinct variables:
+#  * ARG_DEFAULT_ARGS: hello;world
+#  * ARG_LIST1: fuz;baz
+#  * ARG_LIST2:
+#  * ARG_LIST3: foo;bar
+#  * ARG_OPTION1: FALSE
+#  * ARG_OPTION2: TRUE
+#  * ARG_OPTION3: TRUE
+#
+# taken from http://www.cmake.org/Wiki/CMakeMacroParseArguments 
+
+MACRO(PARSE_ARGUMENTS prefix arg_names option_names)
+    SET(DEFAULT_ARGS)
+    FOREACH(arg_name ${arg_names})    
+        SET(${prefix}_${arg_name})
+    ENDFOREACH(arg_name)
+    FOREACH(option ${option_names})
+        SET(${prefix}_${option} FALSE)
+    ENDFOREACH(option)
+    
+    SET(current_arg_name DEFAULT_ARGS)
+    SET(current_arg_list)
+    FOREACH(arg ${ARGN})            
+        SET(larg_names ${arg_names})    
+        LIST(FIND larg_names "${arg}" is_arg_name)                   
+        IF (is_arg_name GREATER -1)
+            SET(${prefix}_${current_arg_name} ${current_arg_list})
+            SET(current_arg_name ${arg})
+            SET(current_arg_list)
+        ELSE (is_arg_name GREATER -1)
+            SET(loption_names ${option_names})    
+            LIST(FIND loption_names "${arg}" is_option)            
+            IF (is_option GREATER -1)
+                SET(${prefix}_${arg} TRUE)
+            ELSE (is_option GREATER -1)
+                SET(current_arg_list ${current_arg_list} ${arg})
+            ENDIF (is_option GREATER -1)
+        ENDIF (is_arg_name GREATER -1)
+    ENDFOREACH(arg)
+    SET(${prefix}_${current_arg_name} ${current_arg_list})
+ENDMACRO(PARSE_ARGUMENTS)

=== added directory 'examples/mfw-plugin-dummy/data'
=== added file 'examples/mfw-plugin-dummy/data/CMakeLists.txt'
--- examples/mfw-plugin-dummy/data/CMakeLists.txt	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/data/CMakeLists.txt	2017-03-22 21:22:50 +0000
@@ -0,0 +1,63 @@
+if (NOT IS_MF_BUILD)
+    # glob files to be shown in qt-creator
+    file(GLOB MANAGER_FILES *.manager)
+    file(GLOB SERVICE_FILES *.service)
+    file(GLOB PNG_FILES *.png)
+    add_custom_target(manager_files_plugin ALL SOURCES ${MANAGER_FILES})
+    add_custom_target(service_files_plugin ALL SOURCES ${SERVICE_FILES})
+    add_custom_target(png_files_plugin ALL SOURCES ${PNG_FILES})
+    add_custom_target(schema_files_plugin ALL SOURCES ${SCHEMA_FILES})
+    add_custom_target(info_files_plugin ALL SOURCES ${INFO_FILES})
+
+    # uninstall target
+    configure_file("${CMAKE_CURRENT_SOURCE_DIR}/cmake_uninstall.cmake.in"
+                   "${CMAKE_CURRENT_BINARY_DIR}/cmake_uninstall.cmake"
+                   IMMEDIATE @ONLY)
+    add_custom_target(uninstall "${CMAKE_COMMAND}"
+                      -P "${CMAKE_CURRENT_BINARY_DIR}/cmake_uninstall.cmake")
+
+endif()
+
+###########################################
+# Messaging-fw data and configuration files
+###########################################
+
+# Compose the pkg-config file needed to find the library using that tool
+set(PREFIX "${CMAKE_INSTALL_PREFIX}") # /usr
+set(LIBDIR "${CMAKE_INSTALL_PREFIX}/${CMAKE_INSTALL_LIBDIR}") # /usr/lib
+set(INCLUDEDIR "${CMAKE_INSTALL_PREFIX}/include") # /usr/include
+
+#############################################
+# Dummy plugin data and configuration files
+#############################################
+
+set(CM dummy)
+set(PROTOCOL dummy)
+# DUMMY_DATADIR is used in dummy.protocol.in
+set(DUMMY_DATADIR ${CMAKE_INSTALL_DATADIR}/${CM})
+
+configure_file(
+    ${CM}.service.in
+    org.freedesktop.Telepathy.ConnectionManager.${CM}.service
+)
+configure_file(
+    ${PROTOCOL}.protocol.in
+    ${PROTOCOL}.protocol)
+
+configure_file(
+    ${CM}.manager.in
+    ${CM}.manager)
+
+install(FILES ${CMAKE_CURRENT_BINARY_DIR}/org.freedesktop.Telepathy.ConnectionManager.${CM}.service
+    DESTINATION share/dbus-1/services)
+
+install(FILES ${CMAKE_CURRENT_BINARY_DIR}/${PROTOCOL}.protocol
+    DESTINATION share/telephony-service/protocols)
+
+install(FILES ${CMAKE_CURRENT_BINARY_DIR}/${CM}.manager
+    DESTINATION share/telepathy/managers)
+
+# background and protocol icons to be displayed in the UI
+install(FILES dummy-background.png dummy.png
+    DESTINATION ${DUMMY_DATADIR}/assets)
+

=== added file 'examples/mfw-plugin-dummy/data/cmake_uninstall.cmake.in'
--- examples/mfw-plugin-dummy/data/cmake_uninstall.cmake.in	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/data/cmake_uninstall.cmake.in	2017-03-22 21:22:50 +0000
@@ -0,0 +1,22 @@
+IF(NOT EXISTS "@CMAKE_BINARY_DIR@/install_manifest.txt")
+    MESSAGE(FATAL_ERROR "Cannot find install manifest: \"@CMAKE_BINARY_DIR@/install_manifest.txt\"")
+ENDIF(NOT EXISTS "@CMAKE_BINARY_DIR@/install_manifest.txt")
+
+FILE(READ "@CMAKE_BINARY_DIR@/install_manifest.txt" files)
+STRING(REGEX REPLACE "\n" ";" files "${files}")
+FOREACH(file ${files})
+    MESSAGE(STATUS "Uninstalling \"$ENV{DESTDIR}${file}\"")
+    IF(EXISTS "$ENV{DESTDIR}${file}")
+        EXEC_PROGRAM(
+            "@CMAKE_COMMAND@" ARGS "-E remove \"$ENV{DESTDIR}${file}\""
+            OUTPUT_VARIABLE rm_out
+            RETURN_VALUE rm_retval
+        )
+        IF(NOT "${rm_retval}" STREQUAL 0)
+            MESSAGE(FATAL_ERROR "Problem when removing \"$ENV{DESTDIR}${file}\"")
+        ENDIF(NOT "${rm_retval}" STREQUAL 0)
+    ELSE(EXISTS "$ENV{DESTDIR}${file}")
+        MESSAGE(STATUS "File \"$ENV{DESTDIR}${file}\" does not exist.")
+    ENDIF(EXISTS "$ENV{DESTDIR}${file}")
+ENDFOREACH(file)
+

=== added file 'examples/mfw-plugin-dummy/data/dummy-background.png'
Binary files examples/mfw-plugin-dummy/data/dummy-background.png	1970-01-01 00:00:00 +0000 and examples/mfw-plugin-dummy/data/dummy-background.png	2017-03-22 21:22:50 +0000 differ
=== added file 'examples/mfw-plugin-dummy/data/dummy.manager.in'
--- examples/mfw-plugin-dummy/data/dummy.manager.in	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/data/dummy.manager.in	2017-03-22 21:22:50 +0000
@@ -0,0 +1,10 @@
+[ConnectionManager]
+Name = @CM@
+BusName = org.freedesktop.Telepathy.ConnectionManager.@CM@
+ObjectPath = /org/freedesktop/Telepathy/ConnectionManager/@CM@
+
+[Protocol @PROTOCOL@]
+param-account=s required register
+param-password=s secret
+Interfaces=org.freedesktop.Telepathy.Protocol.Interface.Addressing;
+ConnectionInterfaces=org.freedesktop.Telepathy.Connection.Interface.Requests;org.freedesktop.Telepathy.Connection.Interface.Contacts;org.freedesktop.Telepathy.Connection.Interface.SimplePresence;

=== added file 'examples/mfw-plugin-dummy/data/dummy.png'
Binary files examples/mfw-plugin-dummy/data/dummy.png	1970-01-01 00:00:00 +0000 and examples/mfw-plugin-dummy/data/dummy.png	2017-03-22 21:22:50 +0000 differ
=== added file 'examples/mfw-plugin-dummy/data/dummy.protocol.in'
--- examples/mfw-plugin-dummy/data/dummy.protocol.in	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/data/dummy.protocol.in	2017-03-22 21:22:50 +0000
@@ -0,0 +1,16 @@
+[Protocol]
+Name=@PROTOCOL@
+Features=text
+FallbackProtocol=
+BackgroundImage=@CMAKE_INSTALL_PREFIX@/@DUMMY_DATADIR@/assets/dummy-background.png
+Icon=@CMAKE_INSTALL_PREFIX@/@DUMMY_DATADIR@/assets/dummy.png
+ServiceName=Dummy
+ServiceDisplayName=Dummy
+ShowOnSelector=1
+ShowOnlineStatus=0
+JoinExistingChannels=1
+ReturnToSend=1
+EnableAttachments=0
+EnableRejoin=1
+EnableTabCompletion=1
+LeaveRoomsOnClose=1

=== added file 'examples/mfw-plugin-dummy/data/dummy.service.in'
--- examples/mfw-plugin-dummy/data/dummy.service.in	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/data/dummy.service.in	2017-03-22 21:22:50 +0000
@@ -0,0 +1,3 @@
+[D-BUS Service]
+Name=org.freedesktop.Telepathy.ConnectionManager.@CM@
+Exec=@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_LIBDIR@/messaging-framework-runner --connection-manager-name @CM@ --protocol-name @PROTOCOL@ --connector messaging::PluginConnector --PluginConnector::path=@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_LIBDIR@/messaging-framework/libmfw-plugin-@CM@.so

=== added directory 'examples/mfw-plugin-dummy/debian'
=== added file 'examples/mfw-plugin-dummy/debian/changelog'
--- examples/mfw-plugin-dummy/debian/changelog	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/debian/changelog	2017-03-22 21:22:50 +0000
@@ -0,0 +1,5 @@
+mfw-plugin-dummy (0.1) xenial; urgency=medium
+
+  * Initial release
+
+ -- Developer Of Dummy Protocol <[e-mail]>  Mon, 05 Dec 2016 10:50:40 -0200

=== added file 'examples/mfw-plugin-dummy/debian/compat'
--- examples/mfw-plugin-dummy/debian/compat	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/debian/compat	2017-03-22 21:22:50 +0000
@@ -0,0 +1,1 @@
+9

=== added file 'examples/mfw-plugin-dummy/debian/control'
--- examples/mfw-plugin-dummy/debian/control	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/debian/control	2017-03-22 21:22:50 +0000
@@ -0,0 +1,31 @@
+Source: mfw-plugin-dummy
+Priority: optional
+Maintainer: Ubuntu Developers <[e-mail]>
+Build-Depends: cmake,
+               debhelper (>= 9),
+               doxygen,
+               gcovr,
+               google-mock,
+               lcov,
+               libboost-dev,
+               libboost-filesystem-dev,
+               libboost-program-options-dev,
+               libboost-system-dev,
+               libdbus-cpp-dev,
+               libgoogle-glog-dev,
+               libmessaging-framework-dev,
+               libprocess-cpp-dev,
+	       libtelepathy-qt5-dev,
+               pkg-config,
+               qtbase5-dev,
+	       libcppnetlib-dev,
+Standards-Version: 3.9.5
+Section: libs
+Homepage: https://launchpad.net/mfw-plugin-dummy
+Vcs-Bzr: https://code.launchpad.net/
+
+Package: mfw-plugin-dummy
+Architecture: any
+Depends: ${misc:Depends}, ${shlibs:Depends}
+Description: Ubuntu Messaging Framework Dummy Plugin
+ A plugin for messaging fw implementing Dummy protocol

=== added file 'examples/mfw-plugin-dummy/debian/copyright'
--- examples/mfw-plugin-dummy/debian/copyright	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/debian/copyright	2017-03-22 21:22:50 +0000
@@ -0,0 +1,22 @@
+Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Upstream-Name: mfw-plugin-dummy
+Source: https://launchpad.net/mfw-plugin-dummy
+
+Files: *
+Copyright: 2016 Canonical Ltd.
+License: LGPL-3.0
+ This package is free software; you can redistribute it and/or
+ modify it under the terms of the GNU Lesser General Public
+ License as published by the Free Software Foundation, version 3 of
+ the License.
+ .
+ This package is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+ Lesser General Public License for more details.
+ .
+ You should have received a copy of the GNU General Public License
+ along with this program. If not, see <http://www.gnu.org/licenses/>.
+ .
+ On Debian systems, the complete text of the GNU Lesser General
+ Public License can be found in /usr/share/common-licenses/LGPL-3.

=== added file 'examples/mfw-plugin-dummy/debian/rules'
--- examples/mfw-plugin-dummy/debian/rules	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/debian/rules	2017-03-22 21:22:50 +0000
@@ -0,0 +1,19 @@
+#!/usr/bin/make -f
+# -*- makefile -*-
+
+export DPKG_GENSYMBOLS_CHECK_LEVEL=4
+
+include /usr/share/dpkg/default.mk
+
+BUILDHOME=$(CURDIR)/debian/build
+
+%:
+	dh $@ --fail-missing
+
+override_dh_clean:
+	dh_clean
+	rm -rf $(BUILDHOME)
+
+override_dh_auto_test:
+	mkdir -p $(BUILDHOME)
+	HOME=$(BUILDHOME) dh_auto_test

=== added directory 'examples/mfw-plugin-dummy/debian/source'
=== added file 'examples/mfw-plugin-dummy/debian/source/format'
--- examples/mfw-plugin-dummy/debian/source/format	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/debian/source/format	2017-03-22 21:22:50 +0000
@@ -0,0 +1,1 @@
+3.0 (native)

=== added directory 'examples/mfw-plugin-dummy/doc'
=== added file 'examples/mfw-plugin-dummy/doc/CMakeLists.txt'
--- examples/mfw-plugin-dummy/doc/CMakeLists.txt	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/doc/CMakeLists.txt	2017-03-22 21:22:50 +0000
@@ -0,0 +1,21 @@
+option(
+  ENABLE_DOC_GENERATION
+  "Generate package documentation with doxygen"
+  OFF
+)
+
+if (ENABLE_DOC_GENERATION)
+
+find_package(Doxygen)
+
+if (DOXYGEN_FOUND)
+  configure_file(
+    ${CMAKE_CURRENT_SOURCE_DIR}/Doxyfile.in 
+    ${CMAKE_CURRENT_BINARY_DIR}/Doxyfile @ONLY)
+  add_custom_target(doc ALL
+    ${DOXYGEN_EXECUTABLE} ${CMAKE_CURRENT_BINARY_DIR}/Doxyfile
+    WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}
+    COMMENT "Generating API documentation with Doxygen" VERBATIM)
+
+endif (DOXYGEN_FOUND)
+endif (ENABLE_DOC_GENERATION)

=== added file 'examples/mfw-plugin-dummy/doc/Doxyfile.in'
--- examples/mfw-plugin-dummy/doc/Doxyfile.in	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/doc/Doxyfile.in	2017-03-22 21:22:50 +0000
@@ -0,0 +1,1869 @@
+# Doxyfile 1.8.3.1
+
+# This file describes the settings to be used by the documentation system
+# doxygen (www.doxygen.org) for a project.
+#
+# All text after a hash (#) is considered a comment and will be ignored.
+# The format is:
+#       TAG = value [value, ...]
+# For lists items can also be appended using:
+#       TAG += value [value, ...]
+# Values that contain spaces should be placed between quotes (" ").
+
+#---------------------------------------------------------------------------
+# Project related configuration options
+#---------------------------------------------------------------------------
+
+# This tag specifies the encoding used for all characters in the config file
+# that follow. The default is UTF-8 which is also the encoding used for all
+# text before the first occurrence of this tag. Doxygen uses libiconv (or the
+# iconv built into libc) for the transcoding. See
+# http://www.gnu.org/software/libiconv for the list of possible encodings.
+
+DOXYFILE_ENCODING      = UTF-8
+
+# The PROJECT_NAME tag is a single word (or sequence of words) that should
+# identify the project. Note that if you do not use Doxywizard you need
+# to put quotes around the project name if it contains spaces.
+
+PROJECT_NAME           = @CMAKE_PROJECT_NAME@
+
+# The PROJECT_NUMBER tag can be used to enter a project or revision number.
+# This could be handy for archiving the generated documentation or
+# if some version control system is used.
+
+PROJECT_NUMBER         = @SO_VERSION_MAJOR@.@SO_VERSION_MINOR@.@SO_VERSION_PATCH@
+
+# Using the PROJECT_BRIEF tag one can provide an optional one line description
+# for a project that appears at the top of each page and should give viewer
+# a quick idea about the purpose of the project. Keep the description short.
+
+PROJECT_BRIEF          = "Messaging framework backend enabling Dummy Protocol on Ubuntu phones"
+
+# With the PROJECT_LOGO tag one can specify an logo or icon that is
+# included in the documentation. The maximum height of the logo should not
+# exceed 55 pixels and the maximum width should not exceed 200 pixels.
+# Doxygen will copy the logo to the output directory.
+
+PROJECT_LOGO           =
+
+# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
+# base path where the generated documentation will be put.
+# If a relative path is entered, it will be relative to the location
+# where doxygen was started. If left blank the current directory will be used.
+
+OUTPUT_DIRECTORY       =
+
+# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
+# 4096 sub-directories (in 2 levels) under the output directory of each output
+# format and will distribute the generated files over these directories.
+# Enabling this option can be useful when feeding doxygen a huge amount of
+# source files, where putting all generated files in the same directory would
+# otherwise cause performance problems for the file system.
+
+CREATE_SUBDIRS         = NO
+
+# The OUTPUT_LANGUAGE tag is used to specify the language in which all
+# documentation generated by doxygen is written. Doxygen will use this
+# information to generate all constant output in the proper language.
+# The default language is English, other supported languages are:
+# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional,
+# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German,
+# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English
+# messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian,
+# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak,
+# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese.
+
+OUTPUT_LANGUAGE        = English
+
+# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
+# include brief member descriptions after the members that are listed in
+# the file and class documentation (similar to JavaDoc).
+# Set to NO to disable this.
+
+BRIEF_MEMBER_DESC      = YES
+
+# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
+# the brief description of a member or function before the detailed description.
+# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
+# brief descriptions will be completely suppressed.
+
+REPEAT_BRIEF           = YES
+
+# This tag implements a quasi-intelligent brief description abbreviator
+# that is used to form the text in various listings. Each string
+# in this list, if found as the leading text of the brief description, will be
+# stripped from the text and the result after processing the whole list, is
+# used as the annotated text. Otherwise, the brief description is used as-is.
+# If left blank, the following values are used ("$name" is automatically
+# replaced with the name of the entity): "The $name class" "The $name widget"
+# "The $name file" "is" "provides" "specifies" "contains"
+# "represents" "a" "an" "the"
+
+ABBREVIATE_BRIEF       =
+
+# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
+# Doxygen will generate a detailed section even if there is only a brief
+# description.
+
+ALWAYS_DETAILED_SEC    = NO
+
+# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
+# inherited members of a class in the documentation of that class as if those
+# members were ordinary class members. Constructors, destructors and assignment
+# operators of the base classes will not be shown.
+
+INLINE_INHERITED_MEMB  = NO
+
+# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
+# path before files name in the file list and in the header files. If set
+# to NO the shortest path that makes the file name unique will be used.
+
+FULL_PATH_NAMES        = YES
+
+# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
+# can be used to strip a user-defined part of the path. Stripping is
+# only done if one of the specified strings matches the left-hand part of
+# the path. The tag can be used to show relative paths in the file list.
+# If left blank the directory from which doxygen is run is used as the
+# path to strip. Note that you specify absolute paths here, but also
+# relative paths, which will be relative from the directory where doxygen is
+# started.
+
+STRIP_FROM_PATH        =
+
+# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
+# the path mentioned in the documentation of a class, which tells
+# the reader which header file to include in order to use a class.
+# If left blank only the name of the header file containing the class
+# definition is used. Otherwise one should specify the include paths that
+# are normally passed to the compiler using the -I flag.
+
+STRIP_FROM_INC_PATH    =
+
+# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
+# (but less readable) file names. This can be useful if your file system
+# doesn't support long names like on DOS, Mac, or CD-ROM.
+
+SHORT_NAMES            = NO
+
+# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
+# will interpret the first line (until the first dot) of a JavaDoc-style
+# comment as the brief description. If set to NO, the JavaDoc
+# comments will behave just like regular Qt-style comments
+# (thus requiring an explicit @brief command for a brief description.)
+
+JAVADOC_AUTOBRIEF      = NO
+
+# If the QT_AUTOBRIEF tag is set to YES then Doxygen will
+# interpret the first line (until the first dot) of a Qt-style
+# comment as the brief description. If set to NO, the comments
+# will behave just like regular Qt-style comments (thus requiring
+# an explicit \brief command for a brief description.)
+
+QT_AUTOBRIEF           = NO
+
+# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
+# treat a multi-line C++ special comment block (i.e. a block of //! or ///
+# comments) as a brief description. This used to be the default behaviour.
+# The new default is to treat a multi-line C++ comment block as a detailed
+# description. Set this tag to YES if you prefer the old behaviour instead.
+
+MULTILINE_CPP_IS_BRIEF = NO
+
+# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
+# member inherits the documentation from any documented member that it
+# re-implements.
+
+INHERIT_DOCS           = YES
+
+# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce
+# a new page for each member. If set to NO, the documentation of a member will
+# be part of the file/class/namespace that contains it.
+
+SEPARATE_MEMBER_PAGES  = NO
+
+# The TAB_SIZE tag can be used to set the number of spaces in a tab.
+# Doxygen uses this value to replace tabs by spaces in code fragments.
+
+TAB_SIZE               = 4
+
+# This tag can be used to specify a number of aliases that acts
+# as commands in the documentation. An alias has the form "name=value".
+# For example adding "sideeffect=\par Side Effects:\n" will allow you to
+# put the command \sideeffect (or @sideeffect) in the documentation, which
+# will result in a user-defined paragraph with heading "Side Effects:".
+# You can put \n's in the value part of an alias to insert newlines.
+
+ALIASES                =
+
+# This tag can be used to specify a number of word-keyword mappings (TCL only).
+# A mapping has the form "name=value". For example adding
+# "class=itcl::class" will allow you to use the command class in the
+# itcl::class meaning.
+
+TCL_SUBST              =
+
+# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
+# sources only. Doxygen will then generate output that is more tailored for C.
+# For instance, some of the names that are used will be different. The list
+# of all members will be omitted, etc.
+
+OPTIMIZE_OUTPUT_FOR_C  = NO
+
+# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java
+# sources only. Doxygen will then generate output that is more tailored for
+# Java. For instance, namespaces will be presented as packages, qualified
+# scopes will look different, etc.
+
+OPTIMIZE_OUTPUT_JAVA   = NO
+
+# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
+# sources only. Doxygen will then generate output that is more tailored for
+# Fortran.
+
+OPTIMIZE_FOR_FORTRAN   = NO
+
+# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
+# sources. Doxygen will then generate output that is tailored for
+# VHDL.
+
+OPTIMIZE_OUTPUT_VHDL   = NO
+
+# Doxygen selects the parser to use depending on the extension of the files it
+# parses. With this tag you can assign which parser to use for a given
+# extension. Doxygen has a built-in mapping, but you can override or extend it
+# using this tag. The format is ext=language, where ext is a file extension,
+# and language is one of the parsers supported by doxygen: IDL, Java,
+# Javascript, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C,
+# C++. For instance to make doxygen treat .inc files as Fortran files (default
+# is PHP), and .f files as C (default is Fortran), use: inc=Fortran f=C. Note
+# that for custom extensions you also need to set FILE_PATTERNS otherwise the
+# files are not read by doxygen.
+
+EXTENSION_MAPPING      =
+
+# If MARKDOWN_SUPPORT is enabled (the default) then doxygen pre-processes all
+# comments according to the Markdown format, which allows for more readable
+# documentation. See http://daringfireball.net/projects/markdown/ for details.
+# The output of markdown processing is further processed by doxygen, so you
+# can mix doxygen, HTML, and XML commands with Markdown formatting.
+# Disable only in case of backward compatibilities issues.
+
+MARKDOWN_SUPPORT       = YES
+
+# When enabled doxygen tries to link words that correspond to documented classes,
+# or namespaces to their corresponding documentation. Such a link can be
+# prevented in individual cases by by putting a % sign in front of the word or
+# globally by setting AUTOLINK_SUPPORT to NO.
+
+AUTOLINK_SUPPORT       = YES
+
+# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
+# to include (a tag file for) the STL sources as input, then you should
+# set this tag to YES in order to let doxygen match functions declarations and
+# definitions whose arguments contain STL classes (e.g. func(std::string); v.s.
+# func(std::string) {}). This also makes the inheritance and collaboration
+# diagrams that involve STL classes more complete and accurate.
+
+BUILTIN_STL_SUPPORT    = YES
+
+# If you use Microsoft's C++/CLI language, you should set this option to YES to
+# enable parsing support.
+
+CPP_CLI_SUPPORT        = NO
+
+# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only.
+# Doxygen will parse them like normal C++ but will assume all classes use public
+# instead of private inheritance when no explicit protection keyword is present.
+
+SIP_SUPPORT            = NO
+
+# For Microsoft's IDL there are propget and propput attributes to indicate
+# getter and setter methods for a property. Setting this option to YES (the
+# default) will make doxygen replace the get and set methods by a property in
+# the documentation. This will only work if the methods are indeed getting or
+# setting a simple type. If this is not the case, or you want to show the
+# methods anyway, you should set this option to NO.
+
+IDL_PROPERTY_SUPPORT   = YES
+
+# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
+# tag is set to YES, then doxygen will reuse the documentation of the first
+# member in the group (if any) for the other members of the group. By default
+# all members of a group must be documented explicitly.
+
+DISTRIBUTE_GROUP_DOC   = NO
+
+# Set the SUBGROUPING tag to YES (the default) to allow class member groups of
+# the same type (for instance a group of public functions) to be put as a
+# subgroup of that type (e.g. under the Public Functions section). Set it to
+# NO to prevent subgrouping. Alternatively, this can be done per class using
+# the \nosubgrouping command.
+
+SUBGROUPING            = YES
+
+# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and
+# unions are shown inside the group in which they are included (e.g. using
+# @ingroup) instead of on a separate page (for HTML and Man pages) or
+# section (for LaTeX and RTF).
+
+INLINE_GROUPED_CLASSES = NO
+
+# When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and
+# unions with only public data fields will be shown inline in the documentation
+# of the scope in which they are defined (i.e. file, namespace, or group
+# documentation), provided this scope is documented. If set to NO (the default),
+# structs, classes, and unions are shown on a separate page (for HTML and Man
+# pages) or section (for LaTeX and RTF).
+
+INLINE_SIMPLE_STRUCTS  = NO
+
+# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum
+# is documented as struct, union, or enum with the name of the typedef. So
+# typedef struct TypeS {} TypeT, will appear in the documentation as a struct
+# with name TypeT. When disabled the typedef will appear as a member of a file,
+# namespace, or class. And the struct will be named TypeS. This can typically
+# be useful for C code in case the coding convention dictates that all compound
+# types are typedef'ed and only the typedef is referenced, never the tag name.
+
+TYPEDEF_HIDES_STRUCT   = NO
+
+# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to
+# determine which symbols to keep in memory and which to flush to disk.
+# When the cache is full, less often used symbols will be written to disk.
+# For small to medium size projects (<1000 input files) the default value is
+# probably good enough. For larger projects a too small cache size can cause
+# doxygen to be busy swapping symbols to and from disk most of the time
+# causing a significant performance penalty.
+# If the system has enough physical memory increasing the cache will improve the
+# performance by keeping more symbols in memory. Note that the value works on
+# a logarithmic scale so increasing the size by one will roughly double the
+# memory usage. The cache size is given by this formula:
+# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0,
+# corresponding to a cache size of 2^16 = 65536 symbols.
+
+SYMBOL_CACHE_SIZE      = 0
+
+# Similar to the SYMBOL_CACHE_SIZE the size of the symbol lookup cache can be
+# set using LOOKUP_CACHE_SIZE. This cache is used to resolve symbols given
+# their name and scope. Since this can be an expensive process and often the
+# same symbol appear multiple times in the code, doxygen keeps a cache of
+# pre-resolved symbols. If the cache is too small doxygen will become slower.
+# If the cache is too large, memory is wasted. The cache size is given by this
+# formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range is 0..9, the default is 0,
+# corresponding to a cache size of 2^16 = 65536 symbols.
+
+LOOKUP_CACHE_SIZE      = 0
+
+#---------------------------------------------------------------------------
+# Build related configuration options
+#---------------------------------------------------------------------------
+
+# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
+# documentation are documented, even if no documentation was available.
+# Private class members and static file members will be hidden unless
+# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
+
+EXTRACT_ALL            = YES
+
+# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
+# will be included in the documentation.
+
+EXTRACT_PRIVATE        = NO
+
+# If the EXTRACT_PACKAGE tag is set to YES all members with package or internal
+# scope will be included in the documentation.
+
+EXTRACT_PACKAGE        = NO
+
+# If the EXTRACT_STATIC tag is set to YES all static members of a file
+# will be included in the documentation.
+
+EXTRACT_STATIC         = NO
+
+# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
+# defined locally in source files will be included in the documentation.
+# If set to NO only classes defined in header files are included.
+
+EXTRACT_LOCAL_CLASSES  = YES
+
+# This flag is only useful for Objective-C code. When set to YES local
+# methods, which are defined in the implementation section but not in
+# the interface are included in the documentation.
+# If set to NO (the default) only methods in the interface are included.
+
+EXTRACT_LOCAL_METHODS  = NO
+
+# If this flag is set to YES, the members of anonymous namespaces will be
+# extracted and appear in the documentation as a namespace called
+# 'anonymous_namespace{file}', where file will be replaced with the base
+# name of the file that contains the anonymous namespace. By default
+# anonymous namespaces are hidden.
+
+EXTRACT_ANON_NSPACES   = NO
+
+# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
+# undocumented members of documented classes, files or namespaces.
+# If set to NO (the default) these members will be included in the
+# various overviews, but no documentation section is generated.
+# This option has no effect if EXTRACT_ALL is enabled.
+
+HIDE_UNDOC_MEMBERS     = NO
+
+# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
+# undocumented classes that are normally visible in the class hierarchy.
+# If set to NO (the default) these classes will be included in the various
+# overviews. This option has no effect if EXTRACT_ALL is enabled.
+
+HIDE_UNDOC_CLASSES     = NO
+
+# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
+# friend (class|struct|union) declarations.
+# If set to NO (the default) these declarations will be included in the
+# documentation.
+
+HIDE_FRIEND_COMPOUNDS  = NO
+
+# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
+# documentation blocks found inside the body of a function.
+# If set to NO (the default) these blocks will be appended to the
+# function's detailed documentation block.
+
+HIDE_IN_BODY_DOCS      = NO
+
+# The INTERNAL_DOCS tag determines if documentation
+# that is typed after a \internal command is included. If the tag is set
+# to NO (the default) then the documentation will be excluded.
+# Set it to YES to include the internal documentation.
+
+INTERNAL_DOCS          = NO
+
+# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
+# file names in lower-case letters. If set to YES upper-case letters are also
+# allowed. This is useful if you have classes or files whose names only differ
+# in case and if your file system supports case sensitive file names. Windows
+# and Mac users are advised to set this option to NO.
+
+CASE_SENSE_NAMES       = YES
+
+# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
+# will show members with their full class and namespace scopes in the
+# documentation. If set to YES the scope will be hidden.
+
+HIDE_SCOPE_NAMES       = NO
+
+# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
+# will put a list of the files that are included by a file in the documentation
+# of that file.
+
+SHOW_INCLUDE_FILES     = YES
+
+# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen
+# will list include files with double quotes in the documentation
+# rather than with sharp brackets.
+
+FORCE_LOCAL_INCLUDES   = NO
+
+# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
+# is inserted in the documentation for inline members.
+
+INLINE_INFO            = YES
+
+# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
+# will sort the (detailed) documentation of file and class members
+# alphabetically by member name. If set to NO the members will appear in
+# declaration order.
+
+SORT_MEMBER_DOCS       = YES
+
+# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
+# brief documentation of file, namespace and class members alphabetically
+# by member name. If set to NO (the default) the members will appear in
+# declaration order.
+
+SORT_BRIEF_DOCS        = NO
+
+# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen
+# will sort the (brief and detailed) documentation of class members so that
+# constructors and destructors are listed first. If set to NO (the default)
+# the constructors will appear in the respective orders defined by
+# SORT_MEMBER_DOCS and SORT_BRIEF_DOCS.
+# This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO
+# and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.
+
+SORT_MEMBERS_CTORS_1ST = NO
+
+# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the
+# hierarchy of group names into alphabetical order. If set to NO (the default)
+# the group names will appear in their defined order.
+
+SORT_GROUP_NAMES       = NO
+
+# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
+# sorted by fully-qualified names, including namespaces. If set to
+# NO (the default), the class list will be sorted only by class name,
+# not including the namespace part.
+# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
+# Note: This option applies only to the class list, not to the
+# alphabetical list.
+
+SORT_BY_SCOPE_NAME     = NO
+
+# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to
+# do proper type resolution of all parameters of a function it will reject a
+# match between the prototype and the implementation of a member function even
+# if there is only one candidate or it is obvious which candidate to choose
+# by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen
+# will still accept a match between prototype and implementation in such cases.
+
+STRICT_PROTO_MATCHING  = NO
+
+# The GENERATE_TODOLIST tag can be used to enable (YES) or
+# disable (NO) the todo list. This list is created by putting \todo
+# commands in the documentation.
+
+GENERATE_TODOLIST      = YES
+
+# The GENERATE_TESTLIST tag can be used to enable (YES) or
+# disable (NO) the test list. This list is created by putting \test
+# commands in the documentation.
+
+GENERATE_TESTLIST      = YES
+
+# The GENERATE_BUGLIST tag can be used to enable (YES) or
+# disable (NO) the bug list. This list is created by putting \bug
+# commands in the documentation.
+
+GENERATE_BUGLIST       = YES
+
+# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
+# disable (NO) the deprecated list. This list is created by putting
+# \deprecated commands in the documentation.
+
+GENERATE_DEPRECATEDLIST= YES
+
+# The ENABLED_SECTIONS tag can be used to enable conditional
+# documentation sections, marked by \if section-label ... \endif
+# and \cond section-label ... \endcond blocks.
+
+ENABLED_SECTIONS       =
+
+# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
+# the initial value of a variable or macro consists of for it to appear in
+# the documentation. If the initializer consists of more lines than specified
+# here it will be hidden. Use a value of 0 to hide initializers completely.
+# The appearance of the initializer of individual variables and macros in the
+# documentation can be controlled using \showinitializer or \hideinitializer
+# command in the documentation regardless of this setting.
+
+MAX_INITIALIZER_LINES  = 30
+
+# Set the SHOW_USED_FILES tag to NO to disable the list of files generated
+# at the bottom of the documentation of classes and structs. If set to YES the
+# list will mention the files that were used to generate the documentation.
+
+SHOW_USED_FILES        = YES
+
+# Set the SHOW_FILES tag to NO to disable the generation of the Files page.
+# This will remove the Files entry from the Quick Index and from the
+# Folder Tree View (if specified). The default is YES.
+
+SHOW_FILES             = YES
+
+# Set the SHOW_NAMESPACES tag to NO to disable the generation of the
+# Namespaces page.
+# This will remove the Namespaces entry from the Quick Index
+# and from the Folder Tree View (if specified). The default is YES.
+
+SHOW_NAMESPACES        = YES
+
+# The FILE_VERSION_FILTER tag can be used to specify a program or script that
+# doxygen should invoke to get the current version for each file (typically from
+# the version control system). Doxygen will invoke the program by executing (via
+# popen()) the command <command> <input-file>, where <command> is the value of
+# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
+# provided by doxygen. Whatever the program writes to standard output
+# is used as the file version. See the manual for examples.
+
+FILE_VERSION_FILTER    =
+
+# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
+# by doxygen. The layout file controls the global structure of the generated
+# output files in an output format independent way. To create the layout file
+# that represents doxygen's defaults, run doxygen with the -l option.
+# You can optionally specify a file name after the option, if omitted
+# DoxygenLayout.xml will be used as the name of the layout file.
+
+LAYOUT_FILE            =
+
+# The CITE_BIB_FILES tag can be used to specify one or more bib files
+# containing the references data. This must be a list of .bib files. The
+# .bib extension is automatically appended if omitted. Using this command
+# requires the bibtex tool to be installed. See also
+# http://en.wikipedia.org/wiki/BibTeX for more info. For LaTeX the style
+# of the bibliography can be controlled using LATEX_BIB_STYLE. To use this
+# feature you need bibtex and perl available in the search path. Do not use
+# file names with spaces, bibtex cannot handle them.
+
+CITE_BIB_FILES         =
+
+#---------------------------------------------------------------------------
+# configuration options related to warning and progress messages
+#---------------------------------------------------------------------------
+
+# The QUIET tag can be used to turn on/off the messages that are generated
+# by doxygen. Possible values are YES and NO. If left blank NO is used.
+
+QUIET                  = NO
+
+# The WARNINGS tag can be used to turn on/off the warning messages that are
+# generated by doxygen. Possible values are YES and NO. If left blank
+# NO is used.
+
+WARNINGS               = YES
+
+# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
+# for undocumented members. If EXTRACT_ALL is set to YES then this flag will
+# automatically be disabled.
+
+WARN_IF_UNDOCUMENTED   = YES
+
+# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
+# potential errors in the documentation, such as not documenting some
+# parameters in a documented function, or documenting parameters that
+# don't exist or using markup commands wrongly.
+
+WARN_IF_DOC_ERROR      = YES
+
+# The WARN_NO_PARAMDOC option can be enabled to get warnings for
+# functions that are documented, but have no documentation for their parameters
+# or return value. If set to NO (the default) doxygen will only warn about
+# wrong or incomplete parameter documentation, but not about the absence of
+# documentation.
+
+WARN_NO_PARAMDOC       = NO
+
+# The WARN_FORMAT tag determines the format of the warning messages that
+# doxygen can produce. The string should contain the $file, $line, and $text
+# tags, which will be replaced by the file and line number from which the
+# warning originated and the warning text. Optionally the format may contain
+# $version, which will be replaced by the version of the file (if it could
+# be obtained via FILE_VERSION_FILTER)
+
+WARN_FORMAT            = "$file:$line: $text"
+
+# The WARN_LOGFILE tag can be used to specify a file to which warning
+# and error messages should be written. If left blank the output is written
+# to stderr.
+
+WARN_LOGFILE           =
+
+#---------------------------------------------------------------------------
+# configuration options related to the input files
+#---------------------------------------------------------------------------
+
+# The INPUT tag can be used to specify the files and/or directories that contain
+# documented source files. You may enter file names like "myfile.cpp" or
+# directories like "/usr/src/myproject". Separate the files or directories
+# with spaces.
+
+INPUT                  = @CMAKE_SOURCE_DIR@/include @CMAKE_SOURCE_DIR@/doc
+
+# This tag can be used to specify the character encoding of the source files
+# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is
+# also the default input encoding. Doxygen uses libiconv (or the iconv built
+# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for
+# the list of possible encodings.
+
+INPUT_ENCODING         = UTF-8
+
+# If the value of the INPUT tag contains directories, you can use the
+# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
+# and *.h) to filter out the source-files in the directories. If left
+# blank the following patterns are tested:
+# *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh
+# *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py
+# *.f90 *.f *.for *.vhd *.vhdl
+
+FILE_PATTERNS          =
+
+# The RECURSIVE tag can be used to turn specify whether or not subdirectories
+# should be searched for input files as well. Possible values are YES and NO.
+# If left blank NO is used.
+
+RECURSIVE              = YES
+
+# The EXCLUDE tag can be used to specify files and/or directories that should be
+# excluded from the INPUT source files. This way you can easily exclude a
+# subdirectory from a directory tree whose root is specified with the INPUT tag.
+# Note that relative paths are relative to the directory from which doxygen is
+# run.
+
+EXCLUDE                =
+
+# The EXCLUDE_SYMLINKS tag can be used to select whether or not files or
+# directories that are symbolic links (a Unix file system feature) are excluded
+# from the input.
+
+EXCLUDE_SYMLINKS       = NO
+
+# If the value of the INPUT tag contains directories, you can use the
+# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
+# certain files from those directories. Note that the wildcards are matched
+# against the file with absolute path, so to exclude all test directories
+# for example use the pattern */test/*
+
+EXCLUDE_PATTERNS       =
+
+# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
+# (namespaces, classes, functions, etc.) that should be excluded from the
+# output. The symbol name can be a fully qualified name, a word, or if the
+# wildcard * is used, a substring. Examples: ANamespace, AClass,
+# AClass::ANamespace, ANamespace::*Test
+
+EXCLUDE_SYMBOLS        =
+
+# The EXAMPLE_PATH tag can be used to specify one or more files or
+# directories that contain example code fragments that are included (see
+# the \include command).
+
+EXAMPLE_PATH           = @CMAKE_CURRENT_SOURCE_DIR@/../tests
+
+# If the value of the EXAMPLE_PATH tag contains directories, you can use the
+# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
+# and *.h) to filter out the source-files in the directories. If left
+# blank all files are included.
+
+EXAMPLE_PATTERNS       =
+
+# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
+# searched for input files to be used with the \include or \dontinclude
+# commands irrespective of the value of the RECURSIVE tag.
+# Possible values are YES and NO. If left blank NO is used.
+
+EXAMPLE_RECURSIVE      = YES
+
+# The IMAGE_PATH tag can be used to specify one or more files or
+# directories that contain image that are included in the documentation (see
+# the \image command).
+
+IMAGE_PATH             =
+
+# The INPUT_FILTER tag can be used to specify a program that doxygen should
+# invoke to filter for each input file. Doxygen will invoke the filter program
+# by executing (via popen()) the command <filter> <input-file>, where <filter>
+# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
+# input file. Doxygen will then use the output that the filter program writes
+# to standard output.
+# If FILTER_PATTERNS is specified, this tag will be
+# ignored.
+
+INPUT_FILTER           =
+
+# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
+# basis.
+# Doxygen will compare the file name with each pattern and apply the
+# filter if there is a match.
+# The filters are a list of the form:
+# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
+# info on how filters are used. If FILTER_PATTERNS is empty or if
+# non of the patterns match the file name, INPUT_FILTER is applied.
+
+FILTER_PATTERNS        =
+
+# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
+# INPUT_FILTER) will be used to filter the input files when producing source
+# files to browse (i.e. when SOURCE_BROWSER is set to YES).
+
+FILTER_SOURCE_FILES    = NO
+
+# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file
+# pattern. A pattern will override the setting for FILTER_PATTERN (if any)
+# and it is also possible to disable source filtering for a specific pattern
+# using *.ext= (so without naming a filter). This option only has effect when
+# FILTER_SOURCE_FILES is enabled.
+
+FILTER_SOURCE_PATTERNS =
+
+# If the USE_MD_FILE_AS_MAINPAGE tag refers to the name of a markdown file that
+# is part of the input, its contents will be placed on the main page (index.html).
+# This can be useful if you have a project on for instance GitHub and want reuse
+# the introduction page also for the doxygen output.
+
+USE_MDFILE_AS_MAINPAGE = @CMAKE_SOURCE_DIR@/README.md
+
+#---------------------------------------------------------------------------
+# configuration options related to source browsing
+#---------------------------------------------------------------------------
+
+# If the SOURCE_BROWSER tag is set to YES then a list of source files will
+# be generated. Documented entities will be cross-referenced with these sources.
+# Note: To get rid of all source code in the generated output, make sure also
+# VERBATIM_HEADERS is set to NO.
+
+SOURCE_BROWSER         = YES
+
+# Setting the INLINE_SOURCES tag to YES will include the body
+# of functions and classes directly in the documentation.
+
+INLINE_SOURCES         = NO
+
+# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
+# doxygen to hide any special comment blocks from generated source code
+# fragments. Normal C, C++ and Fortran comments will always remain visible.
+
+STRIP_CODE_COMMENTS    = YES
+
+# If the REFERENCED_BY_RELATION tag is set to YES
+# then for each documented function all documented
+# functions referencing it will be listed.
+
+REFERENCED_BY_RELATION = YES
+
+# If the REFERENCES_RELATION tag is set to YES
+# then for each documented function all documented entities
+# called/used by that function will be listed.
+
+REFERENCES_RELATION    = YES
+
+# If the REFERENCES_LINK_SOURCE tag is set to YES (the default)
+# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from
+# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will
+# link to the source code.
+# Otherwise they will link to the documentation.
+
+REFERENCES_LINK_SOURCE = YES
+
+# If the USE_HTAGS tag is set to YES then the references to source code
+# will point to the HTML generated by the htags(1) tool instead of doxygen
+# built-in source browser. The htags tool is part of GNU's global source
+# tagging system (see http://www.gnu.org/software/global/global.html). You
+# will need version 4.8.6 or higher.
+
+USE_HTAGS              = NO
+
+# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
+# will generate a verbatim copy of the header file for each class for
+# which an include is specified. Set to NO to disable this.
+
+VERBATIM_HEADERS       = YES
+
+#---------------------------------------------------------------------------
+# configuration options related to the alphabetical class index
+#---------------------------------------------------------------------------
+
+# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
+# of all compounds will be generated. Enable this if the project
+# contains a lot of classes, structs, unions or interfaces.
+
+ALPHABETICAL_INDEX     = YES
+
+# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
+# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
+# in which this list will be split (can be a number in the range [1..20])
+
+COLS_IN_ALPHA_INDEX    = 5
+
+# In case all classes in a project start with a common prefix, all
+# classes will be put under the same header in the alphabetical index.
+# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
+# should be ignored while generating the index headers.
+
+IGNORE_PREFIX          =
+
+#---------------------------------------------------------------------------
+# configuration options related to the HTML output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
+# generate HTML output.
+
+GENERATE_HTML          = YES
+
+# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be
+# put in front of it. If left blank `html' will be used as the default path.
+
+HTML_OUTPUT            = html
+
+# The HTML_FILE_EXTENSION tag can be used to specify the file extension for
+# each generated HTML page (for example: .htm,.php,.asp). If it is left blank
+# doxygen will generate files with .html extension.
+
+HTML_FILE_EXTENSION    = .html
+
+# The HTML_HEADER tag can be used to specify a personal HTML header for
+# each generated HTML page. If it is left blank doxygen will generate a
+# standard header. Note that when using a custom header you are responsible
+#  for the proper inclusion of any scripts and style sheets that doxygen
+# needs, which is dependent on the configuration options used.
+# It is advised to generate a default header using "doxygen -w html
+# header.html footer.html stylesheet.css YourConfigFile" and then modify
+# that header. Note that the header is subject to change so you typically
+# have to redo this when upgrading to a newer version of doxygen or when
+# changing the value of configuration settings such as GENERATE_TREEVIEW!
+
+HTML_HEADER            =
+
+# The HTML_FOOTER tag can be used to specify a personal HTML footer for
+# each generated HTML page. If it is left blank doxygen will generate a
+# standard footer.
+
+HTML_FOOTER            =
+
+# The HTML_STYLESHEET tag can be used to specify a user-defined cascading
+# style sheet that is used by each HTML page. It can be used to
+# fine-tune the look of the HTML output. If left blank doxygen will
+# generate a default style sheet. Note that it is recommended to use
+# HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this
+# tag will in the future become obsolete.
+
+HTML_STYLESHEET        =
+
+# The HTML_EXTRA_STYLESHEET tag can be used to specify an additional
+# user-defined cascading style sheet that is included after the standard
+# style sheets created by doxygen. Using this option one can overrule
+# certain style aspects. This is preferred over using HTML_STYLESHEET
+# since it does not replace the standard style sheet and is therefor more
+# robust against future updates. Doxygen will copy the style sheet file to
+# the output directory.
+
+HTML_EXTRA_STYLESHEET  = @CMAKE_CURRENT_SOURCE_DIR@/extra.css
+
+# The HTML_EXTRA_FILES tag can be used to specify one or more extra images or
+# other source files which should be copied to the HTML output directory. Note
+# that these files will be copied to the base HTML output directory. Use the
+# $relpath$ marker in the HTML_HEADER and/or HTML_FOOTER files to load these
+# files. In the HTML_STYLESHEET file, use the file name only. Also note that
+# the files will be copied as-is; there are no commands or markers available.
+
+HTML_EXTRA_FILES       =
+
+# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output.
+# Doxygen will adjust the colors in the style sheet and background images
+# according to this color. Hue is specified as an angle on a colorwheel,
+# see http://en.wikipedia.org/wiki/Hue for more information.
+# For instance the value 0 represents red, 60 is yellow, 120 is green,
+# 180 is cyan, 240 is blue, 300 purple, and 360 is red again.
+# The allowed range is 0 to 359.
+
+HTML_COLORSTYLE_HUE    = 220
+
+# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of
+# the colors in the HTML output. For a value of 0 the output will use
+# grayscales only. A value of 255 will produce the most vivid colors.
+
+HTML_COLORSTYLE_SAT    = 100
+
+# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to
+# the luminance component of the colors in the HTML output. Values below
+# 100 gradually make the output lighter, whereas values above 100 make
+# the output darker. The value divided by 100 is the actual gamma applied,
+# so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2,
+# and 100 does not change the gamma.
+
+HTML_COLORSTYLE_GAMMA  = 80
+
+# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
+# page will contain the date and time when the page was generated. Setting
+# this to NO can help when comparing the output of multiple runs.
+
+HTML_TIMESTAMP         = YES
+
+# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
+# documentation will contain sections that can be hidden and shown after the
+# page has loaded.
+
+HTML_DYNAMIC_SECTIONS  = YES
+
+# With HTML_INDEX_NUM_ENTRIES one can control the preferred number of
+# entries shown in the various tree structured indices initially; the user
+# can expand and collapse entries dynamically later on. Doxygen will expand
+# the tree to such a level that at most the specified number of entries are
+# visible (unless a fully collapsed tree already exceeds this amount).
+# So setting the number of entries 1 will produce a full collapsed tree by
+# default. 0 is a special value representing an infinite number of entries
+# and will result in a full expanded tree by default.
+
+HTML_INDEX_NUM_ENTRIES = 100
+
+# If the GENERATE_DOCSET tag is set to YES, additional index files
+# will be generated that can be used as input for Apple's Xcode 3
+# integrated development environment, introduced with OSX 10.5 (Leopard).
+# To create a documentation set, doxygen will generate a Makefile in the
+# HTML output directory. Running make will produce the docset in that
+# directory and running "make install" will install the docset in
+# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
+# it at startup.
+# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
+# for more information.
+
+GENERATE_DOCSET        = NO
+
+# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the
+# feed. A documentation feed provides an umbrella under which multiple
+# documentation sets from a single provider (such as a company or product suite)
+# can be grouped.
+
+DOCSET_FEEDNAME        = "Doxygen generated docs"
+
+# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that
+# should uniquely identify the documentation set bundle. This should be a
+# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen
+# will append .docset to the name.
+
+DOCSET_BUNDLE_ID       = org.doxygen.Project
+
+# When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely
+# identify the documentation publisher. This should be a reverse domain-name
+# style string, e.g. com.mycompany.MyDocSet.documentation.
+
+DOCSET_PUBLISHER_ID    = org.doxygen.Publisher
+
+# The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.
+
+DOCSET_PUBLISHER_NAME  = Publisher
+
+# If the GENERATE_HTMLHELP tag is set to YES, additional index files
+# will be generated that can be used as input for tools like the
+# Microsoft HTML help workshop to generate a compiled HTML help file (.chm)
+# of the generated HTML documentation.
+
+GENERATE_HTMLHELP      = NO
+
+# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
+# be used to specify the file name of the resulting .chm file. You
+# can add a path in front of the file if the result should not be
+# written to the html output directory.
+
+CHM_FILE               =
+
+# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
+# be used to specify the location (absolute path including file name) of
+# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
+# the HTML help compiler on the generated index.hhp.
+
+HHC_LOCATION           =
+
+# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
+# controls if a separate .chi index file is generated (YES) or that
+# it should be included in the master .chm file (NO).
+
+GENERATE_CHI           = NO
+
+# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING
+# is used to encode HtmlHelp index (hhk), content (hhc) and project file
+# content.
+
+CHM_INDEX_ENCODING     =
+
+# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
+# controls whether a binary table of contents is generated (YES) or a
+# normal table of contents (NO) in the .chm file.
+
+BINARY_TOC             = NO
+
+# The TOC_EXPAND flag can be set to YES to add extra items for group members
+# to the contents of the HTML help documentation and to the tree view.
+
+TOC_EXPAND             = NO
+
+# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and
+# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated
+# that can be used as input for Qt's qhelpgenerator to generate a
+# Qt Compressed Help (.qch) of the generated HTML documentation.
+
+GENERATE_QHP           = NO
+
+# If the QHG_LOCATION tag is specified, the QCH_FILE tag can
+# be used to specify the file name of the resulting .qch file.
+# The path specified is relative to the HTML output folder.
+
+QCH_FILE               =
+
+# The QHP_NAMESPACE tag specifies the namespace to use when generating
+# Qt Help Project output. For more information please see
+# http://doc.trolltech.com/qthelpproject.html#namespace
+
+QHP_NAMESPACE          = org.doxygen.Project
+
+# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating
+# Qt Help Project output. For more information please see
+# http://doc.trolltech.com/qthelpproject.html#virtual-folders
+
+QHP_VIRTUAL_FOLDER     = doc
+
+# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to
+# add. For more information please see
+# http://doc.trolltech.com/qthelpproject.html#custom-filters
+
+QHP_CUST_FILTER_NAME   =
+
+# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the
+# custom filter to add. For more information please see
+# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">
+# Qt Help Project / Custom Filters</a>.
+
+QHP_CUST_FILTER_ATTRS  =
+
+# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
+# project's
+# filter section matches.
+# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">
+# Qt Help Project / Filter Attributes</a>.
+
+QHP_SECT_FILTER_ATTRS  =
+
+# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can
+# be used to specify the location of Qt's qhelpgenerator.
+# If non-empty doxygen will try to run qhelpgenerator on the generated
+# .qhp file.
+
+QHG_LOCATION           =
+
+# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files
+#  will be generated, which together with the HTML files, form an Eclipse help
+# plugin. To install this plugin and make it available under the help contents
+# menu in Eclipse, the contents of the directory containing the HTML and XML
+# files needs to be copied into the plugins directory of eclipse. The name of
+# the directory within the plugins directory should be the same as
+# the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before
+# the help appears.
+
+GENERATE_ECLIPSEHELP   = NO
+
+# A unique identifier for the eclipse help plugin. When installing the plugin
+# the directory name containing the HTML and XML files should also have
+# this name.
+
+ECLIPSE_DOC_ID         = org.doxygen.Project
+
+# The DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs)
+# at top of each HTML page. The value NO (the default) enables the index and
+# the value YES disables it. Since the tabs have the same information as the
+# navigation tree you can set this option to NO if you already set
+# GENERATE_TREEVIEW to YES.
+
+DISABLE_INDEX          = YES
+
+# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
+# structure should be generated to display hierarchical information.
+# If the tag value is set to YES, a side panel will be generated
+# containing a tree-like index structure (just like the one that
+# is generated for HTML Help). For this to work a browser that supports
+# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser).
+# Windows users are probably better off using the HTML help feature.
+# Since the tree basically has the same information as the tab index you
+# could consider to set DISABLE_INDEX to NO when enabling this option.
+
+GENERATE_TREEVIEW      = YES
+
+# The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values
+# (range [0,1..20]) that doxygen will group on one line in the generated HTML
+# documentation. Note that a value of 0 will completely suppress the enum
+# values from appearing in the overview section.
+
+ENUM_VALUES_PER_LINE   = 1
+
+# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
+# used to set the initial width (in pixels) of the frame in which the tree
+# is shown.
+
+TREEVIEW_WIDTH         = 250
+
+# When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open
+# links to external symbols imported via tag files in a separate window.
+
+EXT_LINKS_IN_WINDOW    = NO
+
+# Use this tag to change the font size of Latex formulas included
+# as images in the HTML documentation. The default is 10. Note that
+# when you change the font size after a successful doxygen run you need
+# to manually remove any form_*.png images from the HTML output directory
+# to force them to be regenerated.
+
+FORMULA_FONTSIZE       = 10
+
+# Use the FORMULA_TRANPARENT tag to determine whether or not the images
+# generated for formulas are transparent PNGs. Transparent PNGs are
+# not supported properly for IE 6.0, but are supported on all modern browsers.
+# Note that when changing this option you need to delete any form_*.png files
+# in the HTML output before the changes have effect.
+
+FORMULA_TRANSPARENT    = YES
+
+# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax
+# (see http://www.mathjax.org) which uses client side Javascript for the
+# rendering instead of using prerendered bitmaps. Use this if you do not
+# have LaTeX installed or if you want to formulas look prettier in the HTML
+# output. When enabled you may also need to install MathJax separately and
+# configure the path to it using the MATHJAX_RELPATH option.
+
+USE_MATHJAX            = NO
+
+# When MathJax is enabled you can set the default output format to be used for
+# thA MathJax output. Supported types are HTML-CSS, NativeMML (i.e. MathML) and
+# SVG. The default value is HTML-CSS, which is slower, but has the best
+# compatibility.
+
+MATHJAX_FORMAT         = HTML-CSS
+
+# When MathJax is enabled you need to specify the location relative to the
+# HTML output directory using the MATHJAX_RELPATH option. The destination
+# directory should contain the MathJax.js script. For instance, if the mathjax
+# directory is located at the same level as the HTML output directory, then
+# MATHJAX_RELPATH should be ../mathjax. The default value points to
+# the MathJax Content Delivery Network so you can quickly see the result without
+# installing MathJax.
+# However, it is strongly recommended to install a local
+# copy of MathJax from http://www.mathjax.org before deployment.
+
+MATHJAX_RELPATH        = http://cdn.mathjax.org/mathjax/latest
+
+# The MATHJAX_EXTENSIONS tag can be used to specify one or MathJax extension
+# names that should be enabled during MathJax rendering.
+
+MATHJAX_EXTENSIONS     =
+
+# When the SEARCHENGINE tag is enabled doxygen will generate a search box
+# for the HTML output. The underlying search engine uses javascript
+# and DHTML and should work on any modern browser. Note that when using
+# HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets
+# (GENERATE_DOCSET) there is already a search function so this one should
+# typically be disabled. For large projects the javascript based search engine
+# can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution.
+
+SEARCHENGINE           = NO
+
+# When the SERVER_BASED_SEARCH tag is enabled the search engine will be
+# implemented using a web server instead of a web client using Javascript.
+# There are two flavours of web server based search depending on the
+# EXTERNAL_SEARCH setting. When disabled, doxygen will generate a PHP script for
+# searching and an index file used by the script. When EXTERNAL_SEARCH is
+# enabled the indexing and searching needs to be provided by external tools.
+# See the manual for details.
+
+SERVER_BASED_SEARCH    = NO
+
+# When EXTERNAL_SEARCH is enabled doxygen will no longer generate the PHP
+# script for searching. Instead the search results are written to an XML file
+# which needs to be processed by an external indexer. Doxygen will invoke an
+# external search engine pointed to by the SEARCHENGINE_URL option to obtain
+# the search results. Doxygen ships with an example indexer (doxyindexer) and
+# search engine (doxysearch.cgi) which are based on the open source search engine
+# library Xapian. See the manual for configuration details.
+
+EXTERNAL_SEARCH        = NO
+
+# The SEARCHENGINE_URL should point to a search engine hosted by a web server
+# which will returned the search results when EXTERNAL_SEARCH is enabled.
+# Doxygen ships with an example search engine (doxysearch) which is based on
+# the open source search engine library Xapian. See the manual for configuration
+# details.
+
+SEARCHENGINE_URL       =
+
+# When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the unindexed
+# search data is written to a file for indexing by an external tool. With the
+# SEARCHDATA_FILE tag the name of this file can be specified.
+
+SEARCHDATA_FILE        = searchdata.xml
+
+# When SERVER_BASED_SEARCH AND EXTERNAL_SEARCH are both enabled the
+# EXTERNAL_SEARCH_ID tag can be used as an identifier for the project. This is
+# useful in combination with EXTRA_SEARCH_MAPPINGS to search through multiple
+# projects and redirect the results back to the right project.
+
+EXTERNAL_SEARCH_ID     =
+
+# The EXTRA_SEARCH_MAPPINGS tag can be used to enable searching through doxygen
+# projects other than the one defined by this configuration file, but that are
+# all added to the same external search index. Each project needs to have a
+# unique id set via EXTERNAL_SEARCH_ID. The search mapping then maps the id
+# of to a relative location where the documentation can be found.
+# The format is: EXTRA_SEARCH_MAPPINGS = id1=loc1 id2=loc2 ...
+
+EXTRA_SEARCH_MAPPINGS  =
+
+#---------------------------------------------------------------------------
+# configuration options related to the LaTeX output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
+# generate Latex output.
+
+GENERATE_LATEX         = YES
+
+# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be
+# put in front of it. If left blank `latex' will be used as the default path.
+
+LATEX_OUTPUT           = latex
+
+# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
+# invoked. If left blank `latex' will be used as the default command name.
+# Note that when enabling USE_PDFLATEX this option is only used for
+# generating bitmaps for formulas in the HTML output, but not in the
+# Makefile that is written to the output directory.
+
+LATEX_CMD_NAME         = latex
+
+# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
+# generate index for LaTeX. If left blank `makeindex' will be used as the
+# default command name.
+
+MAKEINDEX_CMD_NAME     = makeindex
+
+# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
+# LaTeX documents. This may be useful for small projects and may help to
+# save some trees in general.
+
+COMPACT_LATEX          = YES 
+
+# The PAPER_TYPE tag can be used to set the paper type that is used
+# by the printer. Possible values are: a4, letter, legal and
+# executive. If left blank a4wide will be used.
+
+PAPER_TYPE             = a4
+
+# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
+# packages that should be included in the LaTeX output.
+
+EXTRA_PACKAGES         =
+
+# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
+# the generated latex document. The header should contain everything until
+# the first chapter. If it is left blank doxygen will generate a
+# standard header. Notice: only use this tag if you know what you are doing!
+
+LATEX_HEADER           =
+
+# The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for
+# the generated latex document. The footer should contain everything after
+# the last chapter. If it is left blank doxygen will generate a
+# standard footer. Notice: only use this tag if you know what you are doing!
+
+LATEX_FOOTER           =
+
+# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
+# is prepared for conversion to pdf (using ps2pdf). The pdf file will
+# contain links (just like the HTML output) instead of page references
+# This makes the output suitable for online browsing using a pdf viewer.
+
+PDF_HYPERLINKS         = YES
+
+# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
+# plain latex in the generated Makefile. Set this option to YES to get a
+# higher quality PDF documentation.
+
+USE_PDFLATEX           = YES
+
+# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
+# command to the generated LaTeX files. This will instruct LaTeX to keep
+# running if errors occur, instead of asking the user for help.
+# This option is also used when generating formulas in HTML.
+
+LATEX_BATCHMODE        = NO
+
+# If LATEX_HIDE_INDICES is set to YES then doxygen will not
+# include the index chapters (such as File Index, Compound Index, etc.)
+# in the output.
+
+LATEX_HIDE_INDICES     = NO
+
+# If LATEX_SOURCE_CODE is set to YES then doxygen will include
+# source code with syntax highlighting in the LaTeX output.
+# Note that which sources are shown also depends on other settings
+# such as SOURCE_BROWSER.
+
+LATEX_SOURCE_CODE      = NO 
+
+# The LATEX_BIB_STYLE tag can be used to specify the style to use for the
+# bibliography, e.g. plainnat, or ieeetr. The default style is "plain". See
+# http://en.wikipedia.org/wiki/BibTeX for more info.
+
+LATEX_BIB_STYLE        = plain
+
+#---------------------------------------------------------------------------
+# configuration options related to the RTF output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
+# The RTF output is optimized for Word 97 and may not look very pretty with
+# other RTF readers or editors.
+
+GENERATE_RTF           = NO
+
+# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be
+# put in front of it. If left blank `rtf' will be used as the default path.
+
+RTF_OUTPUT             = rtf
+
+# If the COMPACT_RTF tag is set to YES Doxygen generates more compact
+# RTF documents. This may be useful for small projects and may help to
+# save some trees in general.
+
+COMPACT_RTF            = NO
+
+# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
+# will contain hyperlink fields. The RTF file will
+# contain links (just like the HTML output) instead of page references.
+# This makes the output suitable for online browsing using WORD or other
+# programs which support those fields.
+# Note: wordpad (write) and others do not support links.
+
+RTF_HYPERLINKS         = NO
+
+# Load style sheet definitions from file. Syntax is similar to doxygen's
+# config file, i.e. a series of assignments. You only have to provide
+# replacements, missing definitions are set to their default value.
+
+RTF_STYLESHEET_FILE    =
+
+# Set optional variables used in the generation of an rtf document.
+# Syntax is similar to doxygen's config file.
+
+RTF_EXTENSIONS_FILE    =
+
+#---------------------------------------------------------------------------
+# configuration options related to the man page output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
+# generate man pages
+
+GENERATE_MAN           = YES
+
+# The MAN_OUTPUT tag is used to specify where the man pages will be put.
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be
+# put in front of it. If left blank `man' will be used as the default path.
+
+MAN_OUTPUT             = man
+
+# The MAN_EXTENSION tag determines the extension that is added to
+# the generated man pages (default is the subroutine's section .3)
+
+MAN_EXTENSION          = .3
+
+# If the MAN_LINKS tag is set to YES and Doxygen generates man output,
+# then it will generate one additional man file for each entity
+# documented in the real man page(s). These additional files
+# only source the real man page, but without them the man command
+# would be unable to find the correct page. The default is NO.
+
+MAN_LINKS              = NO
+
+#---------------------------------------------------------------------------
+# configuration options related to the XML output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_XML tag is set to YES Doxygen will
+# generate an XML file that captures the structure of
+# the code including all documentation.
+
+GENERATE_XML           = NO
+
+# The XML_OUTPUT tag is used to specify where the XML pages will be put.
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be
+# put in front of it. If left blank `xml' will be used as the default path.
+
+XML_OUTPUT             = xml
+
+# The XML_SCHEMA tag can be used to specify an XML schema,
+# which can be used by a validating XML parser to check the
+# syntax of the XML files.
+
+XML_SCHEMA             =
+
+# The XML_DTD tag can be used to specify an XML DTD,
+# which can be used by a validating XML parser to check the
+# syntax of the XML files.
+
+XML_DTD                =
+
+# If the XML_PROGRAMLISTING tag is set to YES Doxygen will
+# dump the program listings (including syntax highlighting
+# and cross-referencing information) to the XML output. Note that
+# enabling this will significantly increase the size of the XML output.
+
+XML_PROGRAMLISTING     = YES
+
+#---------------------------------------------------------------------------
+# configuration options for the AutoGen Definitions output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
+# generate an AutoGen Definitions (see autogen.sf.net) file
+# that captures the structure of the code including all
+# documentation. Note that this feature is still experimental
+# and incomplete at the moment.
+
+GENERATE_AUTOGEN_DEF   = NO
+
+#---------------------------------------------------------------------------
+# configuration options related to the Perl module output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_PERLMOD tag is set to YES Doxygen will
+# generate a Perl module file that captures the structure of
+# the code including all documentation. Note that this
+# feature is still experimental and incomplete at the
+# moment.
+
+GENERATE_PERLMOD       = NO
+
+# If the PERLMOD_LATEX tag is set to YES Doxygen will generate
+# the necessary Makefile rules, Perl scripts and LaTeX code to be able
+# to generate PDF and DVI output from the Perl module output.
+
+PERLMOD_LATEX          = NO
+
+# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
+# nicely formatted so it can be parsed by a human reader.
+# This is useful
+# if you want to understand what is going on.
+# On the other hand, if this
+# tag is set to NO the size of the Perl module output will be much smaller
+# and Perl will parse it just the same.
+
+PERLMOD_PRETTY         = YES
+
+# The names of the make variables in the generated doxyrules.make file
+# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
+# This is useful so different doxyrules.make files included by the same
+# Makefile don't overwrite each other's variables.
+
+PERLMOD_MAKEVAR_PREFIX =
+
+#---------------------------------------------------------------------------
+# Configuration options related to the preprocessor
+#---------------------------------------------------------------------------
+
+# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
+# evaluate all C-preprocessor directives found in the sources and include
+# files.
+
+ENABLE_PREPROCESSING   = YES
+
+# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
+# names in the source code. If set to NO (the default) only conditional
+# compilation will be performed. Macro expansion can be done in a controlled
+# way by setting EXPAND_ONLY_PREDEF to YES.
+
+MACRO_EXPANSION        = NO
+
+# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
+# then the macro expansion is limited to the macros specified with the
+# PREDEFINED and EXPAND_AS_DEFINED tags.
+
+EXPAND_ONLY_PREDEF     = NO
+
+# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
+# pointed to by INCLUDE_PATH will be searched when a #include is found.
+
+SEARCH_INCLUDES        = YES
+
+# The INCLUDE_PATH tag can be used to specify one or more directories that
+# contain include files that are not input files but should be processed by
+# the preprocessor.
+
+INCLUDE_PATH           =
+
+# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
+# patterns (like *.h and *.hpp) to filter out the header-files in the
+# directories. If left blank, the patterns specified with FILE_PATTERNS will
+# be used.
+
+INCLUDE_FILE_PATTERNS  =
+
+# The PREDEFINED tag can be used to specify one or more macro names that
+# are defined before the preprocessor is started (similar to the -D option of
+# gcc). The argument of the tag is a list of macros of the form: name
+# or name=definition (no spaces). If the definition and the = are
+# omitted =1 is assumed. To prevent a macro definition from being
+# undefined via #undef or recursively expanded use the := operator
+# instead of the = operator.
+
+PREDEFINED             =
+
+# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
+# this tag can be used to specify a list of macro names that should be expanded.
+# The macro definition that is found in the sources will be used.
+# Use the PREDEFINED tag if you want to use a different macro definition that
+# overrules the definition found in the source code.
+
+EXPAND_AS_DEFINED      =
+
+# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
+# doxygen's preprocessor will remove all references to function-like macros
+# that are alone on a line, have an all uppercase name, and do not end with a
+# semicolon, because these will confuse the parser if not removed.
+
+SKIP_FUNCTION_MACROS   = YES
+
+#---------------------------------------------------------------------------
+# Configuration::additions related to external references
+#---------------------------------------------------------------------------
+
+# The TAGFILES option can be used to specify one or more tagfiles. For each
+# tag file the location of the external documentation should be added. The
+# format of a tag file without this location is as follows:
+#
+# TAGFILES = file1 file2 ...
+# Adding location for the tag files is done as follows:
+#
+# TAGFILES = file1=loc1 "file2 = loc2" ...
+# where "loc1" and "loc2" can be relative or absolute paths
+# or URLs. Note that each tag file must have a unique name (where the name does
+# NOT include the path). If a tag file is not located in the directory in which
+# doxygen is run, you must also specify the path to the tagfile here.
+
+TAGFILES               =
+
+# When a file name is specified after GENERATE_TAGFILE, doxygen will create
+# a tag file that is based on the input files it reads.
+
+GENERATE_TAGFILE       =
+
+# If the ALLEXTERNALS tag is set to YES all external classes will be listed
+# in the class index. If set to NO only the inherited external classes
+# will be listed.
+
+ALLEXTERNALS           = NO
+
+# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
+# in the modules index. If set to NO, only the current project's groups will
+# be listed.
+
+EXTERNAL_GROUPS        = YES
+
+# The PERL_PATH should be the absolute path and name of the perl script
+# interpreter (i.e. the result of `which perl').
+
+PERL_PATH              = /usr/bin/perl
+
+#---------------------------------------------------------------------------
+# Configuration options related to the dot tool
+#---------------------------------------------------------------------------
+
+# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
+# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
+# or super classes. Setting the tag to NO turns the diagrams off. Note that
+# this option also works with HAVE_DOT disabled, but it is recommended to
+# install and use dot, since it yields more powerful graphs.
+
+CLASS_DIAGRAMS         = YES
+
+# You can define message sequence charts within doxygen comments using the \msc
+# command. Doxygen will then run the mscgen tool (see
+# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the
+# documentation. The MSCGEN_PATH tag allows you to specify the directory where
+# the mscgen tool resides. If left empty the tool is assumed to be found in the
+# default search path.
+
+MSCGEN_PATH            =
+
+# If set to YES, the inheritance and collaboration graphs will hide
+# inheritance and usage relations if the target is undocumented
+# or is not a class.
+
+HIDE_UNDOC_RELATIONS   = NO
+
+# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
+# available from the path. This tool is part of Graphviz, a graph visualization
+# toolkit from AT&T and Lucent Bell Labs. The other options in this section
+# have no effect if this option is set to NO (the default)
+
+HAVE_DOT               = YES
+
+# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is
+# allowed to run in parallel. When set to 0 (the default) doxygen will
+# base this on the number of processors available in the system. You can set it
+# explicitly to a value larger than 0 to get control over the balance
+# between CPU load and processing speed.
+
+DOT_NUM_THREADS        = 1 
+
+# By default doxygen will use the Helvetica font for all dot files that
+# doxygen generates. When you want a differently looking font you can specify
+# the font name using DOT_FONTNAME. You need to make sure dot is able to find
+# the font, which can be done by putting it in a standard location or by setting
+# the DOTFONTPATH environment variable or by setting DOT_FONTPATH to the
+# directory containing the font.
+
+DOT_FONTNAME           = Helvetica
+
+# The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs.
+# The default size is 10pt.
+
+DOT_FONTSIZE           = 10
+
+# By default doxygen will tell dot to use the Helvetica font.
+# If you specify a different font using DOT_FONTNAME you can use DOT_FONTPATH to
+# set the path where dot can find it.
+
+DOT_FONTPATH           =
+
+# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
+# will generate a graph for each documented class showing the direct and
+# indirect inheritance relations. Setting this tag to YES will force the
+# CLASS_DIAGRAMS tag to NO.
+
+CLASS_GRAPH            = YES
+
+# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
+# will generate a graph for each documented class showing the direct and
+# indirect implementation dependencies (inheritance, containment, and
+# class references variables) of the class with other documented classes.
+
+COLLABORATION_GRAPH    = YES
+
+# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen
+# will generate a graph for groups, showing the direct groups dependencies
+
+GROUP_GRAPHS           = YES
+
+# If the UML_LOOK tag is set to YES doxygen will generate inheritance and
+# collaboration diagrams in a style similar to the OMG's Unified Modeling
+# Language.
+
+UML_LOOK               = YES
+
+# If the UML_LOOK tag is enabled, the fields and methods are shown inside
+# the class node. If there are many fields or methods and many nodes the
+# graph may become too big to be useful. The UML_LIMIT_NUM_FIELDS
+# threshold limits the number of items for each type to make the size more
+# managable. Set this to 0 for no limit. Note that the threshold may be
+# exceeded by 50% before the limit is enforced.
+
+UML_LIMIT_NUM_FIELDS   = 10
+
+# If set to YES, the inheritance and collaboration graphs will show the
+# relations between templates and their instances.
+
+TEMPLATE_RELATIONS     = NO
+
+# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
+# tags are set to YES then doxygen will generate a graph for each documented
+# file showing the direct and indirect include dependencies of the file with
+# other documented files.
+
+INCLUDE_GRAPH          = YES
+
+# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
+# HAVE_DOT tags are set to YES then doxygen will generate a graph for each
+# documented header file showing the documented files that directly or
+# indirectly include this file.
+
+INCLUDED_BY_GRAPH      = YES
+
+# If the CALL_GRAPH and HAVE_DOT options are set to YES then
+# doxygen will generate a call dependency graph for every global function
+# or class method. Note that enabling this option will significantly increase
+# the time of a run. So in most cases it will be better to enable call graphs
+# for selected functions only using the \callgraph command.
+
+CALL_GRAPH             = YES
+
+# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then
+# doxygen will generate a caller dependency graph for every global function
+# or class method. Note that enabling this option will significantly increase
+# the time of a run. So in most cases it will be better to enable caller
+# graphs for selected functions only using the \callergraph command.
+
+CALLER_GRAPH           = NO
+
+# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
+# will generate a graphical hierarchy of all classes instead of a textual one.
+
+GRAPHICAL_HIERARCHY    = YES
+
+# If the DIRECTORY_GRAPH and HAVE_DOT tags are set to YES
+# then doxygen will show the dependencies a directory has on other directories
+# in a graphical way. The dependency relations are determined by the #include
+# relations between the files in the directories.
+
+DIRECTORY_GRAPH        = YES
+
+# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
+# generated by dot. Possible values are svg, png, jpg, or gif.
+# If left blank png will be used. If you choose svg you need to set
+# HTML_FILE_EXTENSION to xhtml in order to make the SVG files
+# visible in IE 9+ (other browsers do not have this requirement).
+
+DOT_IMAGE_FORMAT       = png
+
+# If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to
+# enable generation of interactive SVG images that allow zooming and panning.
+# Note that this requires a modern browser other than Internet Explorer.
+# Tested and working are Firefox, Chrome, Safari, and Opera. For IE 9+ you
+# need to set HTML_FILE_EXTENSION to xhtml in order to make the SVG files
+# visible. Older versions of IE do not have SVG support.
+
+INTERACTIVE_SVG        = YES
+
+# The tag DOT_PATH can be used to specify the path where the dot tool can be
+# found. If left blank, it is assumed the dot tool can be found in the path.
+
+DOT_PATH               =
+
+# The DOTFILE_DIRS tag can be used to specify one or more directories that
+# contain dot files that are included in the documentation (see the
+# \dotfile command).
+
+DOTFILE_DIRS           =
+
+# The MSCFILE_DIRS tag can be used to specify one or more directories that
+# contain msc files that are included in the documentation (see the
+# \mscfile command).
+
+MSCFILE_DIRS           =
+
+# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of
+# nodes that will be shown in the graph. If the number of nodes in a graph
+# becomes larger than this value, doxygen will truncate the graph, which is
+# visualized by representing a node as a red box. Note that doxygen if the
+# number of direct children of the root node in a graph is already larger than
+# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note
+# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
+
+DOT_GRAPH_MAX_NODES    = 50
+
+# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
+# graphs generated by dot. A depth value of 3 means that only nodes reachable
+# from the root by following a path via at most 3 edges will be shown. Nodes
+# that lay further from the root node will be omitted. Note that setting this
+# option to 1 or 2 may greatly reduce the computation time needed for large
+# code bases. Also note that the size of a graph can be further restricted by
+# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
+
+MAX_DOT_GRAPH_DEPTH    = 0
+
+# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
+# background. This is disabled by default, because dot on Windows does not
+# seem to support this out of the box. Warning: Depending on the platform used,
+# enabling this option may lead to badly anti-aliased labels on the edges of
+# a graph (i.e. they become hard to read).
+
+DOT_TRANSPARENT        = YES
+
+# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
+# files in one run (i.e. multiple -o and -T options on the command line). This
+# makes dot run faster, but since only newer versions of dot (>1.8.10)
+# support this, this feature is disabled by default.
+
+DOT_MULTI_TARGETS      = YES
+
+# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
+# generate a legend page explaining the meaning of the various boxes and
+# arrows in the dot generated graphs.
+
+GENERATE_LEGEND        = YES
+
+# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
+# remove the intermediate dot files that are used to generate
+# the various graphs.
+
+DOT_CLEANUP            = YES

=== added directory 'examples/mfw-plugin-dummy/include'
=== added file 'examples/mfw-plugin-dummy/include/CMakeLists.txt'
--- examples/mfw-plugin-dummy/include/CMakeLists.txt	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/include/CMakeLists.txt	2017-03-22 21:22:50 +0000
@@ -0,0 +1,3 @@
+# make the .h files visible on qtcreator
+file(GLOB_RECURSE H_FILES_PLUGIN *.h)
+add_custom_target(dot_h_files_plugin ALL SOURCES ${H_FILES_PLUGIN})

=== added directory 'examples/mfw-plugin-dummy/include/dummy'
=== added file 'examples/mfw-plugin-dummy/include/dummy/chat.h'
--- examples/mfw-plugin-dummy/include/dummy/chat.h	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/include/dummy/chat.h	2017-03-22 21:22:50 +0000
@@ -0,0 +1,31 @@
+#ifndef DUMMY_CLI_CHAT
+#define DUMMY_CLI_CHAT
+
+#include <messaging/chat.h>
+
+#include <map>
+
+namespace dummy
+{
+
+/// @brief base class not instantiable for ContactChat, GroupChat, ...
+class Chat
+        : public messaging::Chat
+{
+public:
+    virtual ~Chat();
+    std::string download_file(std::string) override;
+    void handle_incoming_message(const messaging::Message& message);
+
+protected:
+    Chat(const std::shared_ptr<messaging::Chat::Observer>& observer);
+
+    void mark_message_as_delivered(const std::string &alias, uint session_id = 0);
+    void mark_message_as_read(const std::string &alias, uint session_id = 0);
+
+};
+
+}
+
+#endif // DUMMY_CLI_CHAT
+

=== added file 'examples/mfw-plugin-dummy/include/dummy/connection.h'
--- examples/mfw-plugin-dummy/include/dummy/connection.h	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/include/dummy/connection.h	2017-03-22 21:22:50 +0000
@@ -0,0 +1,98 @@
+#ifndef DUMMY_CLI_CONNECTION_H_
+#define DUMMY_CLI_CONNECTION_H_
+
+#include <dummy/visibility.h>
+
+#include <dummy/messenger.h>
+#include <dummy/presence_manager.h>
+#include <dummy/group_starter.h>
+
+#include <messaging/associative_dictionary.h>
+#include <messaging/connection.h>
+
+
+namespace messaging
+{
+// Handy fw declarations
+class Variant;
+class BoostVariant;
+}
+
+class Connection;
+
+namespace dummy
+{
+
+class Connector;
+
+/// @brief Connection models an active, logged in session with DUMMY server.
+class DUMMY_PUBLIC Connection : public messaging::Connection, public std::enable_shared_from_this<Connection>
+{
+public:
+
+    /// @brief Constructs a new connection instance with the given connector as parent.
+    ///
+    /// Attempts a login on construction.
+    ///
+    /// @throws dummy::Error if there are any issues logging in to the DUMMY server.
+    Connection(const std::shared_ptr<messaging::Connection::Observer>& connection_observer,
+               const std::shared_ptr<messaging::Messenger::Observer>& messenger_observer,
+               const std::shared_ptr<messaging::PresenceManager::Observer>& presence_observer,
+               const messaging::Dictionary<std::string, messaging::Variant>& dict,
+               Connector *connector);
+
+    /// @brief ~Connection frees up all resources and logs out from the DUMMY server.
+    ~Connection();
+
+    /// @brief presence_manager returns a mutable reference to an instance of Presence
+    std::shared_ptr<messaging::PresenceManager> presence_manager() override;
+
+    /// @brief messenger returns a mutable reference to an instance of Messenger.
+    std::shared_ptr<messaging::Messenger> messenger() override;
+
+    /// @brief group_starter returns a mutable referece to an instance of GroupStarter
+    std::shared_ptr<messaging::GroupStarter> group_starter() override;
+
+    /// @brief returns identifier of current plugin user
+    std::string self_identifier() override;
+
+    /// @brief login log in to server
+    void connect() override;
+
+    /// @brief logout logs out from server
+    void disconnect(messaging::Connection::StatusChangedReason reason) override;
+
+    /// @brief change_status changes the current status of connection to the server
+    void set_status(Status new_status, StatusChangedReason reason = StatusChangedReason::not_specified);
+
+    /// @brief request_presence request the current state for a peer
+    void request_presence(const std::string& sip_uri);
+
+    /// @brief normalize_identifier unifies the format of an identifier
+    std::string normalize_identifier(const std::string& id) override;
+
+    /// @brief checks if an identifier is valid
+    bool is_valid_identifier(const std::string &id) override;
+
+private:
+
+    /// @brief parent reference
+    Connector* connector_;
+
+    /// @brief The messenger instance for managing IM messages
+    std::shared_ptr<Messenger> messenger_;
+    /// @brief the instance to manage the presence
+    std::shared_ptr<PresenceManager> presence_manager_;
+    /// @brief the instance to manage the group creation/acceptance/rejoin
+    std::shared_ptr<GroupStarter> group_starter_;
+
+    std::shared_ptr<messaging::Messenger::Observer> messenger_observer_;
+
+    std::string account;
+    std::string password;
+};
+}
+
+
+
+#endif  // DUMMY_CLI_CONNECTION_H_

=== added file 'examples/mfw-plugin-dummy/include/dummy/connector.h'
--- examples/mfw-plugin-dummy/include/dummy/connector.h	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/include/dummy/connector.h	2017-03-22 21:22:50 +0000
@@ -0,0 +1,58 @@
+#ifndef DUMMY_CLI_CONNECTOR_H_
+#define DUMMY_CLI_CONNECTOR_H_
+
+#include <dummy/visibility.h>
+
+#include <messaging/connector.h>
+#include <messaging/messenger.h>
+#include <messaging/enumerator.h>
+#include <messaging/associative_dictionary.h>
+
+
+namespace messaging
+{
+// Handy fw declarations
+class Variant;
+class BoostVariant;
+}
+
+namespace dummy
+{
+
+// Handy fw declarations
+class Connection;
+
+class DUMMY_PUBLIC Connector : public messaging::Connector
+{
+public:
+
+    // create returns a new shared instance of Connector.
+    static std::shared_ptr<Connector> create();
+    virtual ~Connector();
+
+    void run() override;
+    void stop() override;
+    bool network_monitor_enabled() override;
+    const messaging::Enumerator<messaging::Parameter>& parameters() const override;
+    std::shared_ptr<messaging::Connection> request_connection(
+        const std::shared_ptr<messaging::Connection::Observer>& connection_observer,
+        const std::shared_ptr<messaging::Messenger::Observer>& messenger_observer,
+        const std::shared_ptr<messaging::PresenceManager::Observer>& presence_observer,
+        const messaging::Dictionary<std::string, messaging::Variant>& dict =
+            messaging::AssociativeDictionary<std::string, messaging::BoostVariant, messaging::Variant>()) override;
+
+    void release_connection(const std::weak_ptr<Connection>& connection);
+
+private:
+    Connector();
+
+    static Connector*& mutable_instance();
+    static Connector* instance();
+
+    messaging::StdVectorEnumerator<messaging::Parameter> params_enum_;
+    std::set<std::weak_ptr<Connection>, std::owner_less<std::weak_ptr<Connection>>> connections_;
+};
+}
+
+
+#endif  // DUMMY_CLI_CONNECTOR_H_

=== added file 'examples/mfw-plugin-dummy/include/dummy/contact_chat.h'
--- examples/mfw-plugin-dummy/include/dummy/contact_chat.h	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/include/dummy/contact_chat.h	2017-03-22 21:22:50 +0000
@@ -0,0 +1,54 @@
+#ifndef DUMMY_CLI_CONTACT_CHAT_H
+#define DUMMY_CLI_CONTACT_CHAT_H
+
+#include <messaging/user.h>
+
+#include <dummy/visibility.h>
+
+#include <dummy/chat.h>
+#include <dummy/user.h>
+
+namespace dummy
+{
+// Handy fw declarations
+class Connector;
+class Message;
+
+
+
+class DUMMY_PUBLIC ContactChat
+        : public Chat
+{
+  public:
+
+    /// @brief Creates a new instance configuring the given user as recipient.
+    static std::shared_ptr<ContactChat> create(const User& user,
+                                               const std::shared_ptr<messaging::Chat::Observer>& observer);
+
+    /// @brief Creates a new instance translating the given recipient to a user.
+    static std::shared_ptr<ContactChat> create(const messaging::User::shared_ptr& user,
+                                               const std::shared_ptr<messaging::Chat::Observer>& observer);
+
+
+    /// @brief send_message enqueues the given message for delivery.
+    /// @returns a numeric identifier referencing back to the delivery request.
+    /// @throws std::runtime_error in case of issues.
+    std::string send_message(const messaging::Message& message) override;
+    void mark_message_as_read(const std::string& message_id) override;
+    void start_typing() override;
+    void end_typing() override;
+
+private:
+    /// @brief Creates a new instance configuring the given user as recipient.
+    ContactChat(const User& user,
+                const std::shared_ptr<messaging::Chat::Observer>& observer);
+    /// @brief Creates a new instance translating the given recipient to a user.
+    ContactChat(const messaging::User::shared_ptr& user,
+                const std::shared_ptr<messaging::Chat::Observer>& observer);
+
+    User recipient;
+};
+}
+
+
+#endif // DUMMY_CLI_CONTACT_CHAT_H_

=== added file 'examples/mfw-plugin-dummy/include/dummy/group_chat.h'
--- examples/mfw-plugin-dummy/include/dummy/group_chat.h	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/include/dummy/group_chat.h	2017-03-22 21:22:50 +0000
@@ -0,0 +1,50 @@
+#ifndef DUMMY_CLI_GROUP_CHAT_H
+#define DUMMY_CLI_GROUP_CHAT_H
+
+#include <dummy/visibility.h>
+
+#include <dummy/chat.h>
+
+namespace messaging
+{
+class Group;
+class Interface;
+}
+
+namespace dummy
+{
+
+// Handy fw declarations
+class GroupManager;
+
+class DUMMY_PUBLIC GroupChat
+        : public Chat
+{
+public:
+
+    /// @brief Creates a new instance translating the given recipient to a user.
+    static std::shared_ptr<GroupChat> create(const std::shared_ptr<messaging::Group> &group,
+                                             const std::shared_ptr<messaging::Chat::Observer>& observer);
+
+    /// @brief send_message enqueues the given message for delivery.
+    /// @returns a numeric identifier referencing back to the delivery request.
+    /// @throws std::runtime_error in case of issues.
+    std::string send_message(const messaging::Message& message) override;
+    void mark_message_as_read(const std::string& message_token) override;
+    void start_typing() override;
+    void end_typing() override;
+
+    void mark_message_as_delivered(const std::string& message_token);
+    std::string id();
+
+private:
+    /// @brief Creates a new instance translating the given recipient to a user.
+    GroupChat(const std::shared_ptr<messaging::Group> &group,
+              const std::shared_ptr<messaging::Chat::Observer>& observer);
+
+    std::string channel_id;
+};
+
+}
+
+#endif // DUMMY_CLI_GROUP_CHAT_H

=== added file 'examples/mfw-plugin-dummy/include/dummy/group_manager.h'
--- examples/mfw-plugin-dummy/include/dummy/group_manager.h	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/include/dummy/group_manager.h	2017-03-22 21:22:50 +0000
@@ -0,0 +1,72 @@
+#ifndef DUMMY_CLI_CHAT_GROUP_MANAGER_H
+#define DUMMY_CLI_CHAT_GROUP_MANAGER_H
+
+#include <dummy/visibility.h>
+
+#include <messaging/group_manager.h>
+#include <messaging/members.h>
+
+namespace messaging
+{
+// Handy fw declarations
+class Group;
+class HasInterfaces;
+}
+
+namespace dummy
+{
+
+// Handy fw declaration
+class Messenger;
+class GroupChat;
+
+
+class DUMMY_PUBLIC GroupManager
+        : public messaging::GroupManager
+        , public std::enable_shared_from_this<GroupManager>
+{
+public:
+
+    /// @brief Creates a new chat group manager configuring the given user as recipient.
+    static std::shared_ptr<GroupManager> create(const std::shared_ptr<messaging::Group>& group,
+                                                const std::shared_ptr<Messenger>& messenger);
+
+    virtual ~GroupManager();
+
+    std::string group_id() override;
+    std::string group_title() override;
+    std::string group_subject() override;
+    bool persistent() override;
+    std::shared_ptr<messaging::Member> group_creator() override;
+    std::set<std::string> group_admins() override;
+    messaging::Members members() override;
+
+    void leave_group() override;
+    void dissolve_group() override;
+    void change_group_title(const std::string& new_title) override;
+    void change_group_subject(const std::string& new_subject) override;
+    void add_members(const messaging::Members& users) override;
+    void remove_members(const messaging::Members& users) override;
+
+    void set_group_permissions(bool is_chairman);
+
+    void set_observer(const std::shared_ptr<Observer> &observer);
+
+private:
+    /// @brief Creates a new instance of chat group manager
+    GroupManager(const std::shared_ptr<messaging::Group>& group,
+                 const std::shared_ptr<Messenger>& messenger);
+
+    void on_plugged(const std::weak_ptr<messaging::HasInterfaces> &where) override;
+
+
+    std::weak_ptr<Messenger> messenger_;
+    std::weak_ptr<GroupChat> chat_;
+    std::string id;
+    messaging::Members participants;
+    std::string creator;
+
+};
+
+}
+#endif // DUMMY_CLI_CHAT_GROUP_MANAGER_H

=== added file 'examples/mfw-plugin-dummy/include/dummy/group_starter.h'
--- examples/mfw-plugin-dummy/include/dummy/group_starter.h	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/include/dummy/group_starter.h	2017-03-22 21:22:50 +0000
@@ -0,0 +1,52 @@
+#ifndef DUMMY_CLI_GROUP_STARTER
+#define DUMMY_CLI_GROUP_STARTER
+
+#include <dummy/visibility.h>
+
+#include <messaging/group_starter.h>
+#include <messaging/members.h>
+
+#include <map>
+
+namespace messaging
+{
+// Handy fw declarations
+class GroupManager;
+class Group;
+class Broadcast;
+}
+
+namespace dummy
+{
+
+class Messenger;
+class GroupManager;
+
+
+class DUMMY_PUBLIC GroupStarter
+        : public messaging::GroupStarter
+        , public std::enable_shared_from_this<GroupStarter>
+{
+public:
+
+    static std::shared_ptr<GroupStarter> create(const std::shared_ptr<Messenger>& messenger);
+
+    std::shared_ptr<messaging::GroupManager> create_group(const std::shared_ptr<messaging::Group> &group) override;
+    std::shared_ptr<messaging::GroupManager> accept_group(const std::shared_ptr<messaging::Group> &group) override;
+    std::shared_ptr<messaging::GroupManager> rejoin_group(const std::shared_ptr<messaging::Group> &group) override;
+    void reject_group(const std::shared_ptr<messaging::Group> &group) override;
+    std::shared_ptr<messaging::Broadcast> create_broadcast(const messaging::Members& recipients);
+    std::map<std::string, std::shared_ptr<dummy::GroupManager>> group_managers();
+
+private:
+    GroupStarter(const std::shared_ptr<Messenger>& messenger);
+
+    std::weak_ptr<Messenger> messenger_;
+    std::map<std::string, std::shared_ptr<dummy::GroupManager>> group_managers_;
+
+};
+
+}
+
+#endif // DUMMY_CLI_GROUP_STARTER
+

=== added file 'examples/mfw-plugin-dummy/include/dummy/messenger.h'
--- examples/mfw-plugin-dummy/include/dummy/messenger.h	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/include/dummy/messenger.h	2017-03-22 21:22:50 +0000
@@ -0,0 +1,50 @@
+#ifndef DUMMY_CLI_MESSENGER_H_
+#define DUMMY_CLI_MESSENGER_H_
+
+#include <dummy/visibility.h>
+
+#include <messaging/messenger.h>
+
+namespace dummy
+{
+
+// Handy fw declaration
+class Message;
+class File;
+class Connector;
+class Connection;
+class GroupManager;
+
+class DUMMY_PUBLIC Messenger
+        : public messaging::Messenger
+        , public std::enable_shared_from_this<Messenger>
+{
+public:
+    /// @cond
+    DEFINE_PTRS(Messenger);
+    /// @endcond
+
+    static std::shared_ptr<Messenger> create(const std::shared_ptr<Messenger::Observer>& messenger_observer, const std::shared_ptr<dummy::Connection> &connection);
+
+    std::shared_ptr<messaging::Chat> create_chat_with(const messaging::Recipient::shared_ptr& recipient, const std::shared_ptr<messaging::Chat::Observer>& observer) override;
+
+    void handle_incoming_message(const std::string &sender, const std::string &message);
+    void handle_incoming_channel_message(const std::string &channel, const std::string &sender, const std::string &message);
+    std::shared_ptr<GroupManager> get_group_manager(const std::string &group_chat_id);
+    void handle_join_new_channel(const std::string &channel);
+    void handle_join_new_channel(const std::string &channel, const std::string &the_creator);
+    void remove_chat(const std::string &chat_id);
+
+    std::shared_ptr<dummy::Connection> connection;
+private:
+    Messenger(const std::shared_ptr<messaging::Messenger::Observer>& observer, const std::shared_ptr<dummy::Connection> &connection);
+
+    /// @brief identity provider to correlate msg_id with imdn unique identifier. First will be
+    /// used internally for chat messages and the other used as message external unique id
+    /// @brief maintains the history of managed messages correlated to their unique_id
+    void send_delivery_notification(const std::shared_ptr<Message>& message);
+};
+}
+
+
+#endif  // DUMMY_CLI_MESSENGER_H_

=== added file 'examples/mfw-plugin-dummy/include/dummy/presence_manager.h'
--- examples/mfw-plugin-dummy/include/dummy/presence_manager.h	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/include/dummy/presence_manager.h	2017-03-22 21:22:50 +0000
@@ -0,0 +1,40 @@
+#ifndef DUMMY_CLI_PRESENCE_MANAGER_H
+#define DUMMY_CLI_PRESENCE_MANAGER_H
+
+#include <dummy/visibility.h>
+
+#include <messaging/presence_manager.h>
+
+#include <memory>
+
+namespace dummy
+{
+
+class Connector;
+
+class DUMMY_PUBLIC PresenceManager : public messaging::PresenceManager, public std::enable_shared_from_this<PresenceManager>
+{
+public:
+
+    static std::shared_ptr<PresenceManager> create(const std::shared_ptr<messaging::PresenceManager::Observer>& observer,
+                                                   Connector *connector);
+
+    StatusMap get_valid_statuses() override;
+    void set_self_presence(const std::string& status, const std::string& status_message = "") override;
+    void request_presence(const std::shared_ptr<messaging::Recipient>& recipient) override;
+
+private:
+    /// @brief Messenger constructs a new instance, installing the given observer instance.
+    PresenceManager(const std::shared_ptr<Observer>& observer,
+                    Connector* connector);
+
+    messaging::Presence create_presence(const std::string& status, const std::string& status_message = "");
+
+    Connector *connector_;
+    StatusMap statuses_;
+};
+
+}
+
+
+#endif // DUMMY_CLI_PRESENCE_MANAGER_H

=== added file 'examples/mfw-plugin-dummy/include/dummy/recipient.h'
--- examples/mfw-plugin-dummy/include/dummy/recipient.h	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/include/dummy/recipient.h	2017-03-22 21:22:50 +0000
@@ -0,0 +1,19 @@
+#ifndef DUMMY_CLI_RECIPIENT_H
+#define DUMMY_CLI_RECIPIENT_H
+
+#include <messaging/recipient.h>
+
+namespace dummy
+{
+
+
+class Recipient : public messaging::Recipient
+{
+public:
+    Recipient() : messaging::Recipient{}
+};
+
+
+}
+
+#endif // DUMMY_CLI_RECIPIENT_H

=== added file 'examples/mfw-plugin-dummy/include/dummy/user.h'
--- examples/mfw-plugin-dummy/include/dummy/user.h	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/include/dummy/user.h	2017-03-22 21:22:50 +0000
@@ -0,0 +1,31 @@
+#ifndef DUMMY_CLI_USER_H_
+#define DUMMY_CLI_USER_H_
+
+#include <dummy/visibility.h>
+
+#include <memory>
+
+#include <map>
+
+namespace messaging
+{
+// A handy fw declaration
+class Recipient;
+}
+
+namespace dummy
+{
+
+
+/// @brief User models a subscriber to DUMMY services.
+struct DUMMY_PUBLIC User
+{
+    std::string username;      ///< dummy username
+
+    static User from_recipient(const std::shared_ptr<messaging::Recipient>& recipient);
+    std::shared_ptr<messaging::Recipient> to_recipient() const;
+};
+}
+
+
+#endif  // DUMMY_CLI_USER_H_

=== added file 'examples/mfw-plugin-dummy/include/dummy/visibility.h'
--- examples/mfw-plugin-dummy/include/dummy/visibility.h	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/include/dummy/visibility.h	2017-03-22 21:22:50 +0000
@@ -0,0 +1,7 @@
+#ifndef DUMMY_VISIBILITY_H_
+#define DUMMY_VISIBILITY_H_
+
+#define DUMMY_PUBLIC __attribute__((visibility("default")))
+#define DUMMY_LOCAL __attribute__((visibility("hidden")))
+
+#endif  // DUMMY_VISIBILITY_H_

=== added directory 'examples/mfw-plugin-dummy/src'
=== added file 'examples/mfw-plugin-dummy/src/CMakeLists.txt'
--- examples/mfw-plugin-dummy/src/CMakeLists.txt	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/src/CMakeLists.txt	2017-03-22 21:22:50 +0000
@@ -0,0 +1,43 @@
+set(PLUGIN_NAME mfw-plugin-dummy)
+
+add_library(${PLUGIN_NAME} SHARED
+
+    ${PLUGIN_MOCS}
+
+    dummy/group_manager.cpp
+    dummy/chat.cpp
+    dummy/connection.cpp
+    dummy/connector.cpp
+    dummy/contact_chat.cpp
+    dummy/group_starter.cpp
+    dummy/messenger.cpp
+    dummy/group_chat.cpp
+    dummy/presence_manager.cpp
+    dummy/user.cpp
+)
+
+set_target_properties(${PLUGIN_NAME} PROPERTIES VERSION ${SO_VERSION} SOVERSION ${SO_VERSION_MAJOR})
+set (PLUGIN_LINK_LIBRARIES
+    ${MESSAGING_FW_LIBRARIES}
+    Qt5::Core
+    Qt5::DBus
+    ${ACCOUNTS_LDFLAGS}
+    ${ZLIB_LIBRARIES}
+    ${GLog_LIBRARY}
+    ${Boost_LIBRARIES}
+    ${PROCESS_CPP_LDFLAGS}
+    ${CPPNETLIB_LIBRARIES}
+    -lpthread
+)
+
+if(IS_MF_BUILD)
+    set (PLUGIN_LINK_LIBRARIES ${PLUGIN_LINK_LIBRARIES} messaging-framework)
+endif()
+
+target_link_libraries(${PLUGIN_NAME}
+    ${PLUGIN_LINK_LIBRARIES}
+)
+
+install(
+    TARGETS ${PLUGIN_NAME}
+    LIBRARY DESTINATION ${CMAKE_INSTALL_LIBDIR}/messaging-framework)

=== added directory 'examples/mfw-plugin-dummy/src/dummy'
=== added file 'examples/mfw-plugin-dummy/src/dummy/chat.cpp'
--- examples/mfw-plugin-dummy/src/dummy/chat.cpp	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/src/dummy/chat.cpp	2017-03-22 21:22:50 +0000
@@ -0,0 +1,30 @@
+#include <dummy/chat.h>
+
+#include <glog/logging.h>
+
+dummy::Chat::Chat(const std::shared_ptr<messaging::Chat::Observer>& observer)
+    : messaging::Chat{observer}
+{
+}
+
+dummy::Chat::~Chat()
+{
+}
+
+
+std::string dummy::Chat::download_file(std::string alias)
+{
+}
+
+void dummy::Chat::mark_message_as_delivered(const std::string &alias, uint session_id)
+{
+}
+
+void dummy::Chat::mark_message_as_read(const std::string &alias, uint session_id)
+{
+}
+
+void dummy::Chat::handle_incoming_message(const messaging::Message& message)
+{
+    announce_message_received(message);
+}

=== added file 'examples/mfw-plugin-dummy/src/dummy/connection.cpp'
--- examples/mfw-plugin-dummy/src/dummy/connection.cpp	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/src/dummy/connection.cpp	2017-03-22 21:22:50 +0000
@@ -0,0 +1,132 @@
+#include <dummy/connection.h>
+#include <dummy/connector.h>
+#include <dummy/group_manager.h>
+#include <dummy/group_chat.h>
+
+#include <glog/logging.h>
+
+#include <messaging/parameter.h>
+#include <messaging/group.h>
+
+using namespace std;
+
+dummy::Connection::Connection(const std::shared_ptr<messaging::Connection::Observer>& connection_observer,
+                           const std::shared_ptr<messaging::Messenger::Observer>& messenger_observer,
+                           const std::shared_ptr<messaging::PresenceManager::Observer>& presence_observer,
+                           const messaging::Dictionary<std::string, messaging::Variant>& dict,
+                           Connector *connector)
+    : messaging::Connection{connection_observer}
+    , connector_{connector}
+    , presence_manager_(PresenceManager::create(presence_observer, connector))
+    , messenger_observer_(messenger_observer)
+{
+    messaging::Parameter account_param{"account", "s", messaging::Parameter::Flags::required|messaging::Parameter::Flags::required_for_registration};
+    messaging::Parameter password_param{"password", "s", messaging::Parameter::Flags::secret};
+
+    if (account_param.can_extract_from(dict))
+    {
+        account = account_param.extract_from(dict).as_string();
+        if (account.empty())
+        {
+            throw std::runtime_error{"account could not be found"};
+        }
+    }
+    else
+    {
+        throw std::runtime_error{"account could not be found"};
+    }
+
+    if (password_param.can_extract_from(dict))
+    {
+        password = password_param.extract_from(dict).as_string();
+    }
+}
+
+dummy::Connection::~Connection()
+{
+
+}
+
+std::string dummy::Connection::self_identifier()
+{
+    return account;
+}
+
+shared_ptr<messaging::PresenceManager> dummy::Connection::presence_manager()
+{
+    return presence_manager_;
+}
+
+shared_ptr<messaging::Messenger> dummy::Connection::messenger()
+{
+    return messenger_;
+}
+
+std::shared_ptr<messaging::GroupStarter> dummy::Connection::group_starter()
+{
+    return group_starter_;
+}
+
+void dummy::Connection::connect()
+{
+    LOG(INFO) << this << __PRETTY_FUNCTION__;
+
+    // initiate other components
+    messenger_ = Messenger::create(messenger_observer_, shared_from_this());
+    group_starter_ = dummy::GroupStarter::create(messenger_);
+
+    // Do something here to actually connect the account
+
+    set_status(Status::connecting, StatusChangedReason::requested);
+}
+
+void dummy::Connection::disconnect(messaging::Connection::StatusChangedReason reason)
+{
+    LOG(INFO) << this << __PRETTY_FUNCTION__;
+    try
+    {
+        set_status(Status::disconnected, reason);
+    }
+    catch (const std::runtime_error &e)
+    {
+        LOG(ERROR) << "disconnect failed: " << e.what();
+    }
+}
+
+void dummy::Connection::set_status(Status new_status, StatusChangedReason reason)
+{
+    try
+    {
+        announce_status_changed(new_status, reason);
+
+        switch (new_status)
+        {
+        case Status::connected:
+            break;
+        case Status::connecting:
+            break;
+        case Status::disconnected:
+            if (connector_) {
+                connector_->release_connection(shared_from_this());
+            }
+            break;
+        default:
+            break;
+        }
+    }
+    catch (const std::runtime_error &e)
+    {
+        LOG(ERROR) << "set_status failed: " << e.what();
+    }
+}
+
+std::string dummy::Connection::normalize_identifier(const std::string &id)
+{
+    // dummy plugin does not require normalization
+    return id;
+}
+
+bool dummy::Connection::is_valid_identifier(const std::string &id)
+{
+    return !id.empty();
+}

=== added file 'examples/mfw-plugin-dummy/src/dummy/connector.cpp'
--- examples/mfw-plugin-dummy/src/dummy/connector.cpp	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/src/dummy/connector.cpp	2017-03-22 21:22:50 +0000
@@ -0,0 +1,95 @@
+#include <dummy/connector.h>
+#include <dummy/connection.h>
+
+#include <messaging/enumerator.h>
+#include <messaging/parameter.h>
+#include <messaging/plugin.h>
+
+#include <messaging/boost/variant.h>
+
+#include <glog/logging.h>
+
+std::shared_ptr<dummy::Connector> dummy::Connector::create()
+{
+    return std::shared_ptr<Connector>(new Connector());
+}
+
+dummy::Connector::Connector() :
+    params_enum_{
+          std::vector<messaging::Parameter>{messaging::Parameter{"account", "s", messaging::Parameter::Flags::required|messaging::Parameter::Flags::required_for_registration},
+                                            messaging::Parameter{"password", "s", messaging::Parameter::Flags::secret}}}
+{
+    mutable_instance() = this;
+}
+
+dummy::Connector::~Connector()
+{
+    mutable_instance() = nullptr;
+}
+
+void dummy::Connector::run()
+{
+   LOG(INFO) << "dummy::Connector::run";
+}
+
+void dummy::Connector::stop()
+{
+   LOG(INFO) << "dummy::Connector::stop";
+}
+
+std::shared_ptr<messaging::Connection> dummy::Connector::request_connection(const std::shared_ptr<messaging::Connection::Observer>& connection_observer,
+                                                                    const std::shared_ptr<messaging::Messenger::Observer>& messenger_observer,
+                                                                    const std::shared_ptr<messaging::PresenceManager::Observer>& presence_observer,
+                                                                    const messaging::Dictionary<std::string, messaging::Variant>& dict)
+{    
+    auto connection = std::make_shared<dummy::Connection>(connection_observer,
+                                       messenger_observer,
+                                       presence_observer,
+                                       dict,
+                                       this);
+    connections_.insert(connection);
+    return connection;
+}
+
+void dummy::Connector::release_connection(const std::weak_ptr<Connection>& connection)
+{
+    auto it = connections_.find(connection);
+    if (it != connections_.end())
+    {
+        connections_.erase(it);
+    }
+}
+
+const messaging::Enumerator<messaging::Parameter>& dummy::Connector::parameters() const
+{
+    return params_enum_;
+}
+
+bool dummy::Connector::network_monitor_enabled()
+{
+    return false;
+}
+
+dummy::Connector*& dummy::Connector::mutable_instance()
+{
+    static Connector* instance{nullptr};
+    return instance;
+}
+
+dummy::Connector* dummy::Connector::instance()
+{
+    return mutable_instance();
+}
+
+// Integrate with the messaging fw plugin runtime.
+messaging::Connector* MESSAGING_FW_CREATE_FUNCTION()
+{
+    static auto instance = dummy::Connector::create();
+    return instance.get();
+}
+
+void MESSAGING_FW_DESTROY_FUNCTION(messaging::Connector*)
+{
+    // Empty on purpose.
+}
+

=== added file 'examples/mfw-plugin-dummy/src/dummy/contact_chat.cpp'
--- examples/mfw-plugin-dummy/src/dummy/contact_chat.cpp	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/src/dummy/contact_chat.cpp	2017-03-22 21:22:50 +0000
@@ -0,0 +1,58 @@
+#include <dummy/contact_chat.h>
+
+#include <messaging/message.h>
+#include <messaging/recipient.h>
+
+#include <glog/logging.h>
+
+using namespace std;
+
+shared_ptr<dummy::ContactChat> dummy::ContactChat::create(const User& user,
+                                                    const shared_ptr<messaging::Chat::Observer>& observer)
+{
+    shared_ptr<dummy::ContactChat> chat(new dummy::ContactChat{user, observer});
+    return chat;
+}
+
+shared_ptr<dummy::ContactChat> dummy::ContactChat::create(const messaging::User::shared_ptr& user,
+                                                    const shared_ptr<messaging::Chat::Observer>& observer)
+{
+    shared_ptr<dummy::ContactChat> chat(new dummy::ContactChat{user, observer});
+    return chat;
+}
+
+dummy::ContactChat::ContactChat(const User& user,
+                             const shared_ptr<messaging::Chat::Observer>& observer)
+    : Chat{observer}
+    , recipient(user)
+{
+}
+
+dummy::ContactChat::ContactChat(const messaging::User::shared_ptr& user,
+                             const shared_ptr<messaging::Chat::Observer>& observer)
+        : ContactChat{User::from_recipient(user), observer}
+{
+}
+
+void dummy::ContactChat::mark_message_as_read(const string &alias)
+{
+    // Not supported on DUMMY
+}
+
+void dummy::ContactChat::start_typing()
+{
+    // Typing signal not supported on DUMMY
+}
+
+void dummy::ContactChat::end_typing()
+{
+    // Typing signal not supported on DUMMY
+}
+
+string dummy::ContactChat::send_message(const messaging::Message& message)
+{
+    // this method is called when the ui sends a message to any user or group
+    return string();
+}
+
+

=== added file 'examples/mfw-plugin-dummy/src/dummy/group_chat.cpp'
--- examples/mfw-plugin-dummy/src/dummy/group_chat.cpp	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/src/dummy/group_chat.cpp	2017-03-22 21:22:50 +0000
@@ -0,0 +1,50 @@
+#include <dummy/group_chat.h>
+#include <dummy/group_manager.h>
+
+#include <messaging/message.h>
+#include <messaging/group.h>
+#include <messaging/recipient.h>
+
+#include <glog/logging.h>
+
+std::shared_ptr<dummy::GroupChat> dummy::GroupChat::create(const std::shared_ptr<messaging::Group> &group,
+                                                     const std::shared_ptr<messaging::Chat::Observer>& observer)
+{
+    return std::shared_ptr<dummy::GroupChat>(new dummy::GroupChat{group, observer});
+}
+
+dummy::GroupChat::GroupChat(const std::shared_ptr<messaging::Group> &group,
+                         const std::shared_ptr<messaging::Chat::Observer>& observer)
+        : Chat{observer}
+        , channel_id(group->id())
+{
+}
+
+std::string dummy::GroupChat::send_message(const messaging::Message& message)
+{
+    // a message is being sent to this group
+    return std::string();
+}
+
+void dummy::GroupChat::mark_message_as_delivered(const std::string &message_token)
+{
+    LOG(INFO) << __PRETTY_FUNCTION__ << " token:" << message_token;
+}
+
+void dummy::GroupChat::mark_message_as_read(const std::string &alias)
+{
+}
+
+void dummy::GroupChat::start_typing()
+{
+}
+
+void dummy::GroupChat::end_typing()
+{
+}
+
+std::string dummy::GroupChat::id()
+{
+    return channel_id;
+}
+

=== added file 'examples/mfw-plugin-dummy/src/dummy/group_manager.cpp'
--- examples/mfw-plugin-dummy/src/dummy/group_manager.cpp	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/src/dummy/group_manager.cpp	2017-03-22 21:22:50 +0000
@@ -0,0 +1,114 @@
+#include <dummy/group_manager.h>
+
+#include <dummy/messenger.h>
+#include <dummy/group_chat.h>
+#include <dummy/connection.h>
+
+
+#include <messaging/group.h>
+#include <messaging/user.h>
+
+#include <glog/logging.h>
+
+
+std::shared_ptr<dummy::GroupManager> dummy::GroupManager::create(const std::shared_ptr<messaging::Group>& group,
+                                                           const std::shared_ptr<Messenger>& messenger)
+{
+    return std::shared_ptr<dummy::GroupManager>(new dummy::GroupManager{group, messenger});
+}
+
+dummy::GroupManager::GroupManager(const std::shared_ptr<messaging::Group>& group,
+                               const std::shared_ptr<Messenger>& messenger)
+        : messaging::GroupManager{}
+        , messenger_{messenger}
+        , id(group->id())
+        , creator(group->creator()->id())
+{
+}
+
+dummy::GroupManager::~GroupManager()
+{
+}
+
+void dummy::GroupManager::on_plugged(const std::weak_ptr<messaging::HasInterfaces> &where)
+{
+    auto sp = where.lock();
+    if (sp) {
+        chat_ = std::dynamic_pointer_cast<dummy::GroupChat>(sp);
+    }
+}
+
+std::string dummy::GroupManager::group_id()
+{
+    return id;
+}
+
+std::string dummy::GroupManager::group_title()
+{
+    return id;
+}
+
+std::string dummy::GroupManager::group_subject()
+{
+    return std::string{};
+}
+
+std::shared_ptr<messaging::Member> dummy::GroupManager::group_creator()
+{
+    return std::make_shared<messaging::Member>(creator);
+}
+
+std::set<std::string> dummy::GroupManager::group_admins()
+{
+    std::set<std::string> admins;
+
+    return admins;
+}
+
+messaging::Members dummy::GroupManager::members()
+{
+    return participants;
+}
+
+void dummy::GroupManager::set_observer(const std::shared_ptr<Observer> &observer)
+{
+    messaging::GroupManager::set_observer(observer);
+    announce_group_permissions_changed(messaging::GroupManager::permissions());
+}
+
+void dummy::GroupManager::change_group_title(const std::string &new_title)
+{
+}
+
+void dummy::GroupManager::change_group_subject(const std::string &new_subject)
+{
+
+}
+
+void dummy::GroupManager::add_members(const messaging::Members &members)
+{
+}
+
+void dummy::GroupManager::remove_members(const messaging::Members &members)
+{
+    for (auto member : members) {
+        if (member->id() == messenger_.lock()->connection->self_identifier()) {
+            leave_group();
+        }
+    }
+}
+
+void dummy::GroupManager::leave_group()
+{
+}
+
+void dummy::GroupManager::dissolve_group()
+{
+    // not supported on dummy
+}
+
+bool dummy::GroupManager::persistent()
+{
+    return false;
+}
+

=== added file 'examples/mfw-plugin-dummy/src/dummy/group_starter.cpp'
--- examples/mfw-plugin-dummy/src/dummy/group_starter.cpp	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/src/dummy/group_starter.cpp	2017-03-22 21:22:50 +0000
@@ -0,0 +1,85 @@
+#include <messaging/group.h>
+
+#include <dummy/group_starter.h>
+#include <dummy/group_manager.h>
+#include <dummy/messenger.h>
+
+#include <glog/logging.h>
+
+dummy::GroupStarter::GroupStarter(const std::shared_ptr<dummy::Messenger>& messenger)
+    : messaging::GroupStarter()
+    , messenger_{messenger}
+{
+}
+
+std::shared_ptr<dummy::GroupStarter> dummy::GroupStarter::create(const std::shared_ptr<dummy::Messenger>& messenger)
+{
+    std::shared_ptr<GroupStarter> group_starter(new GroupStarter{messenger});
+    return group_starter;
+}
+
+std::shared_ptr<messaging::GroupManager> dummy::GroupStarter::create_group(const std::shared_ptr<messaging::Group> &group)
+{
+    auto group_manager = dummy::GroupManager::create(group, messenger_.lock());
+    group_managers_[group->id()] = group_manager;
+
+    return group_manager;
+}
+
+std::shared_ptr<messaging::GroupManager> dummy::GroupStarter::accept_group(const std::shared_ptr<messaging::Group> &group)
+{
+    LOG(INFO) << __PRETTY_FUNCTION__ << " ,group_chat_id:" << group->id();
+
+    std::string group_chat_id = group->id();
+
+    if (group_chat_id.empty())
+    {
+        throw std::runtime_error{"Cannot accept an invitation with empty chat id"};
+    }
+
+    auto it = group_managers_.find(group_chat_id);
+    if (it != group_managers_.end())
+    {
+        return it->second;
+    }
+
+    auto group_manager = dummy::GroupManager::create(group, messenger_.lock());
+    group_managers_[group->id()] = group_manager;
+    return group_manager;
+}
+
+std::shared_ptr<messaging::GroupManager> dummy::GroupStarter::rejoin_group(const std::shared_ptr<messaging::Group> &group)
+{
+    LOG(INFO) << __PRETTY_FUNCTION__ << " group_chat_id:" << group->id();
+    std::string group_chat_id = group->id();
+    if (group_chat_id.empty())
+    {
+        throw std::runtime_error{"Cannot rejoin with empty chat id"};
+    }
+
+    auto it = group_managers_.find(group_chat_id);
+    if (it != group_managers_.end())
+    {
+        return it->second;
+    }
+
+    auto group_manager = dummy::GroupManager::create(group, messenger_.lock());
+    group_managers_[group->id()] = group_manager;
+
+    return group_manager;
+}
+
+void dummy::GroupStarter::reject_group(const std::shared_ptr<messaging::Group> &group)
+{
+    LOG(INFO) << __PRETTY_FUNCTION__ << " ,group_chat_id:" << group->id();
+}
+
+std::shared_ptr<messaging::Broadcast> dummy::GroupStarter::create_broadcast(const messaging::Members& recipients)
+{
+
+}
+
+std::map<std::string, std::shared_ptr<dummy::GroupManager>> dummy::GroupStarter::group_managers()
+{
+    return group_managers_;
+}

=== added file 'examples/mfw-plugin-dummy/src/dummy/messenger.cpp'
--- examples/mfw-plugin-dummy/src/dummy/messenger.cpp	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/src/dummy/messenger.cpp	2017-03-22 21:22:50 +0000
@@ -0,0 +1,71 @@
+#include <dummy/messenger.h>
+#include <dummy/group_chat.h>
+#include <dummy/contact_chat.h>
+#include <dummy/group_manager.h>
+#include <dummy/connection.h>
+
+#include <messaging/group.h>
+#include <messaging/user.h>
+#include <messaging/variant.h>
+
+#include <glog/logging.h>
+
+using namespace std;
+
+dummy::Messenger::Messenger(const std::shared_ptr<messaging::Messenger::Observer>& observer, const std::shared_ptr<dummy::Connection> &_connection)
+    : messaging::Messenger{observer}
+    , connection(_connection)
+{
+}
+
+std::shared_ptr<dummy::Messenger> dummy::Messenger::create(const std::shared_ptr<messaging::Messenger::Observer>& observer, const std::shared_ptr<dummy::Connection> &connection)
+{
+    std::shared_ptr<Messenger> messenger(new Messenger{observer, connection});
+    return messenger;
+}
+
+std::shared_ptr<messaging::Chat> dummy::Messenger::create_chat_with(const messaging::Recipient::shared_ptr& recipient,
+                                                                 const std::shared_ptr<messaging::Chat::Observer>& observer)
+{
+    switch (recipient->type())
+    {
+    case messaging::RecipientType::user:
+        LOG(INFO) << "Creating user chat" << recipient->id();
+        return dummy::ContactChat::create(std::dynamic_pointer_cast<messaging::User>(recipient), observer);
+    case messaging::RecipientType::group:
+        LOG(INFO) << "Creating group chat" << recipient->id();
+        return dummy::GroupChat::create(std::dynamic_pointer_cast<messaging::Group>(recipient), observer);
+    case messaging::RecipientType::broadcast:
+        LOG(ERROR) << "Broadcast chat not supported on DUMMY";
+        break;
+    }
+    return std::shared_ptr<messaging::Chat>();
+}
+
+void dummy::Messenger::send_delivery_notification(const std::shared_ptr<dummy::Message>& message)
+{
+
+}
+
+std::shared_ptr<dummy::GroupManager> dummy::Messenger::get_group_manager(const std::string &group_chat_id)
+{
+    auto chat = get_chat(group_chat_id);
+    if (not chat) {
+        return nullptr;
+    }
+
+    auto group_chat = dynamic_pointer_cast<dummy::GroupChat>(chat);
+    auto group_manager = group_chat->interface<messaging::GroupManager>();
+
+    if (not group_manager) {
+        LOG(ERROR) << "Could not find a valid group manager plugged to chat " << group_chat_id;
+        return nullptr;
+    }
+
+    return std::dynamic_pointer_cast<dummy::GroupManager>(group_manager);
+}
+    
+void dummy::Messenger::remove_chat(const std::string &chat_id)
+{
+    chats().erase(chat_id); 
+}

=== added file 'examples/mfw-plugin-dummy/src/dummy/presence_manager.cpp'
--- examples/mfw-plugin-dummy/src/dummy/presence_manager.cpp	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/src/dummy/presence_manager.cpp	2017-03-22 21:22:50 +0000
@@ -0,0 +1,59 @@
+#include <dummy/presence_manager.h>
+#include <dummy/user.h>
+#include <dummy/connector.h>
+
+#include <glog/logging.h>
+
+using namespace std;
+
+dummy::PresenceManager::PresenceManager(
+        const std::shared_ptr<messaging::PresenceManager::Observer>& observer,
+        Connector *connector)
+    : messaging::PresenceManager{observer}
+    , connector_{connector}
+    , statuses_{{"offline", messaging::StatusSpec{
+                                messaging::PresenceType::offline,
+                                messaging::StatusSpec::Flags::may_set_on_self &
+                                messaging::StatusSpec::Flags::can_have_message}},
+                {"available", messaging::StatusSpec{
+                                messaging::PresenceType::available,
+                                messaging::StatusSpec::Flags::may_set_on_self &
+                                messaging::StatusSpec::Flags::can_have_message}},
+                {"unknown", messaging::StatusSpec{
+                                messaging::PresenceType::unknown,
+                                messaging::StatusSpec::Flags::none}}}
+{
+}
+
+std::shared_ptr<dummy::PresenceManager> dummy::PresenceManager::create(const std::shared_ptr<messaging::PresenceManager::Observer>& observer,
+                                                                 Connector* connector)
+{
+    std::shared_ptr<PresenceManager> presence(new PresenceManager{observer, connector});
+    return presence;
+}
+
+messaging::PresenceManager::StatusMap dummy::PresenceManager::get_valid_statuses()
+{
+    return statuses_;
+}
+
+void dummy::PresenceManager::set_self_presence(const std::string&, const std::string&)
+{
+    throw std::logic_error{"Not implemented"};
+}
+
+void dummy::PresenceManager::request_presence(const std::shared_ptr<messaging::Recipient> &recipient)
+{
+
+}
+
+messaging::Presence dummy::PresenceManager::create_presence(const std::string& status, const std::string& status_message)
+{
+    auto it = statuses_.find(status);
+    if (it != statuses_.end())
+    {
+        return messaging::Presence{it->second.type, status, status_message};
+    }
+
+    throw std::logic_error{"Trying to create a presence from a not specified presence status"};
+}

=== added file 'examples/mfw-plugin-dummy/src/dummy/user.cpp'
--- examples/mfw-plugin-dummy/src/dummy/user.cpp	1970-01-01 00:00:00 +0000
+++ examples/mfw-plugin-dummy/src/dummy/user.cpp	2017-03-22 21:22:50 +0000
@@ -0,0 +1,14 @@
+#include <dummy/user.h>
+
+#include <messaging/user.h>
+
+dummy::User dummy::User::from_recipient(const std::shared_ptr<messaging::Recipient> &recipient)
+{
+    dummy::User user;
+    user.username = recipient->id();
+    return user;
+}
+
+messaging::Recipient::shared_ptr dummy::User::to_recipient() const
+{
+}