diff --git a/.gitignore b/.gitignore
index e190163..99f72db 100644
--- a/.gitignore
+++ b/.gitignore
@@ -16,3 +16,4 @@
/CopyQ-2.9.0.tar.gz
/CopyQ-3.0.0.tar.gz
/CopyQ-3.0.1.tar.gz
+/CopyQ-3.0.2.tar.gz
diff --git a/CopyQ-3.0.2/.gitignore b/CopyQ-3.0.2/.gitignore
new file mode 100644
index 0000000..645d1d5
--- /dev/null
+++ b/CopyQ-3.0.2/.gitignore
@@ -0,0 +1,49 @@
+# Generated CMake files
+CMakeFiles/
+CMakeCache.txt
+*.cmake
+
+# Generated Visual Studio files
+/plugins/Debug/
+/plugins/Release/
+/plugins/Win*/
+/Debug/
+/Release/
+/Win*/
+*.sln
+*.suo
+*.*sdf
+*.vc?proj*
+
+# Generated Makefiles
+/plugins/Makefile
+/plugins/*/Makefile
+/src/Makefile
+/Makefile
+
+# Generated Qt files
+/plugins/**/*.dir/
+/src/copyqcon.dir/
+/src/copyq.dir/
+/src/copyq_*.qm
+/src/copyq_*.qm.rule
+/src/qrc_copyq.cxx
+/src/translations.qrc
+/src/qrc_translations.cxx
+
+moc_*
+ui_*
+*.depends
+*.o
+*.dylib
+*.moc
+**/qrc_*.cpp
+/.qmake.cache
+/copyq.app
+copyq.pro.user
+.DS_Store
+.qmake.stash
+*.pyc
+*.dmg
+/build
+*.qm
diff --git a/CopyQ-3.0.2/.gitlab-ci.yml b/CopyQ-3.0.2/.gitlab-ci.yml
new file mode 100644
index 0000000..496d086
--- /dev/null
+++ b/CopyQ-3.0.2/.gitlab-ci.yml
@@ -0,0 +1,59 @@
+# Use latest Ubuntu LTS docker image.
+image: ubuntu:xenial
+
+variables:
+ BUILD_DIR: "build"
+ INSTALL_PREFIX: "copyq"
+ SCREENSHOT_DIR: "screenshots"
+ TESTS_LOG_DIR: "logs"
+
+build:
+ stage: build
+
+ before_script:
+ - utils/gitlab/build-before_script.sh
+
+ script:
+ - utils/gitlab/build-script.sh
+
+ # Upload installed application.
+ artifacts:
+ paths:
+ - "$INSTALL_PREFIX"
+
+ cache:
+ paths:
+ - build
+
+# Run simple tests (doesn't require GUI)
+test:
+ stage: test
+
+ before_script:
+ - utils/gitlab/test-before_script.sh
+
+ script:
+ - utils/gitlab/test-script.sh
+
+ dependencies:
+ - build
+
+# GUI tests (requires X11)
+test_gui:
+ stage: test
+
+ before_script:
+ - utils/gitlab/test_gui-before_script.sh
+
+ script:
+ - utils/gitlab/test_gui-script.sh
+
+ # Upload screenshots on failure.
+ artifacts:
+ when: on_failure
+ paths:
+ - "$SCREENSHOT_DIR"
+ - "$TESTS_LOG_DIR"
+
+ dependencies:
+ - build
diff --git a/CopyQ-3.0.2/.travis.yml b/CopyQ-3.0.2/.travis.yml
new file mode 100644
index 0000000..2b83315
--- /dev/null
+++ b/CopyQ-3.0.2/.travis.yml
@@ -0,0 +1,62 @@
+language: cpp
+
+matrix:
+ include:
+ - os: osx
+ compiler: clang
+
+ - os: linux
+ compiler: gcc
+ env:
+ - COMPILER=g++-4.8
+ - GCOV=gcov-4.8
+ addons:
+ apt:
+ sources:
+ - ubuntu-toolchain-r-test
+ packages:
+ - g++-4.8
+
+ - os: linux
+ compiler: clang
+ env:
+ - COMPILER=clang++-3.6
+ addons:
+ apt:
+ sources:
+ - ubuntu-toolchain-r-test
+ - llvm-toolchain-precise-3.6
+ packages:
+ - clang-3.6
+
+cache:
+ apt: true
+ ccache: true
+ directories:
+ - $HOME/.wheelhouse
+
+before_install:
+ - utils/travis/before-install-${TRAVIS_OS_NAME}.sh
+
+install:
+ - utils/travis/install-${TRAVIS_OS_NAME}.sh
+
+script:
+ - utils/travis/script-${TRAVIS_OS_NAME}.sh
+
+after_success:
+ - utils/travis/after_success-${TRAVIS_OS_NAME}.sh
+
+deploy:
+ provider: releases
+ api_key:
+ secure: Vax27ifQsc8SlTsLYVbxVJANDAxDroegN6nOPXCN1MLaoh4W2DQ/iGGx+waIOSYig8Sh+AUz2JhCFuMLMVqwFoWY2rxNPBrxhTBjm3aDhylbB+mRECnbInNb0kS3qv4lNDN6lHD4B6K01FWUUiHX14s2JQx4ut+KuwMxxhxyO4Y=
+ file: 'build/*.dmg'
+ file_glob: true
+ skip_cleanup: true
+ overwrite: true
+ on:
+ condition: "$TRAVIS_OS_NAME = osx"
+ tags: true
+ all_branches: true
+ repo: hluk/CopyQ
diff --git a/CopyQ-3.0.2/AUTHORS b/CopyQ-3.0.2/AUTHORS
new file mode 100644
index 0000000..28f09d3
--- /dev/null
+++ b/CopyQ-3.0.2/AUTHORS
@@ -0,0 +1,21 @@
+Adam Batkin
+Giacomo Margarito
+Greg Carp
+Ilya Plenne
+Jörg Thalheim
+Kim Jzhone
+Kos Ivantsov
+lightonflux
+Lukas Holecek
+Marjolein Hoekstra
+Martin Lepadusch
+Matt d'Entremont
+Michal Čihař
+Patricio M. Ros
+Robert Orzanna
+Ryan Wooden
+Scott Kostyshak
+Sebastian Schuberth
+Tomas Nilzon
+Wilfried Caruel
+x2357
diff --git a/CopyQ-3.0.2/CHANGES b/CopyQ-3.0.2/CHANGES
new file mode 100644
index 0000000..95a3278
--- /dev/null
+++ b/CopyQ-3.0.2/CHANGES
@@ -0,0 +1,461 @@
+v3.0.2
+- Added script functions for listing synchronized tabs and their paths
+- Fixed showing window on current screen
+- Fixed notification position with multiple screens
+- Fixed rendering items when scrolling
+- Fixed pasting from main window after switching tabs
+- Fixed copy/paste to some apps on OS X
+- Fixed focusing editor when closing completion popup on OS X
+- Fixed setting temporary file template from script
+
+v3.0.1
+- Install themes on OS X
+- Improve pasting to current window
+- Fix crash when the first tab is not loaded
+- Fix crash when reloading tab after closing editor
+- Fix item rendering and UI elements for high DPI displays
+- Fix window focus after closing menu or main window on OS X
+- Fix opening main window on current space on OS X
+- Fix pasting to some windows on OS X
+- Fix navigating item list
+- Fix getting boolean from checkbox in dialog()
+- Fix default move action for drag'n'drop
+- Fix exitting on logout when tray is disabled
+
+v3.0.0
+- Pinned and protected items
+- Export/import tabs, configuration and commands in one file
+- Create and modify commands from script
+- Create temporary files from script
+- Create notifications with buttons from script
+- Take screenshots using script
+- Allow to process lines on stdout from execute() scriptable using a function
+- Safer and faster encrypt/decrypt commands (need to be re-added)
+- Improved menu scriptable function
+- Improved icon sharpness
+- Improved plugin architecture
+- Improved logging and displaying log
+- Performance and memory consumption improvements
+- Implemented copy() on OS X
+- Fixed focusing menu and windows on OS X
+- Fixed configuration folder path for portable version on Windows
+- Fixed opening menu for a tab
+- Fixed using correct GPG version for encryption
+- Fixed tray menu position in KDE/Plasma
+
+v2.9.0
+- Set text style in editor
+- Search in editor
+- Quick help in completion popup menu for commands
+- Easier text selection in item preview
+- Show whole text and unscaled image in item preview
+- Improved pasting to windows on Linux/X11
+- Fixed global shortcuts at application start on Linux/X11
+- Fixed closing application from installer on Windows
+- Fixed showing item preview at start
+- Fixed saving position of new tabs and tab lists
+
+v2.8.3
+- Search items from tray menu
+- Added support for animated gifs (played when selected)
+- Added special formats for automatic commands to sync and store clipboard
+- Added auto-completion for command editor
+- Added scriptable variables for MIME types
+- Fix encryption with new OpenPGP
+- Fix passing big data to commands on Windows
+
+v2.8.2
+- Simplify appearance of items with notes and tags
+- Support for drag'n'dropping images to more applications
+- Added list widget for custom dialog
+- Fixed opening windows on current screen
+- Fixed tray icon appearance on Linux
+- Fixed focusing tray menu from command
+- Fixed dialog button translation on Windows
+- Fixed passing big data to commands
+
+v2.8.1
+- All Qt messages are logged
+- Fixed and improved commands for Tags plugin
+- Fixed removing last items when changing item limit
+- Fixed library paths for OS X
+- Fixed pasting items on Windows
+- Fixed copying from script on Windows
+
+v2.8.0
+- Insert images in editor
+- Show simple items options
+- Item preview window
+- Move to Qt 5 on Windows and newer Linux distros
+- Faster item content listing
+- Simple filter for Log dialog
+- Smooth icons on OS X
+- Fixed system icons
+- Fixed pasting animated images
+- Fixed occasional crashes when finalizing commands with Qt 5
+- Fixed opening log speed on Windows
+- Lithuanian translation
+
+v2.7.1
+- Colorize items with command
+- Drag'n'drop items in selection order
+- Fixed item selection with "next" and "previous" commands
+- Fixed encrypting/decrypting items on Windows
+- Fixed occasional client crashes at exit
+- Fixed editor command on OS X
+
+v2.7.0
+- Log accessible from GUI
+- Performance and memory usage improvements
+- Added scriptable function to set current tab (setCurrentTab())
+- Added scriptable function to modify new items (setData())
+- Appearance fixes
+- Simplified window management
+- Improved pasting to current window on Windows
+- Window geometry fixes
+- Command with Enter shortcut overrides item activate action
+
+v2.6.1
+- Moved configuration from registry on Windows
+- Fixed shortcuts on Windows
+- Fixed window geometry restoring
+
+v2.6.0
+- Show item notes in tray and window title
+- Removed broken console executable on Windows
+- Dutch translation
+- Added env() and setEnv() to access and modify environment variables
+- Access shortcut which activated command
+- Fixed closing the application at shutdown on Windows
+- Fixed some global shortcuts on Windows
+- Fixed capturing some shortcuts
+
+v2.5.0
+- Smarter tab name matching (ignore key hints '&')
+- Fixed omit passing global shortcuts to widgets
+- Fixed autostart option on Ubuntu
+- Fixed window geometry saving and restoring
+- Fixed reading binary input on Windows
+- Fixed clearing configuration
+
+v2.4.9
+- Added new light theme
+- Added scriptable function focused() to test main window focus
+- Customizable shortcuts for tab navigation
+- Extended item selection
+- Fixed tab expiration and updating context menu
+- Fixed passing text to command from action dialog
+
+v2.4.8
+- New command to show main window under mouse cursor or at a position with custom size
+- Hide clipboard content when "application/x-copyq-hidden" is "1"
+- "Copy next/previous item" command waits for clipboard to be set
+- Fixed updating window title and tray tool tip on X11
+- Fixed modifying multiple commands in Command dialog
+- Fixed implicit date to string conversions
+
+v2.4.7
+- Separate dialog for command help
+- Added scriptable function visible() to check main window visibility
+- Linux: Install bitmap icons for menus
+- Linux: Install AppData file
+- Allow to search for specific MIME types stored in items
+- Menu items and customizable shortcut for cycling item format
+- Fixed icon alignment
+- Fixed moving tabs with Qt 5
+- Fixed overriding socket file path (Linux and OS X)
+- Fixed "Paste as Plain Text" command (Windows and OS X)
+- Fixed tab tree layout and changing icons for tab groups
+- Fixed URL encoding
+
+v2.4.6
+- Fixed crash when removing command
+- Fixed encryption/decryption selected items
+- Fixed reading from standard input
+- GUI fixes for high-DPI displays
+
+v2.4.5
+- Option to save/restore history for filtering items
+- Clipboard changes with unchanged content is ignored
+- Notify about unsaved changes in command dialog
+- Use application icons from current icon theme on Linux
+- Simple error checking for user scripts
+- Fix blocked system shutdown on Linux/X11
+
+v2.4.4
+- Option to choose tab for storing clipboard
+- Fixed overriding mouse selection (Linux/X11)
+- Fixed window title updates from user commands
+- Fixed toggling window visibility with Qt 5
+- Minor GUI improvements and user command fixes
+
+v2.4.3
+- Plugin for tagging items
+- Plugins can provide script functions and commands
+- Improved automatic commands execution
+- Fixed gradients, transparency and other style improvements
+- Fixed decryption with newer version of GnuPG
+- Fixes for Qt 5 version
+
+v2.4.2
+- Send input data to execute()
+- Better clipboard encoding guessing
+- Set tab icon from commands using tabicon()
+- Fixed window title encoding on Windows
+- Fixed restoring window geometry
+- Performance fixes
+- Various bug and usability fixes
+- New logo
+
+v2.4.1
+- Added scriptable classes File and Dir
+- Added scriptable function settings() for saving custom user data
+- Improved dialog() command
+- Windows: Qt translated strings bundled with application
+- Fixed %1 in command
+- Fixed building with tests and Qt5
+
+v2.4.0
+- Separate dialog for user commands and global shortcuts
+- Search for item by row number
+- Command highlighting
+- More shortcuts can be mapped on Windows and X11
+- New "copy" command to copy from current window to clipboard
+- New "dialog" command to show dialog with custom input fields
+- Fixed crash on log out on Windows
+- Fixed clipboard monitoring on Windows
+- Fixed argument encoding from client on Windows
+- Fixed log output when printing messages from multiple processes
+- GUI fixes
+
+v2.3.0
+- Support for OS X
+- Japanese translation
+- Custom icons for tabs
+- Show item count next to each tab name (optional)
+- Added Process Manager for running and finished commands
+- Scripting improvements
+- Nicer format for copied user commands
+- GUI fixes
+
+v2.2.0
+- Custom system shortcuts for any user command
+- Drag'n'drop items to tabs
+- Options to set position and maximum size for notifications
+- Option to open windows on same desktop
+- Weblate service for translations (https://hosted.weblate.org/projects/copyq/master/)
+- Commands input and output is UTF-8 only (this fixes encoding issues on Windows)
+- Scripting engine improvements
+- Various GUI improvements and fixes
+- Fix main window position in various X11 window managers
+- Fix crashing with Oxygen GUI style
+- Fix storing images from clipboard on Windows
+- Various GUI improvements and fixes
+
+v2.1.0
+- French translation
+- Save/load and copy/paste user commands
+- Easier way to write longer commands and scripts
+- Remove formats in clipboard and item content dialogs
+- Command "toggle" focuses main window if unfocused (instead of closing)
+- Choose log file and amount of information to log
+- Lot of bugfixes and GUI improvements
+
+v2.0.1
+- Initial OS X support
+- Configuration moved into installed directory in Windows
+- Change language in configuration
+- New tool bar with item actions
+- Option to apply color theme in tabs, tool bar and menus
+- Allow to match items using a command
+- Focus output item of the last executed command
+- Allow to cancel exit if there are active commands
+- Removed option to hide menu bar (inconsistent behavior)
+- Fix showing lock icon in encrypted items
+
+v2.0.0
+- Synchronize items with files on disk
+- Faster tab loading and saving (data format was changed; only backward compatible)
+- User can limit size of text items
+- Opening external image editor fixed on Windows
+- New logo and website
+- Lot of other fixes
+
+v1.9.3
+- Item and tab encryption (using GnuPG)
+- FakeVim plugin for editing items (Vim editor emulation)
+- Drag'n'drop items from and to list
+- Improved appearance for notes
+- Improved search bar
+- New GUI for application and system-wide shortcuts
+- Option to unload tabs after an interval
+- Fixed item sizes and disabling font anti-aliasing
+- Major bug fixes (mainly for Windows) and performance improvements
+
+v1.9.2
+- Better performance
+- GUI improvements and bugfixes
+
+v1.9.1
+- Notifications -- customizable theme, timeout and position on screen
+- Optional notification for new clipboard content
+- Autostart option on Linux
+- Reset empty clipboard to previous content
+- More user-friendly item editor
+- Optional font antialiasing
+- Changed layout of configuration dialog
+- Other fixes
+
+v1.9.0
+- User notes
+- Improved appearance settings with some example themes
+- Tree view for tabs with groups
+- Sessions, i.e. run multiple independent instances
+- Lot of GUI improvements
+- Compatibility with Qt5
+- Bugfixes (crashing on Unity, icon colors etc.)
+
+v1.8.3
+- Options to hide tab bar and main menu
+- Automatic paste works with more applications under Linux/X11
+- Multi-monitor support
+- Lot of GUI fixes and improvements
+
+v1.8.2
+- Added shortcut to paste current and copy next/previous item
+- Bugfixes (paste to correct window, show tray menu on Unity, GUI and usability fixes)
+
+v1.8.1
+- Spanish translation
+- Option and system-wide shortcuts to temporarily disable clipboard storing
+- Option for main window transparency
+- Custom action on item activation
+- Various GUI improvements and bugfixes
+
+v1.8.0
+- New shortcuts: "Next/previous item to clipboard", "Paste as plain text"
+- Show clipboard content in main window title and tray tooltip
+- New options for commands (transform current item, close main window)
+- GUI enhancements, faster application start with many tabs and items, lot of bugfixes
+
+v1.7.5
+- User-settable editor for images
+- Command-line fixes for Windows
+- Commands for items of specified format (MIME type)
+- Tray menu fixes
+
+v1.7.4
+- Improved automatic paste from tray
+
+v1.7.3
+- Paste immediately after choosing tray item
+- German translation
+- Support for system-wide shortcuts on Qt 5
+
+v1.7.2
+- Clipboard content visible in tray tooltip
+
+v1.7.1
+- Bugfixes for text encoding
+
+v1.7.0
+- Plugins for saving and displaying clipboard content
+- Bugfixes (lot of refactoring and tests happened)
+
+v1.6.3
+- Some important bugfixes
+
+v1.6.2
+- Dialog for viewing item content
+- Improved tray menu
+- Minor GUI updates
+
+v1.6.1
+- Configurable tray menu
+- Lot of fixes in GUI and bugfixes
+
+v1.6.0
+- Highlight text and copy text in items
+- Interactive web view
+- Commands for any MIME type
+- e.g. it's possible to create QR Code image from an URL and save it in list
+- Pipe commands using '|' character
+
+v1.5.0
+- Option to use WebKit to render HTML
+- Wrap text with long lines
+- Faster list rendering
+- Icons from FontAwesome
+- Desktop icon on Linux
+
+v1.4.1
+- Support for other languages -- right now supports only English and Czech (any help is welcome)
+- New "insert" command
+- More safe item saving
+
+v1.4.0
+- lot of GUI Improvements, faster interaction
+- Automatic commands for matched windows (only on Linux and Windows)
+
+v1.3.3
+- GUI Improvements
+- New system-wide shortcuts
+- Item editing improved
+
+v1.3.2
+- Drag'n'Drop to clipboard
+- "Always on Top" option
+- Change tab bar position
+- Fix parsing arguments
+
+v1.3.1
+- GUI improvements
+- Mode for Vi navigation (h, j, k, l keys for movement)
+- Better performance
+
+v1.3.0
+- Import/export items to/from a file (not compatible with older saved format)
+- Use scripts to handle item history
+- Improved performance
+
+v1.2.5
+- Save/load items to/from a file
+- Sort selected items
+- Easier tab browsing (left/right arrow keys)
+- GUI improvements
+- More shortcut combinations work on Linux
+
+v1.2.4
+- Improved commands
+- Fixed and faster scrolling
+- Better tab manipulation
+
+v1.2.3
+- Bugfixes and major clean-up
+
+v1.2.2
+- Performance improved
+
+v1.2.1
+- Save items from commands in other tabs
+- Missing icons in Windows version
+
+v1.2.0
+- Appearance settings
+- Tab manipulation from command line
+- Copy/paste items from/to tabs
+- Faster searching
+
+v1.1.0
+- Better performance
+- New configuration options
+- Improved command line
+
+v1.0.2
+- Improved Windows compatibility
+- Global shortcuts
+- Automatic commands
+
+v1.0.1
+- Compatibility with different platforms
+
diff --git a/CopyQ-3.0.2/CMakeLists.txt b/CopyQ-3.0.2/CMakeLists.txt
new file mode 100644
index 0000000..c164438
--- /dev/null
+++ b/CopyQ-3.0.2/CMakeLists.txt
@@ -0,0 +1,202 @@
+cmake_minimum_required(VERSION 2.8.6)
+project(copyq)
+
+# C++11
+if (${CMAKE_MAJOR_VERSION}.${CMAKE_MINOR_VERSION} GREATER 3.1)
+ set(CMAKE_CXX_STANDARD 11)
+else()
+ set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++11")
+endif()
+
+if(CMAKE_BUILD_TYPE MATCHES Debug)
+ set(COPYQ_DEBUG ON)
+ add_definitions( -DCOPYQ_DEBUG )
+endif()
+
+OPTION(PEDANTIC "Enable all compiler warnings" OFF)
+
+# Options (cmake -LH)
+OPTION(WITH_QT5 "Use Qt 5 (disable to use Qt 4 instead)" ON)
+OPTION(WITH_TESTS "Run test cases from command line" ${COPYQ_DEBUG})
+OPTION(WITH_PLUGINS "Compile plugins" ON)
+# Linux-specific options
+if (${CMAKE_SYSTEM_NAME} MATCHES "Linux")
+ set(PLUGIN_INSTALL_PREFIX "${CMAKE_INSTALL_PREFIX}/${CMAKE_SHARED_MODULE_PREFIX}/copyq/plugins" CACHE PATH "Install path for plugins")
+ set(ICON_INSTALL_PREFIX "${CMAKE_INSTALL_PREFIX}/share/icons/hicolor/scalable/apps" CACHE PATH "Install path for icons")
+ set(ICON_INSTALL_PREFIX_TEMPLATE "${CMAKE_INSTALL_PREFIX}/share/icons/hicolor/%SIZE%/apps" CACHE PATH "Install path for icons (%SIZE% is icon size)")
+ set(THEME_INSTALL_PREFIX "${CMAKE_INSTALL_PREFIX}/share/copyq/themes" CACHE PATH "Install path for themes")
+ set(DESKTOP_INSTALL_PREFIX "${CMAKE_INSTALL_PREFIX}/share/applications" CACHE PATH "Install path for \"copyq.desktop\"")
+ set(APPDATA_INSTALL_PREFIX "${CMAKE_INSTALL_PREFIX}/share/appdata" CACHE PATH "Install path for \"copyq.appdata.xml\"")
+ set(TRANSLATION_INSTALL_PREFIX "${CMAKE_INSTALL_PREFIX}/share/copyq/translations" CACHE PATH "Install path for translations")
+endif()
+
+set(CMAKE_AUTOMOC ON)
+
+if (WITH_QT5)
+ cmake_minimum_required(VERSION 2.8.8)
+ find_package(Qt5Widgets)
+ if (NOT Qt5Widgets_FOUND)
+ message(FATAL_ERROR "Qt 5 is unavailable. To compile with Qt 4 use -DWITH_QT5=OFF.")
+ endif()
+ message(STATUS "Building with Qt 5.")
+else()
+ find_package(Qt4)
+ if (NOT QT4_FOUND)
+ # Try different executable name.
+ set(QT_QMAKE_EXECUTABLE "qmake-qt4")
+ find_package(Qt4)
+ if (NOT QT4_FOUND)
+ message(FATAL_ERROR "Qt 4 is unavailable. To compile with Qt 5 use -DWITH_QT5=ON.")
+ endif()
+ endif()
+ message(STATUS "Building with Qt 4.")
+endif()
+
+set(copyq_ICON_PREFIX src/images/icon)
+set(copyq_ICON_NORMAL src/images/icon.svg)
+set(copyq_ICON_BUSY src/images/icon-running.svg)
+set(copyq_DESKTOP shared/copyq.desktop)
+set(copyq_APPDATA shared/copyq.appdata.xml)
+
+# Be more strict while compiling debugging version
+if(CMAKE_COMPILER_IS_GNUCXX OR "${CMAKE_CXX_COMPILER_ID}" STREQUAL "Clang")
+ set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Wno-long-long")
+ set(CMAKE_CXX_FLAGS_DEBUG
+ "${CMAKE_CXX_FLAGS_DEBUG} -Wextra -Wall -pedantic -Wfloat-equal -Woverloaded-virtual -Wundef")
+endif()
+
+if (PEDANTIC)
+ if (CMAKE_COMPILER_IS_GNUCXX)
+ set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Wextra -Wall \
+ -Wsuggest-override \
+ -Wlogical-op \
+ -Wnoexcept \
+ -Wstrict-null-sentinel \
+ ")
+ else()
+ set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Weverything \
+ -Winconsistent-missing-override \
+ ")
+
+ set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} \
+ -Wno-c++98-compat \
+ -Wno-c++98-compat-pedantic \
+ -Wno-shadow-field-in-constructor \
+ -Wno-weak-vtables \
+ -Wno-disabled-macro-expansion \
+ -fcomment-block-commands=retval \
+ ")
+
+ # Disable errors from moc-generated files.
+ set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} \
+ -Wno-undefined-reinterpret-cast \
+ -Wno-missing-prototypes \
+ ")
+
+ # Disable errors from qrc-generated files.
+ set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} \
+ -Wno-exit-time-destructors \
+ -Wno-global-constructors \
+ ")
+ endif()
+
+ set(CMAKE_CXX_FLAGS
+ "${CMAKE_CXX_FLAGS} -pedantic -Werror \
+ -Wcast-align \
+ -Wcast-qual \
+ -Wctor-dtor-privacy \
+ -Wdisabled-optimization \
+ -Wformat=2 \
+ -Winit-self \
+ -Wmissing-declarations \
+ -Wmissing-include-dirs \
+ -Wold-style-cast \
+ -Woverloaded-virtual \
+ -Wredundant-decls \
+ -Wstrict-overflow=4 \
+ -Wundef \
+ ")
+
+ set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} \
+ -Wno-padded \
+ -Wno-switch-enum \
+ ")
+
+ # Disable Q_OBJECT macro warnings.
+ set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} \
+ -Wno-unused-member-function \
+ ")
+endif()
+
+if(WITH_TESTS)
+ message(STATUS "Building with tests.")
+
+ add_definitions( -DHAS_TESTS )
+
+ if (WITH_QT5)
+ list(APPEND copyq_Qt5_Modules Test)
+ else()
+ set(QT_USE_QTTEST TRUE)
+ endif()
+endif()
+
+# Get application version.
+if (EXISTS "version.txt")
+ file(STRINGS "version.txt" copyq_version)
+endif()
+
+if (NOT copyq_version)
+ find_package(Git)
+ if(GIT_FOUND)
+ execute_process(COMMAND
+ "${GIT_EXECUTABLE}" describe
+ WORKING_DIRECTORY "${CMAKE_SOURCE_DIR}"
+ RESULT_VARIABLE copyq_git_describe_result
+ OUTPUT_VARIABLE copyq_git_describe_output
+ ERROR_QUIET
+ OUTPUT_STRIP_TRAILING_WHITESPACE
+ )
+ if(copyq_git_describe_result EQUAL 0)
+ set(copyq_version "${copyq_git_describe_output}")
+ endif()
+ endif()
+endif()
+
+if (copyq_version)
+ message(STATUS "Building CopyQ version ${copyq_version}.")
+ add_definitions( -DCOPYQ_VERSION="${copyq_version}" )
+endif()
+
+if (${CMAKE_SYSTEM_NAME} MATCHES "Linux")
+ install(FILES ${copyq_ICON_NORMAL} DESTINATION ${ICON_INSTALL_PREFIX} RENAME copyq-normal.svg)
+ install(FILES ${copyq_ICON_BUSY} DESTINATION ${ICON_INSTALL_PREFIX} RENAME copyq-busy.svg)
+ install(FILES ${copyq_DESKTOP} DESTINATION ${DESKTOP_INSTALL_PREFIX})
+ install(FILES ${copyq_APPDATA} DESTINATION ${APPDATA_INSTALL_PREFIX})
+
+ foreach (copyq_ICON_EXTENT 16 22 24 32 48 64 128)
+ set(copyq_ICON_SIZE "${copyq_ICON_EXTENT}x${copyq_ICON_EXTENT}")
+ string(REPLACE "%SIZE%" "${copyq_ICON_SIZE}" copyq_ICON_TARGET_PREFIX "${ICON_INSTALL_PREFIX_TEMPLATE}")
+ foreach (copyq_ICON_TYPE "" "-normal" "-busy")
+ install(FILES "${copyq_ICON_PREFIX}${copyq_ICON_TYPE}_${copyq_ICON_SIZE}.png" DESTINATION "${copyq_ICON_TARGET_PREFIX}" RENAME "copyq${copyq_ICON_TYPE}.png")
+ endforeach()
+ endforeach()
+
+ set(copyq_THEME_INSTALL_PREFIX ${THEME_INSTALL_PREFIX})
+ file(GLOB copyq_THEMES shared/themes/*.ini)
+ install(FILES ${copyq_THEMES} DESTINATION ${THEME_INSTALL_PREFIX})
+
+ add_definitions( -DCOPYQ_ICON_PREFIX="${ICON_INSTALL_PREFIX}/copyq" )
+ add_definitions( -DCOPYQ_THEME_PREFIX="${THEME_INSTALL_PREFIX}" )
+ add_definitions( -DCOPYQ_PLUGIN_PREFIX="${PLUGIN_INSTALL_PREFIX}" )
+ add_definitions( -DCOPYQ_DESKTOP_PREFIX="${DESKTOP_INSTALL_PREFIX}" )
+ add_definitions( -DCOPYQ_TRANSLATION_PREFIX="${TRANSLATION_INSTALL_PREFIX}" )
+endif()
+
+add_definitions( -DQT_NO_CAST_TO_ASCII )
+
+add_subdirectory(src)
+
+if (WITH_PLUGINS)
+ add_subdirectory(plugins)
+endif()
+
diff --git a/CopyQ-3.0.2/Doxyfile b/CopyQ-3.0.2/Doxyfile
new file mode 100644
index 0000000..e98e4f7
--- /dev/null
+++ b/CopyQ-3.0.2/Doxyfile
@@ -0,0 +1,1716 @@
+# Doxyfile 1.7.4
+
+# 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 a sequence of words surrounded
+# by quotes) that should identify the project.
+
+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 =
+
+# 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 =
+
+# 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.
+
+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 = YES
+
+# 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 = 8
+
+# 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 =
+
+# 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 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 = NO
+
+# 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 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
+
+#---------------------------------------------------------------------------
+# 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 = NO
+
+# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
+# will be included in the documentation.
+
+EXTRACT_PRIVATE = YES
+
+# If the EXTRACT_STATIC tag is set to YES all static members of a file
+# will be included in the documentation.
+
+EXTRACT_STATIC = YES
+
+# 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 sectionname ... \endif.
+
+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
+
+# If the sources in your project are distributed over multiple directories
+# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy
+# in the documentation. The default is NO.
+
+SHOW_DIRECTORIES = NO
+
+# 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 , where is the value of
+# the FILE_VERSION_FILTER tag, and 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. The 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 =
+
+#---------------------------------------------------------------------------
+# 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 = src/include src
+
+# 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 = *.cpp *.h
+
+# 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 = NO
+
+# The EXCLUDE tag can be used to specify files and/or directories that should
+# 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.
+
+EXCLUDE =
+
+# The EXCLUDE_SYMLINKS tag can be used 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 =
+
+# 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 = NO
+
+# 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 , where
+# is the value of the INPUT_FILTER tag, and 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 =
+
+#---------------------------------------------------------------------------
+# 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 = NO
+
+# 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 and C++ 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 = NO
+
+# 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 = NO
+
+# 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 adviced 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 the tag is left blank doxygen
+# will generate a default style sheet. Note that doxygen will try to copy
+# the style sheet file to the HTML output directory, so don't put your own
+# stylesheet in the HTML output directory as well, or it will be erased!
+
+HTML_STYLESHEET =
+
+# 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 stylesheet 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_ALIGN_MEMBERS tag is set to YES, the members of classes,
+# files or namespaces will be aligned in HTML using tables. If set to
+# NO a bullet list will be used.
+
+HTML_ALIGN_MEMBERS = 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. For this to work a browser that supports
+# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox
+# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).
+
+HTML_DYNAMIC_SECTIONS = NO
+
+# 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
+#
+# Qt Help Project / Custom Filters.
+
+QHP_CUST_FILTER_ATTRS =
+
+# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
+# project's
+# filter section matches.
+#
+# Qt Help Project / Filter Attributes.
+
+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 at
+# top of each HTML page. The value NO (the default) enables the index and
+# the value YES disables it.
+
+DISABLE_INDEX = NO
+
+# 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 = 4
+
+# 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.
+
+GENERATE_TREEVIEW = NO
+
+# By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories,
+# and Class Hierarchy pages using a tree view instead of an ordered list.
+
+USE_INLINE_TREES = NO
+
+# 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 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 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.org site, so you can quickly see the result without installing
+# MathJax, but it is strongly recommended to install a local copy of MathJax
+# before deployment.
+
+MATHJAX_RELPATH = http://www.mathjax.org/mathjax
+
+# 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 = YES
+
+# When the SERVER_BASED_SEARCH tag is enabled the search engine will be
+# implemented using a PHP enabled web server instead of at the web client
+# using Javascript. Doxygen will generate the search PHP script and index
+# file to put on the web server. The advantage of the server
+# based approach is that it scales better to large projects and allows
+# full text search. The disadvantages are that it is more difficult to setup
+# and does not have live searching capabilities.
+
+SERVER_BASED_SEARCH = NO
+
+#---------------------------------------------------------------------------
+# 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 = NO
+
+# 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 = NO
+
+# 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
+
+#---------------------------------------------------------------------------
+# 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 stylesheet 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 = NO
+
+# 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.
+# Optionally an initial location of the external documentation
+# can be added for each tagfile. 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. If a location is present for each tag, the installdox tool
+# does not have to be run to correct the links.
+# 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 = YES
+
+# 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 = 0
+
+# By default doxygen will write a font called Helvetica to the output
+# directory and reference it in 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 = Ubuntu
+
+# 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 output directory to look for the
+# FreeSans.ttf font (which doxygen will put there itself). If you specify a
+# different font using DOT_FONTNAME you can set the path where dot
+# can find it using this tag.
+
+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
+# 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 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 = YES
+
+# 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, SHOW_DIRECTORIES 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.
+
+DOT_IMAGE_FORMAT = svg
+
+# 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 = NO
+
+# 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 = NO
+
+# 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
diff --git a/CopyQ-3.0.2/HACKING b/CopyQ-3.0.2/HACKING
new file mode 100644
index 0000000..e9594b5
--- /dev/null
+++ b/CopyQ-3.0.2/HACKING
@@ -0,0 +1 @@
+https://github.com/hluk/CopyQ/wiki/Development
diff --git a/CopyQ-3.0.2/INSTALL b/CopyQ-3.0.2/INSTALL
new file mode 100644
index 0000000..d01cde8
--- /dev/null
+++ b/CopyQ-3.0.2/INSTALL
@@ -0,0 +1,30 @@
+Steps to build and install
+==========================
+
+To build and install the application CMake is required (http://www.cmake.org/).
+
+On Ubuntu you'll need packages libqt4-dev, cmake, libxfixes-dev,
+libxtst-dev (optional; auto-paste into some applications),
+libqtwebkit-dev (optional; advanced HTML rendering).
+
+Build with following commands:
+
+ cmake .
+ make
+
+To install run (sudo is required for root privileges on Linux):
+
+ sudo make install
+
+
+Building and Packaging for OS X
+-------------------------------
+
+To build and install on OS X, you will need `qmake` version
+5.2 or greater. Build with the following commands:
+
+ ~/Qt/5.2.0/clang_64/bin/qmake CONFIG+=release WITH_WEBKIT=1
+ make copyq.app
+
+This will produce a self-contained application bundle `copyq.app`
+which can then be copied or moved into `/Applications`.
diff --git a/CopyQ-3.0.2/LICENSE b/CopyQ-3.0.2/LICENSE
new file mode 100644
index 0000000..94a9ed0
--- /dev/null
+++ b/CopyQ-3.0.2/LICENSE
@@ -0,0 +1,674 @@
+ GNU GENERAL PUBLIC LICENSE
+ Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc.
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+ The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works. By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users. We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors. You can apply it to
+your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+ To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights. Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received. You must make sure that they, too, receive
+or can get the source code. And you must show them these terms so they
+know their rights.
+
+ Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+ For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software. For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+ Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so. This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software. The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable. Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products. If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+ Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary. To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ TERMS AND CONDITIONS
+
+ 0. Definitions.
+
+ "This License" refers to version 3 of the GNU General Public License.
+
+ "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+ "The Program" refers to any copyrightable work licensed under this
+License. Each licensee is addressed as "you". "Licensees" and
+"recipients" may be individuals or organizations.
+
+ To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy. The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+ A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+ To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy. Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+ To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies. Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+ An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License. If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+ 1. Source Code.
+
+ The "source code" for a work means the preferred form of the work
+for making modifications to it. "Object code" means any non-source
+form of a work.
+
+ A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+ The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form. A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+ The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities. However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work. For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+ The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+ The Corresponding Source for a work in source code form is that
+same work.
+
+ 2. Basic Permissions.
+
+ All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met. This License explicitly affirms your unlimited
+permission to run the unmodified Program. The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work. This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+ You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force. You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright. Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+ Conveying under any other circumstances is permitted solely under
+the conditions stated below. Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+ 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+ No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+ When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+ 4. Conveying Verbatim Copies.
+
+ You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+ You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+ 5. Conveying Modified Source Versions.
+
+ You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+ a) The work must carry prominent notices stating that you modified
+ it, and giving a relevant date.
+
+ b) The work must carry prominent notices stating that it is
+ released under this License and any conditions added under section
+ 7. This requirement modifies the requirement in section 4 to
+ "keep intact all notices".
+
+ c) You must license the entire work, as a whole, under this
+ License to anyone who comes into possession of a copy. This
+ License will therefore apply, along with any applicable section 7
+ additional terms, to the whole of the work, and all its parts,
+ regardless of how they are packaged. This License gives no
+ permission to license the work in any other way, but it does not
+ invalidate such permission if you have separately received it.
+
+ d) If the work has interactive user interfaces, each must display
+ Appropriate Legal Notices; however, if the Program has interactive
+ interfaces that do not display Appropriate Legal Notices, your
+ work need not make them do so.
+
+ A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit. Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+ 6. Conveying Non-Source Forms.
+
+ You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+ a) Convey the object code in, or embodied in, a physical product
+ (including a physical distribution medium), accompanied by the
+ Corresponding Source fixed on a durable physical medium
+ customarily used for software interchange.
+
+ b) Convey the object code in, or embodied in, a physical product
+ (including a physical distribution medium), accompanied by a
+ written offer, valid for at least three years and valid for as
+ long as you offer spare parts or customer support for that product
+ model, to give anyone who possesses the object code either (1) a
+ copy of the Corresponding Source for all the software in the
+ product that is covered by this License, on a durable physical
+ medium customarily used for software interchange, for a price no
+ more than your reasonable cost of physically performing this
+ conveying of source, or (2) access to copy the
+ Corresponding Source from a network server at no charge.
+
+ c) Convey individual copies of the object code with a copy of the
+ written offer to provide the Corresponding Source. This
+ alternative is allowed only occasionally and noncommercially, and
+ only if you received the object code with such an offer, in accord
+ with subsection 6b.
+
+ d) Convey the object code by offering access from a designated
+ place (gratis or for a charge), and offer equivalent access to the
+ Corresponding Source in the same way through the same place at no
+ further charge. You need not require recipients to copy the
+ Corresponding Source along with the object code. If the place to
+ copy the object code is a network server, the Corresponding Source
+ may be on a different server (operated by you or a third party)
+ that supports equivalent copying facilities, provided you maintain
+ clear directions next to the object code saying where to find the
+ Corresponding Source. Regardless of what server hosts the
+ Corresponding Source, you remain obligated to ensure that it is
+ available for as long as needed to satisfy these requirements.
+
+ e) Convey the object code using peer-to-peer transmission, provided
+ you inform other peers where the object code and Corresponding
+ Source of the work are being offered to the general public at no
+ charge under subsection 6d.
+
+ A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+ A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling. In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage. For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product. A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+ "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source. The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+ If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information. But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+ The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed. Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+ Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+ 7. Additional Terms.
+
+ "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law. If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+ When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it. (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.) You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+ Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+ a) Disclaiming warranty or limiting liability differently from the
+ terms of sections 15 and 16 of this License; or
+
+ b) Requiring preservation of specified reasonable legal notices or
+ author attributions in that material or in the Appropriate Legal
+ Notices displayed by works containing it; or
+
+ c) Prohibiting misrepresentation of the origin of that material, or
+ requiring that modified versions of such material be marked in
+ reasonable ways as different from the original version; or
+
+ d) Limiting the use for publicity purposes of names of licensors or
+ authors of the material; or
+
+ e) Declining to grant rights under trademark law for use of some
+ trade names, trademarks, or service marks; or
+
+ f) Requiring indemnification of licensors and authors of that
+ material by anyone who conveys the material (or modified versions of
+ it) with contractual assumptions of liability to the recipient, for
+ any liability that these contractual assumptions directly impose on
+ those licensors and authors.
+
+ All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10. If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term. If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+ If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+ Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+ 8. Termination.
+
+ You may not propagate or modify a covered work except as expressly
+provided under this License. Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+ However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+ Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+ Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License. If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+ 9. Acceptance Not Required for Having Copies.
+
+ You are not required to accept this License in order to receive or
+run a copy of the Program. Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance. However,
+nothing other than this License grants you permission to propagate or
+modify any covered work. These actions infringe copyright if you do
+not accept this License. Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+ 10. Automatic Licensing of Downstream Recipients.
+
+ Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License. You are not responsible
+for enforcing compliance by third parties with this License.
+
+ An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations. If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+ You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License. For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+ 11. Patents.
+
+ A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based. The
+work thus licensed is called the contributor's "contributor version".
+
+ A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version. For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+ Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+ In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement). To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+ If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients. "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+ If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+ A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License. You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+ Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+ 12. No Surrender of Others' Freedom.
+
+ If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all. For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+ 13. Use with the GNU Affero General Public License.
+
+ Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work. The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+ 14. Revised Versions of this License.
+
+ The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+ Each version is given a distinguishing version number. If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation. If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+ If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+ Later license versions may give you additional or different
+permissions. However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+ 15. Disclaimer of Warranty.
+
+ THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+ 16. Limitation of Liability.
+
+ IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+ 17. Interpretation of Sections 15 and 16.
+
+ If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+ END OF TERMS AND CONDITIONS
+
+ How to Apply These Terms to Your New Programs
+
+ If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+
+ Copyright (C)
+
+ 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 3 of the License, 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.
+
+ You should have received a copy of the GNU General Public License
+ along with this program. If not, see .
+
+Also add information on how to contact you by electronic and paper mail.
+
+ If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+ Copyright (C)
+ This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License. Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+ You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+.
+
+ The GNU General Public License does not permit incorporating your program
+into proprietary programs. If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library. If this is what you want to do, use the GNU Lesser General
+Public License instead of this License. But first, please read
+.
diff --git a/CopyQ-3.0.2/README.md b/CopyQ-3.0.2/README.md
new file mode 100644
index 0000000..803014f
--- /dev/null
+++ b/CopyQ-3.0.2/README.md
@@ -0,0 +1,210 @@
+# CopyQ
+
+[![Translation Status](https://hosted.weblate.org/widgets/copyq/-/svg-badge.svg)](https://hosted.weblate.org/engage/copyq/?utm_source=widget)
+[![Build Status](https://travis-ci.org/hluk/CopyQ.svg?branch=master)](https://travis-ci.org/hluk/CopyQ)
+[![Windows Build Status](https://ci.appveyor.com/api/projects/status/github/hluk/copyq?branch=master&svg=true)](https://ci.appveyor.com/project/hluk/copyq)
+[![Coverage Status](https://coveralls.io/repos/hluk/CopyQ/badge.svg?branch=master)](https://coveralls.io/r/hluk/CopyQ?branch=master)
+
+CopyQ is advanced clipboard manager with editing and scripting features.
+- [Downloads](https://github.com/hluk/CopyQ/releases)
+- [Web Site](https://hluk.github.io/CopyQ/)
+- [Wiki](https://github.com/hluk/CopyQ/wiki)
+- [Mailing List](https://groups.google.com/group/copyq)
+- [Bug Reports](https://github.com/hluk/CopyQ/issues)
+- [Donate](https://www.bountysource.com/teams/copyq)
+- [Scripting Reference](https://github.com/hluk/CopyQ/blob/master/src/scriptable/README.md)
+
+## Overview
+
+CopyQ monitors system clipboard and saves its content in customized tabs.
+Saved clipboard can be later copied and pasted directly into any application.
+
+Items can be:
+
+* edited with internal editor or with preferred text editor,
+* moved to other tabs,
+* drag'n'dropped to applications,
+* marked with tag or a note,
+* passed to or changed by custom commands,
+* or simply removed.
+
+## Features
+
+* Support for Linux, Windows and OS X 10.9+
+* Store text, HTML, images or any other custom formats
+* Quickly browse and filter items in clipboard history
+* Sort, create, edit, remove, copy/paste, drag'n'drop items in tabs
+* Add notes or tags to items
+* System-wide shortcuts with customizable commands
+* Paste items with shortcut or from tray or main window
+* Fully customizable appearance
+* Advanced command-line interface and scripting
+* Ignore clipboard copied from some windows or containing some text
+* Support for simple Vim-like editor and shortcuts
+* Many more features
+
+## Install and Run
+
+To install CopyQ, use the binary package or installer provided for your system. For system-specific information, please see below. For unlisted systems, please follow the instructions in
+[INSTALL](https://github.com/hluk/CopyQ/blob/master/INSTALL) to build the
+application.
+
+### Windows
+
+On Windows you can install [Chocolatey package](https://chocolatey.org/packages/copyq).
+
+### Ubuntu
+
+Install and keep CopyQ always up to date by running the following three commands from the terminal:
+
+```bash
+$ sudo add-apt-repository ppa:hluk/copyq
+$ sudo apt update
+$ sudo apt install copyq
+```
+
+### OS X
+
+On OS X you can use [Homebrew](https://brew.sh/) to install the app.
+
+```bash
+brew cask install copyq
+```
+
+## Using the App
+
+To start the application double-click the program icon or run `copyq`.
+
+The list with clipboard history is accessible by clicking on system tray icon
+or running `copyq toggle`.
+
+Copying text or image to clipboard will create new item in the list.
+
+Selected items can be:
+* edited (`F2`),
+* removed (`Delete`),
+* sorted (`Ctrl+Shift+S`, `Ctrl+Shift+R`),
+* moved around (with mouse or `Ctrl+Up/Down`) or
+* copied back to clipboard (`Enter`, `Ctrl+V`).
+
+All items will be restored when application is started next time.
+
+To exit the application select Exit from tray menu or press Ctrl-Q keys in the
+application window.
+
+Read more:
+- [Basic Usage](https://github.com/hluk/CopyQ/wiki/Basic-Usage)
+- [Keyboard](https://github.com/hluk/CopyQ/wiki/Keyboard)
+
+### Adding Funcionality
+
+To create custom action that can be executed
+from menu, with shortcut or when clipboard changes:
+- go to Command dialog (`F6` shortcut),
+- click Add button and select predefined command or create new one,
+- optionally change the command details (shortcut, name),
+- click OK to save the command.
+
+One of very useful predefined commands there is "Show/hide main window".
+
+Read more:
+- [Writing Commands](https://github.com/hluk/CopyQ/wiki/Writing-Commands-and-Adding-Functionality)
+- [CopyQ Commands Repository](https://github.com/hluk/copyq-commands)
+
+### Command Line
+
+CopyQ has powerful command line and scripting interface.
+
+Note: The main application must be running to be able to issue commands using
+command line.
+
+Print help for some useful command line arguments:
+
+ copyq --help
+ copyq --help add
+
+Insert some texts to the history:
+
+ copyq add "first item" "second item" "third item"
+
+Print content of the first three items:
+
+ copyq read 0 1 2
+ copyq separator "," read 0 1 2
+
+Show current clipboard content:
+
+ copyq clipboard
+ copyq clipboard text/html
+ copyq clipboard \? # lists formats in clipboard
+
+Copy text to the clipboard:
+
+ copyq copy "Some Text"
+
+Load file content into clipboard:
+
+ copyq copy - < file.txt
+ copyq copy text/html < index.html
+ copyq copy image/jpeg - < image.jpg
+
+Create an image items:
+
+ copyq write image/gif - < image.gif
+ copyq write image/svg - < image.svg
+
+Read more:
+- [Scripting](https://github.com/hluk/CopyQ/wiki/Scripting)
+- [Scripting Reference](https://github.com/hluk/CopyQ/blob/master/src/scriptable/README.md)
+
+## Build from Source Code
+
+To build the application from source code, first install the required dependencies:
+- [Git](https://git-scm.com/)
+- [CMake](https://cmake.org/download/)
+- [Qt](https://download.qt.io/archive/qt/)
+- Optionally on Linux/X11: development files and libraries for [Xtst](https://t2-project.org/packages/libxtst.html) and [Xfixes](https://www.x.org/archive/X11R7.5/doc/man/man3/Xfixes.3.html)
+- Optionally [QtWebKit](https://trac.webkit.org/wiki/QtWebKit) (more advanced HTML rendering)
+
+### Ubuntu
+
+#### Install Dependencies
+
+```bash
+sudo apt install \
+ git cmake \
+ qtbase5-private-dev \
+ qtscript5-dev \
+ qttools5-dev \
+ qttools5-dev-tools \
+ libqt5svg5-dev \
+ libxfixes-dev \
+ libxtst-dev \
+ libqt5svg5
+```
+
+#### Build the App
+
+Change install prefix if needed:
+
+```bash
+git clone https://github.com/hluk/CopyQ.git
+cd CopyQ
+cmake -DCMAKE_INSTALL_PREFIX=/usr/local .
+make
+```
+
+#### Install the App
+
+```bash
+sudo make install
+```
+
+## Contributions
+
+You can help translate the application (click the banner below)
+or help [fix issues and implement new features](https://github.com/hluk/CopyQ/issues).
+
+[![Translations](https://hosted.weblate.org/widgets/copyq/-/287x66-white.png)](https://hosted.weblate.org/engage/copyq/?utm_source=widget)
+
+See also [Development](https://github.com/hluk/CopyQ/wiki/Development).
diff --git a/CopyQ-3.0.2/appveyor.yml b/CopyQ-3.0.2/appveyor.yml
new file mode 100644
index 0000000..69ccef5
--- /dev/null
+++ b/CopyQ-3.0.2/appveyor.yml
@@ -0,0 +1,46 @@
+# Configuration file for AppVeyor CI
+configuration: Release
+
+cache:
+ - build
+
+environment:
+ VCINSTALLDIR: C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\
+
+ matrix:
+ - QTDIR: C:\Qt\5.7\mingw53_32
+ CMAKE_GENERATOR: MinGW Makefiles
+ MINGW_PATH: C:\Qt\Tools\mingw530_32
+
+ - QTDIR: C:\Qt\5.7\msvc2015
+ CMAKE_GENERATOR: Visual Studio 14 2015
+ VC_VARS_ARCH: x86
+
+ - QTDIR: C:\Qt\5.7\msvc2015_64
+ CMAKE_GENERATOR: Visual Studio 14 2015 Win64
+ VC_VARS_ARCH: amd64
+
+# Parameters for default build commands (build_script is used instead).
+build:
+
+install:
+- utils\appveyor\install.bat
+
+before_build:
+- utils\appveyor\before_build.bat
+
+build_script:
+- utils\appveyor\build_script.bat
+
+after_build:
+- utils\appveyor\after_build.bat
+
+artifacts:
+- path: 'copyq*.zip'
+ name: CopyQ Portable
+
+- path: 'copyq-*-setup.exe'
+ name: CopyQ Setup
+
+matrix:
+ fast_finish: true # set this flag to immediately finish build once one of the jobs fails.
diff --git a/CopyQ-3.0.2/common.pri b/CopyQ-3.0.2/common.pri
new file mode 100644
index 0000000..2ad2720
--- /dev/null
+++ b/CopyQ-3.0.2/common.pri
@@ -0,0 +1,9 @@
+CONFIG += c++11
+
+macx {
+ QMAKE_MACOSX_DEPLOYMENT_TARGET = 10.9
+ QMAKE_MAC_SDK = macosx # work around QTBUG-41238
+
+ # Only Intel binaries are accepted so force this
+ CONFIG += x86
+}
diff --git a/CopyQ-3.0.2/copyq b/CopyQ-3.0.2/copyq
new file mode 100755
index 0000000..548b1fc
Binary files /dev/null and b/CopyQ-3.0.2/copyq differ
diff --git a/CopyQ-3.0.2/copyq.lang b/CopyQ-3.0.2/copyq.lang
new file mode 100644
index 0000000..2d79208
--- /dev/null
+++ b/CopyQ-3.0.2/copyq.lang
@@ -0,0 +1,22 @@
+%lang(ar) /usr/share/copyq/locale/copyq_ar.qm
+%lang(cs) /usr/share/copyq/locale/copyq_cs.qm
+%lang(da) /usr/share/copyq/locale/copyq_da.qm
+%lang(de) /usr/share/copyq/locale/copyq_de.qm
+%lang(es) /usr/share/copyq/locale/copyq_es.qm
+%lang(fr) /usr/share/copyq/locale/copyq_fr.qm
+%lang(hu) /usr/share/copyq/locale/copyq_hu.qm
+%lang(it) /usr/share/copyq/locale/copyq_it.qm
+%lang(ja) /usr/share/copyq/locale/copyq_ja.qm
+%lang(lt) /usr/share/copyq/locale/copyq_lt.qm
+%lang(nb) /usr/share/copyq/locale/copyq_nb.qm
+%lang(nl) /usr/share/copyq/locale/copyq_nl.qm
+%lang(pl) /usr/share/copyq/locale/copyq_pl.qm
+%lang(pt_BR) /usr/share/copyq/locale/copyq_pt_BR.qm
+%lang(pt_PT) /usr/share/copyq/locale/copyq_pt_PT.qm
+%lang(ru) /usr/share/copyq/locale/copyq_ru.qm
+%lang(sk) /usr/share/copyq/locale/copyq_sk.qm
+%lang(sv) /usr/share/copyq/locale/copyq_sv.qm
+%lang(tr) /usr/share/copyq/locale/copyq_tr.qm
+%lang(uk) /usr/share/copyq/locale/copyq_uk.qm
+%lang(zh_CN) /usr/share/copyq/locale/copyq_zh_CN.qm
+%lang(zh_TW) /usr/share/copyq/locale/copyq_zh_TW.qm
diff --git a/CopyQ-3.0.2/copyq.pro b/CopyQ-3.0.2/copyq.pro
new file mode 100644
index 0000000..c77903d
--- /dev/null
+++ b/CopyQ-3.0.2/copyq.pro
@@ -0,0 +1,69 @@
+include("./common.pri")
+
+TEMPLATE = subdirs
+
+# generate cache file for build
+cache()
+
+DEFINES += QT_NO_CAST_TO_ASCII
+SUBDIRS += src \
+ plugins
+TRANSLATIONS = \
+ translations/copyq_ar.ts \
+ translations/copyq_cs.ts \
+ translations/copyq_da.ts \
+ translations/copyq_de.ts \
+ translations/copyq_es.ts \
+ translations/copyq_fr.ts \
+ translations/copyq_hu.ts \
+ translations/copyq_it.ts \
+ translations/copyq_ja.ts \
+ translations/copyq_lt.ts \
+ translations/copyq_nb.ts \
+ translations/copyq_nl.ts \
+ translations/copyq_pl.ts \
+ translations/copyq_pt_PT.ts \
+ translations/copyq_pt_BR.ts \
+ translations/copyq_ru.ts \
+ translations/copyq_sk.ts \
+ translations/copyq_sv.ts \
+ translations/copyq_tr.ts \
+ translations/copyq_uk.ts \
+ translations/copyq_zh_CN.ts \
+ translations/copyq_zh_TW.ts
+
+macx {
+ # Package the CopyQ plugins into the app bundle
+ package_plugins.commands = \
+ mkdir -p copyq.app/Contents/PlugIns/copyq/ ; \
+ cp plugins/*.dylib copyq.app/Contents/PlugIns/copyq/
+ package_plugins.depends = sub-plugins sub-src
+ QMAKE_EXTRA_TARGETS += package_plugins
+
+ # Package the Qt frameworks into the app bundle
+ package_frameworks.commands = \
+ test -e copyq.app/Contents/Frameworks/QtCore.framework \
+ || $$dirname(QMAKE_QMAKE)/macdeployqt copyq.app
+ package_frameworks.target = copyq.app/Contents/Frameworks/QtCore.framework
+ package_frameworks.depends = sub-src sub-plugins package_plugins
+ QMAKE_EXTRA_TARGETS += package_frameworks
+
+ # Package the translations
+ package_translations.commands = \
+ $$dirname(QMAKE_QMAKE)/lrelease $$_PRO_FILE_PWD_/copyq.pro && \
+ mkdir -p copyq.app/Contents/Resources/translations && \
+ cp $$_PRO_FILE_PWD_/translations/*.qm copyq.app/Contents/Resources/translations
+ QMAKE_EXTRA_TARGETS += package_translations
+
+ # Package the themes
+ package_themes.commands = \
+ mkdir -p copyq.app/Contents/Resources/themes && \
+ cp $$_PRO_FILE_PWD_/shared/themes/*.ini copyq.app/Contents/Resources/themes
+ QMAKE_EXTRA_TARGETS += package_themes
+
+ # Rename to CopyQ.app to make it look better
+ bundle_mac.depends = package_frameworks package_plugins package_translations package_themes
+ bundle_mac.target = CopyQ.app
+ bundle_mac.commands = mv copyq.app CopyQ.app
+ QMAKE_EXTRA_TARGETS += bundle_mac
+}
diff --git a/CopyQ-3.0.2/debian/changelog b/CopyQ-3.0.2/debian/changelog
new file mode 100644
index 0000000..d6809bf
--- /dev/null
+++ b/CopyQ-3.0.2/debian/changelog
@@ -0,0 +1,5 @@
+copyq (2.9.0~xenial) xenial; urgency=medium
+
+ * v2.9.0
+
+ -- Lukas Holecek Fri, 10 Mar 2017 10:10:00 +0200
diff --git a/CopyQ-3.0.2/debian/compat b/CopyQ-3.0.2/debian/compat
new file mode 100644
index 0000000..ec63514
--- /dev/null
+++ b/CopyQ-3.0.2/debian/compat
@@ -0,0 +1 @@
+9
diff --git a/CopyQ-3.0.2/debian/control b/CopyQ-3.0.2/debian/control
new file mode 100644
index 0000000..f925c66
--- /dev/null
+++ b/CopyQ-3.0.2/debian/control
@@ -0,0 +1,45 @@
+Source: copyq
+Section: misc
+Priority: optional
+Maintainer: Lukas Holecek
+Build-Depends: debhelper (>= 9), cmake
+ ,qtbase5-private-dev
+ ,qtscript5-dev
+ ,qttools5-dev
+ ,qttools5-dev-tools
+ ,libqt5svg5-dev
+ ,libxfixes-dev
+ ,libxtst-dev
+Standards-Version: 3.9.7
+Homepage: https://hluk.github.io/CopyQ/
+Vcs-Browser: https://github.com/hluk/CopyQ
+Vcs-Git: https://github.com/hluk/CopyQ.git
+
+Package: copyq
+Architecture: any
+Depends: ${misc:Depends}, ${shlibs:Depends}, libqt5svg5
+Description: Advanced clipboard manager with editing and scripting features
+ CopyQ monitors system clipboard and saves its content in customized tabs.
+ Saved clipboard can be later copied and pasted directly into any application.
+ .
+ Items can be:
+ * edited with internal editor or with preferred text editor,
+ * moved to other tabs,
+ * drag'n'dropped to applications,
+ * marked with tag or a note,
+ * passed to or changed by custom commands,
+ * or simply removed.
+ .
+ Features:
+ * Support for Linux, Windows and OS X 10.9+
+ * Store text, HTML, images or any other custom formats
+ * Quickly browse and filter items in clipboard history
+ * Sort, create, edit, remove, copy/paste, drag'n'drop items in tabs
+ * Add notes or tags to items
+ * System-wide shortcuts with customizable commands
+ * Paste items with shortcut or from tray or main window
+ * Fully customizable appearance
+ * Advanced command-line interface and scripting
+ * Ignore clipboard copied from some windows or containing some text
+ * Support for simple Vim-like editor and shortcuts
+ * Many more features
diff --git a/CopyQ-3.0.2/debian/control-qt4 b/CopyQ-3.0.2/debian/control-qt4
new file mode 100644
index 0000000..91bb0dc
--- /dev/null
+++ b/CopyQ-3.0.2/debian/control-qt4
@@ -0,0 +1,41 @@
+Source: copyq
+Section: misc
+Priority: optional
+Maintainer: Lukas Holecek
+Build-Depends: debhelper (>= 9), cmake
+ , libqt4-dev
+ , libxfixes-dev
+ , libxtst-dev
+Standards-Version: 3.9.7
+Homepage: https://hluk.github.io/CopyQ/
+Vcs-Browser: https://github.com/hluk/CopyQ
+Vcs-Git: https://github.com/hluk/CopyQ.git
+
+Package: copyq
+Architecture: any
+Depends: ${misc:Depends}, ${shlibs:Depends}, libqt4-xml, libqt4-network, libqt4-script, libqt4-svg
+Description: Advanced clipboard manager with editing and scripting features
+ CopyQ monitors system clipboard and saves its content in customized tabs.
+ Saved clipboard can be later copied and pasted directly into any application.
+ .
+ Items can be:
+ * edited with internal editor or with preferred text editor,
+ * moved to other tabs,
+ * drag'n'dropped to applications,
+ * marked with tag or a note,
+ * passed to or changed by custom commands,
+ * or simply removed.
+ .
+ Features:
+ * Support for Linux, Windows and OS X 10.9+
+ * Store text, HTML, images or any other custom formats
+ * Quickly browse and filter items in clipboard history
+ * Sort, create, edit, remove, copy/paste, drag'n'drop items in tabs
+ * Add notes or tags to items
+ * System-wide shortcuts with customizable commands
+ * Paste items with shortcut or from tray or main window
+ * Fully customizable appearance
+ * Advanced command-line interface and scripting
+ * Ignore clipboard copied from some windows or containing some text
+ * Support for simple Vim-like editor and shortcuts
+ * Many more features
diff --git a/CopyQ-3.0.2/debian/copyright b/CopyQ-3.0.2/debian/copyright
new file mode 100644
index 0000000..4cd4d09
--- /dev/null
+++ b/CopyQ-3.0.2/debian/copyright
@@ -0,0 +1,124 @@
+Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Upstream-Name: CopyQ
+Upstream-Contact: Lukas Holecek
+Source: https://github.com/hluk/CopyQ
+Files-Excluded: src/images/*.ttf
+
+Files: *
+Copyright: 2009-2017 Lukas Holecek
+License: GPL-3+
+Comment:
+ CopyQ 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 3 of the License, or
+ (at your option) any later version.
+ .
+ CopyQ 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.
+
+Files: src/images/fontawesome-webfont.ttf
+Copyright: Font Awesome by Dave Gandy - http://fontawesome.io
+License: SIL OFL 1.1
+URL: http://scripts.sil.org/OFL
+
+Files:
+ src/gui/execmenu.*
+ src/gui/fancylineedit.*
+ src/gui/filterlineedit.*
+Copyright: 2014 Digia Plc and/or its subsidiary(-ies).
+License: LGPL-2.1 or LGPL-3
+Comment:
+ In addition, as a special exception, Digia gives you certain additional
+ rights. These rights are described in the Digia Qt LGPL Exception
+ version 1.1.
+ .
+ --------
+ Digia Qt LGPL Exception version 1.1
+ .
+ As a special exception to the GNU Lesser General Public License version
+ 2.1, the object code form of a "work that uses the Library" may
+ incorporate material from a header file that is part of the Library. You
+ may distribute such object code under terms of your choice, provided that
+ the incorporated material (i) does not exceed more than 5% of the total
+ size of the Library; and (ii) is limited to numerical parameters, data
+ structure layouts, accessors, macros, inline functions and templates.
+ --------
+ http://doc.qt.io/qt-5/lgpl.html
+
+Files: qxt/*
+Copyright: 2006-2011, the LibQxt project.
+License: BSD-3-clause
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted provided that the following conditions are met:
+ * Redistributions of source code must retain the above copyright
+ notice, this list of conditions and the following disclaimer.
+ * Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in the
+ documentation and/or other materials provided with the distribution.
+ * Neither the name of the LibQxt project nor the
+ names of its contributors may be used to endorse or promote products
+ derived from this software without specific prior written permission.
+ .
+ THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+ WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+ DISCLAIMED. IN NO EVENT SHALL BE LIABLE FOR ANY
+ DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+ (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+ LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+ ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+ (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+ SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+Files: debian/*
+Copyright: Dmitry Smirnov
+License: GPL-3+
+
+License: GPL-3+
+ 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 3, 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.
+ .
+ The complete text of the GNU General Public License can be found
+ in "/usr/share/common-licenses/GPL-3".
+
+License: LGPL-2.1
+ This library is free software; you can redistribute it and/or
+ modify it under the terms of the GNU Lesser General Public
+ License version 2.1 as published by the Free Software Foundation.
+ .
+ This library 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 Lesser General Public
+ License along with this library; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+ .
+ The complete text of the GNU Lesser General Public License
+ can be found in "/usr/share/common-licenses/LGPL-2.1".
+
+License: LGPL-3
+ This package is free software; you can redistribute it and/or modify
+ it under the terms of the GNU Lesser General Public License version 3
+ as published by the Free Software Foundation.
+ .
+ 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 General Public License for more details.
+ .
+ You should have received a copy of the GNU Lesser General Public License
+ along with this program. If not, see
+ .
+ The complete text fo the GNU Lesser General Public License version 3
+ can be found in "/usr/share/common-licenses/LGPL-3"
diff --git a/CopyQ-3.0.2/debian/rules b/CopyQ-3.0.2/debian/rules
new file mode 100644
index 0000000..26ccbb9
--- /dev/null
+++ b/CopyQ-3.0.2/debian/rules
@@ -0,0 +1,17 @@
+#!/usr/bin/make -f
+
+# Uncomment this to turn on verbose mode.
+#export DH_VERBOSE=1
+
+export DEB_BUILD_MAINT_OPTIONS = hardening=+all
+export DEB_LDFLAGS_MAINT_APPEND += -Wl,--as-needed
+export QT_SELECT=5
+
+%:
+ dh $@
+
+override_dh_auto_configure:
+ dh_auto_configure -- \
+ -DCMAKE_VERBOSE_MAKEFILE=ON \
+ -DCMAKE_BUILD_TYPE=Release \
+ -DWITH_WEBKIT=1
diff --git a/CopyQ-3.0.2/debian/rules-qt4 b/CopyQ-3.0.2/debian/rules-qt4
new file mode 100644
index 0000000..5570df8
--- /dev/null
+++ b/CopyQ-3.0.2/debian/rules-qt4
@@ -0,0 +1,17 @@
+#!/usr/bin/make -f
+
+# Uncomment this to turn on verbose mode.
+#export DH_VERBOSE=1
+
+export DEB_BUILD_MAINT_OPTIONS = hardening=+all
+export DEB_LDFLAGS_MAINT_APPEND += -Wl,--as-needed
+
+%:
+ dh $@
+
+override_dh_auto_configure:
+ dh_auto_configure -- \
+ -DCMAKE_VERBOSE_MAKEFILE=ON \
+ -DCMAKE_BUILD_TYPE=Release \
+ -DWITH_QT5=OFF \
+ -DWITH_WEBKIT=1
diff --git a/CopyQ-3.0.2/debugfiles.list b/CopyQ-3.0.2/debugfiles.list
new file mode 100644
index 0000000..d63427f
--- /dev/null
+++ b/CopyQ-3.0.2/debugfiles.list
@@ -0,0 +1,55 @@
+%dir /usr/lib/debug
+%dir /usr/lib/debug/usr
+%dir /usr/lib/debug/usr/bin
+%dir /usr/lib/debug/usr/lib64
+%dir /usr/lib/debug/usr/lib64/copyq
+%dir /usr/lib/debug/usr/lib64/copyq/plugins
+%dir /usr/lib/debug/.build-id
+%dir /usr/lib/debug/.build-id/39
+%dir /usr/lib/debug/.build-id/40
+%dir /usr/lib/debug/.build-id/50
+%dir /usr/lib/debug/.build-id/e9
+%dir /usr/lib/debug/.build-id/ec
+%dir /usr/lib/debug/.build-id/25
+%dir /usr/lib/debug/.build-id/3c
+%dir /usr/lib/debug/.build-id/92
+%dir /usr/lib/debug/.build-id/48
+%dir /usr/lib/debug/.build-id/ca
+%dir /usr/lib/debug/.build-id/c9
+%dir /usr/lib/debug/.dwz
+/usr/lib/debug/usr/bin/copyq.debug
+/usr/lib/debug/usr/lib64/copyq/plugins/libitemdata.so.debug
+/usr/lib/debug/usr/lib64/copyq/plugins/libitemencrypted.so.debug
+/usr/lib/debug/usr/lib64/copyq/plugins/libitemfakevim.so.debug
+/usr/lib/debug/usr/lib64/copyq/plugins/libitemimage.so.debug
+/usr/lib/debug/usr/lib64/copyq/plugins/libitemnotes.so.debug
+/usr/lib/debug/usr/lib64/copyq/plugins/libitempinned.so.debug
+/usr/lib/debug/usr/lib64/copyq/plugins/libitemtags.so.debug
+/usr/lib/debug/usr/lib64/copyq/plugins/libitemtext.so.debug
+/usr/lib/debug/usr/lib64/copyq/plugins/libitemsync.so.debug
+/usr/lib/debug/usr/lib64/copyq/plugins/libitemweb.so.debug
+/usr/lib/debug/.build-id/39/6fb26cad0769eacd7af5a39c7fc2e9c51ea8d3
+/usr/lib/debug/.build-id/39/6fb26cad0769eacd7af5a39c7fc2e9c51ea8d3.debug
+/usr/lib/debug/.build-id/40/556e992b3e12ba6de9d1882d30b7e73824ba79
+/usr/lib/debug/.build-id/40/556e992b3e12ba6de9d1882d30b7e73824ba79.debug
+/usr/lib/debug/.build-id/50/851b8d260a05ae088cc78dcaa6a102464472b2
+/usr/lib/debug/.build-id/50/851b8d260a05ae088cc78dcaa6a102464472b2.debug
+/usr/lib/debug/.build-id/e9/4627e58f07e29f32c365d4d028acbdd0e89921
+/usr/lib/debug/.build-id/e9/4627e58f07e29f32c365d4d028acbdd0e89921.debug
+/usr/lib/debug/.build-id/ec/a114fc00cc483f6b814421f97ac456e0d12067
+/usr/lib/debug/.build-id/ec/a114fc00cc483f6b814421f97ac456e0d12067.debug
+/usr/lib/debug/.build-id/25/d434b121abb4897672d69bb712ce1be3d655f9
+/usr/lib/debug/.build-id/25/d434b121abb4897672d69bb712ce1be3d655f9.debug
+/usr/lib/debug/.build-id/3c/710c9050a1f474964b4a1386e82800e2c5e62d
+/usr/lib/debug/.build-id/3c/710c9050a1f474964b4a1386e82800e2c5e62d.debug
+/usr/lib/debug/.build-id/3c/0e7d1c8fdaa374d4ed98e50bfd758e379ae062
+/usr/lib/debug/.build-id/3c/0e7d1c8fdaa374d4ed98e50bfd758e379ae062.debug
+/usr/lib/debug/.build-id/92/dc76b6c1c5f939a944e21c7a83618f5f77cc3d
+/usr/lib/debug/.build-id/92/dc76b6c1c5f939a944e21c7a83618f5f77cc3d.debug
+/usr/lib/debug/.build-id/48/9fe1d84c8799004869412a6e133a5e1a105b97
+/usr/lib/debug/.build-id/48/9fe1d84c8799004869412a6e133a5e1a105b97.debug
+/usr/lib/debug/.build-id/ca/536be7713f249df8c76ab5378c30eed1944769
+/usr/lib/debug/.build-id/ca/536be7713f249df8c76ab5378c30eed1944769.debug
+/usr/lib/debug/.build-id/c9/c11dd588b71df9b878fb201fe399e64a211f6e.debug
+/usr/lib/debug/.dwz/copyq-3.0.2-1.fc27.x86_64
+/usr/src/debug/CopyQ-3.0.2
diff --git a/CopyQ-3.0.2/debuglinks.list b/CopyQ-3.0.2/debuglinks.list
new file mode 100644
index 0000000..e566d45
--- /dev/null
+++ b/CopyQ-3.0.2/debuglinks.list
@@ -0,0 +1,23 @@
+/usr/lib/debug/.build-id/39/6fb26cad0769eacd7af5a39c7fc2e9c51ea8d3 /usr/bin/copyq
+/usr/lib/debug/.build-id/39/6fb26cad0769eacd7af5a39c7fc2e9c51ea8d3.debug /usr/lib/debug/usr/bin/copyq.debug
+/usr/lib/debug/.build-id/40/556e992b3e12ba6de9d1882d30b7e73824ba79 /usr/lib64/copyq/plugins/libitemdata.so
+/usr/lib/debug/.build-id/40/556e992b3e12ba6de9d1882d30b7e73824ba79.debug /usr/lib/debug/usr/lib64/copyq/plugins/libitemdata.so.debug
+/usr/lib/debug/.build-id/50/851b8d260a05ae088cc78dcaa6a102464472b2 /usr/lib64/copyq/plugins/libitemencrypted.so
+/usr/lib/debug/.build-id/50/851b8d260a05ae088cc78dcaa6a102464472b2.debug /usr/lib/debug/usr/lib64/copyq/plugins/libitemencrypted.so.debug
+/usr/lib/debug/.build-id/e9/4627e58f07e29f32c365d4d028acbdd0e89921 /usr/lib64/copyq/plugins/libitemfakevim.so
+/usr/lib/debug/.build-id/e9/4627e58f07e29f32c365d4d028acbdd0e89921.debug /usr/lib/debug/usr/lib64/copyq/plugins/libitemfakevim.so.debug
+/usr/lib/debug/.build-id/ec/a114fc00cc483f6b814421f97ac456e0d12067 /usr/lib64/copyq/plugins/libitemimage.so
+/usr/lib/debug/.build-id/ec/a114fc00cc483f6b814421f97ac456e0d12067.debug /usr/lib/debug/usr/lib64/copyq/plugins/libitemimage.so.debug
+/usr/lib/debug/.build-id/25/d434b121abb4897672d69bb712ce1be3d655f9 /usr/lib64/copyq/plugins/libitemnotes.so
+/usr/lib/debug/.build-id/25/d434b121abb4897672d69bb712ce1be3d655f9.debug /usr/lib/debug/usr/lib64/copyq/plugins/libitemnotes.so.debug
+/usr/lib/debug/.build-id/3c/710c9050a1f474964b4a1386e82800e2c5e62d /usr/lib64/copyq/plugins/libitempinned.so
+/usr/lib/debug/.build-id/3c/710c9050a1f474964b4a1386e82800e2c5e62d.debug /usr/lib/debug/usr/lib64/copyq/plugins/libitempinned.so.debug
+/usr/lib/debug/.build-id/3c/0e7d1c8fdaa374d4ed98e50bfd758e379ae062 /usr/lib64/copyq/plugins/libitemtags.so
+/usr/lib/debug/.build-id/3c/0e7d1c8fdaa374d4ed98e50bfd758e379ae062.debug /usr/lib/debug/usr/lib64/copyq/plugins/libitemtags.so.debug
+/usr/lib/debug/.build-id/92/dc76b6c1c5f939a944e21c7a83618f5f77cc3d /usr/lib64/copyq/plugins/libitemtext.so
+/usr/lib/debug/.build-id/92/dc76b6c1c5f939a944e21c7a83618f5f77cc3d.debug /usr/lib/debug/usr/lib64/copyq/plugins/libitemtext.so.debug
+/usr/lib/debug/.build-id/48/9fe1d84c8799004869412a6e133a5e1a105b97 /usr/lib64/copyq/plugins/libitemsync.so
+/usr/lib/debug/.build-id/48/9fe1d84c8799004869412a6e133a5e1a105b97.debug /usr/lib/debug/usr/lib64/copyq/plugins/libitemsync.so.debug
+/usr/lib/debug/.build-id/ca/536be7713f249df8c76ab5378c30eed1944769 /usr/lib64/copyq/plugins/libitemweb.so
+/usr/lib/debug/.build-id/ca/536be7713f249df8c76ab5378c30eed1944769.debug /usr/lib/debug/usr/lib64/copyq/plugins/libitemweb.so.debug
+/usr/lib/debug/.build-id/c9/c11dd588b71df9b878fb201fe399e64a211f6e.debug /usr/lib/debug/.dwz/copyq-3.0.2-1.fc27.x86_64
diff --git a/CopyQ-3.0.2/debugsources.list b/CopyQ-3.0.2/debugsources.list
new file mode 100644
index 0000000..fa89a0c
Binary files /dev/null and b/CopyQ-3.0.2/debugsources.list differ
diff --git a/CopyQ-3.0.2/elfbins.list b/CopyQ-3.0.2/elfbins.list
new file mode 100644
index 0000000..a7be0e3
--- /dev/null
+++ b/CopyQ-3.0.2/elfbins.list
@@ -0,0 +1,11 @@
+.//usr/bin/copyq
+.//usr/lib64/copyq/plugins/libitemdata.so
+.//usr/lib64/copyq/plugins/libitemencrypted.so
+.//usr/lib64/copyq/plugins/libitemfakevim.so
+.//usr/lib64/copyq/plugins/libitemimage.so
+.//usr/lib64/copyq/plugins/libitemnotes.so
+.//usr/lib64/copyq/plugins/libitempinned.so
+.//usr/lib64/copyq/plugins/libitemtags.so
+.//usr/lib64/copyq/plugins/libitemtext.so
+.//usr/lib64/copyq/plugins/libitemsync.so
+.//usr/lib64/copyq/plugins/libitemweb.so
diff --git a/CopyQ-3.0.2/gpl.txt b/CopyQ-3.0.2/gpl.txt
new file mode 100644
index 0000000..94a9ed0
--- /dev/null
+++ b/CopyQ-3.0.2/gpl.txt
@@ -0,0 +1,674 @@
+ GNU GENERAL PUBLIC LICENSE
+ Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc.
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+ The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works. By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users. We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors. You can apply it to
+your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+ To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights. Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received. You must make sure that they, too, receive
+or can get the source code. And you must show them these terms so they
+know their rights.
+
+ Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+ For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software. For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+ Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so. This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software. The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable. Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products. If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+ Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary. To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ TERMS AND CONDITIONS
+
+ 0. Definitions.
+
+ "This License" refers to version 3 of the GNU General Public License.
+
+ "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+ "The Program" refers to any copyrightable work licensed under this
+License. Each licensee is addressed as "you". "Licensees" and
+"recipients" may be individuals or organizations.
+
+ To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy. The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+ A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+ To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy. Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+ To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies. Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+ An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License. If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+ 1. Source Code.
+
+ The "source code" for a work means the preferred form of the work
+for making modifications to it. "Object code" means any non-source
+form of a work.
+
+ A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+ The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form. A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+ The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities. However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work. For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+ The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+ The Corresponding Source for a work in source code form is that
+same work.
+
+ 2. Basic Permissions.
+
+ All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met. This License explicitly affirms your unlimited
+permission to run the unmodified Program. The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work. This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+ You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force. You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright. Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+ Conveying under any other circumstances is permitted solely under
+the conditions stated below. Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+ 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+ No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+ When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+ 4. Conveying Verbatim Copies.
+
+ You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+ You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+ 5. Conveying Modified Source Versions.
+
+ You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+ a) The work must carry prominent notices stating that you modified
+ it, and giving a relevant date.
+
+ b) The work must carry prominent notices stating that it is
+ released under this License and any conditions added under section
+ 7. This requirement modifies the requirement in section 4 to
+ "keep intact all notices".
+
+ c) You must license the entire work, as a whole, under this
+ License to anyone who comes into possession of a copy. This
+ License will therefore apply, along with any applicable section 7
+ additional terms, to the whole of the work, and all its parts,
+ regardless of how they are packaged. This License gives no
+ permission to license the work in any other way, but it does not
+ invalidate such permission if you have separately received it.
+
+ d) If the work has interactive user interfaces, each must display
+ Appropriate Legal Notices; however, if the Program has interactive
+ interfaces that do not display Appropriate Legal Notices, your
+ work need not make them do so.
+
+ A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit. Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+ 6. Conveying Non-Source Forms.
+
+ You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+ a) Convey the object code in, or embodied in, a physical product
+ (including a physical distribution medium), accompanied by the
+ Corresponding Source fixed on a durable physical medium
+ customarily used for software interchange.
+
+ b) Convey the object code in, or embodied in, a physical product
+ (including a physical distribution medium), accompanied by a
+ written offer, valid for at least three years and valid for as
+ long as you offer spare parts or customer support for that product
+ model, to give anyone who possesses the object code either (1) a
+ copy of the Corresponding Source for all the software in the
+ product that is covered by this License, on a durable physical
+ medium customarily used for software interchange, for a price no
+ more than your reasonable cost of physically performing this
+ conveying of source, or (2) access to copy the
+ Corresponding Source from a network server at no charge.
+
+ c) Convey individual copies of the object code with a copy of the
+ written offer to provide the Corresponding Source. This
+ alternative is allowed only occasionally and noncommercially, and
+ only if you received the object code with such an offer, in accord
+ with subsection 6b.
+
+ d) Convey the object code by offering access from a designated
+ place (gratis or for a charge), and offer equivalent access to the
+ Corresponding Source in the same way through the same place at no
+ further charge. You need not require recipients to copy the
+ Corresponding Source along with the object code. If the place to
+ copy the object code is a network server, the Corresponding Source
+ may be on a different server (operated by you or a third party)
+ that supports equivalent copying facilities, provided you maintain
+ clear directions next to the object code saying where to find the
+ Corresponding Source. Regardless of what server hosts the
+ Corresponding Source, you remain obligated to ensure that it is
+ available for as long as needed to satisfy these requirements.
+
+ e) Convey the object code using peer-to-peer transmission, provided
+ you inform other peers where the object code and Corresponding
+ Source of the work are being offered to the general public at no
+ charge under subsection 6d.
+
+ A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+ A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling. In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage. For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product. A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+ "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source. The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+ If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information. But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+ The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed. Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+ Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+ 7. Additional Terms.
+
+ "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law. If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+ When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it. (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.) You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+ Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+ a) Disclaiming warranty or limiting liability differently from the
+ terms of sections 15 and 16 of this License; or
+
+ b) Requiring preservation of specified reasonable legal notices or
+ author attributions in that material or in the Appropriate Legal
+ Notices displayed by works containing it; or
+
+ c) Prohibiting misrepresentation of the origin of that material, or
+ requiring that modified versions of such material be marked in
+ reasonable ways as different from the original version; or
+
+ d) Limiting the use for publicity purposes of names of licensors or
+ authors of the material; or
+
+ e) Declining to grant rights under trademark law for use of some
+ trade names, trademarks, or service marks; or
+
+ f) Requiring indemnification of licensors and authors of that
+ material by anyone who conveys the material (or modified versions of
+ it) with contractual assumptions of liability to the recipient, for
+ any liability that these contractual assumptions directly impose on
+ those licensors and authors.
+
+ All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10. If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term. If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+ If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+ Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+ 8. Termination.
+
+ You may not propagate or modify a covered work except as expressly
+provided under this License. Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+ However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+ Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+ Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License. If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+ 9. Acceptance Not Required for Having Copies.
+
+ You are not required to accept this License in order to receive or
+run a copy of the Program. Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance. However,
+nothing other than this License grants you permission to propagate or
+modify any covered work. These actions infringe copyright if you do
+not accept this License. Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+ 10. Automatic Licensing of Downstream Recipients.
+
+ Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License. You are not responsible
+for enforcing compliance by third parties with this License.
+
+ An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations. If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+ You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License. For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+ 11. Patents.
+
+ A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based. The
+work thus licensed is called the contributor's "contributor version".
+
+ A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version. For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+ Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+ In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement). To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+ If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients. "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+ If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+ A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License. You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+ Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+ 12. No Surrender of Others' Freedom.
+
+ If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all. For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+ 13. Use with the GNU Affero General Public License.
+
+ Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work. The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+ 14. Revised Versions of this License.
+
+ The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+ Each version is given a distinguishing version number. If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation. If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+ If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+ Later license versions may give you additional or different
+permissions. However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+ 15. Disclaimer of Warranty.
+
+ THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+ 16. Limitation of Liability.
+
+ IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+ 17. Interpretation of Sections 15 and 16.
+
+ If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+ END OF TERMS AND CONDITIONS
+
+ How to Apply These Terms to Your New Programs
+
+ If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+
+ Copyright (C)
+
+ 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 3 of the License, 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.
+
+ You should have received a copy of the GNU General Public License
+ along with this program. If not, see .
+
+Also add information on how to contact you by electronic and paper mail.
+
+ If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+ Copyright (C)
+ This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License. Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+ You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+.
+
+ The GNU General Public License does not permit incorporating your program
+into proprietary programs. If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library. If this is what you want to do, use the GNU Lesser General
+Public License instead of this License. But first, please read
+.
diff --git a/CopyQ-3.0.2/install_manifest.txt b/CopyQ-3.0.2/install_manifest.txt
new file mode 100644
index 0000000..71db68d
--- /dev/null
+++ b/CopyQ-3.0.2/install_manifest.txt
@@ -0,0 +1,66 @@
+/usr/share/icons/hicolor/scalable/apps/copyq-normal.svg
+/usr/share/icons/hicolor/scalable/apps/copyq-busy.svg
+/usr/share/applications/copyq.desktop
+/usr/share/appdata/copyq.appdata.xml
+/usr/share/icons/hicolor/16x16/apps/copyq.png
+/usr/share/icons/hicolor/16x16/apps/copyq-normal.png
+/usr/share/icons/hicolor/16x16/apps/copyq-busy.png
+/usr/share/icons/hicolor/22x22/apps/copyq.png
+/usr/share/icons/hicolor/22x22/apps/copyq-normal.png
+/usr/share/icons/hicolor/22x22/apps/copyq-busy.png
+/usr/share/icons/hicolor/24x24/apps/copyq.png
+/usr/share/icons/hicolor/24x24/apps/copyq-normal.png
+/usr/share/icons/hicolor/24x24/apps/copyq-busy.png
+/usr/share/icons/hicolor/32x32/apps/copyq.png
+/usr/share/icons/hicolor/32x32/apps/copyq-normal.png
+/usr/share/icons/hicolor/32x32/apps/copyq-busy.png
+/usr/share/icons/hicolor/48x48/apps/copyq.png
+/usr/share/icons/hicolor/48x48/apps/copyq-normal.png
+/usr/share/icons/hicolor/48x48/apps/copyq-busy.png
+/usr/share/icons/hicolor/64x64/apps/copyq.png
+/usr/share/icons/hicolor/64x64/apps/copyq-normal.png
+/usr/share/icons/hicolor/64x64/apps/copyq-busy.png
+/usr/share/icons/hicolor/128x128/apps/copyq.png
+/usr/share/icons/hicolor/128x128/apps/copyq-normal.png
+/usr/share/icons/hicolor/128x128/apps/copyq-busy.png
+/usr/share/copyq/themes/dark.ini
+/usr/share/copyq/themes/forest.ini
+/usr/share/copyq/themes/light.ini
+/usr/share/copyq/themes/paper.ini
+/usr/share/copyq/themes/simple.ini
+/usr/share/copyq/themes/solarized-dark.ini
+/usr/share/copyq/themes/solarized-light.ini
+/usr/share/copyq/themes/wine.ini
+/usr/bin/copyq
+/usr/share/copyq/locale/copyq_ar.qm
+/usr/share/copyq/locale/copyq_cs.qm
+/usr/share/copyq/locale/copyq_da.qm
+/usr/share/copyq/locale/copyq_de.qm
+/usr/share/copyq/locale/copyq_es.qm
+/usr/share/copyq/locale/copyq_fr.qm
+/usr/share/copyq/locale/copyq_hu.qm
+/usr/share/copyq/locale/copyq_it.qm
+/usr/share/copyq/locale/copyq_ja.qm
+/usr/share/copyq/locale/copyq_lt.qm
+/usr/share/copyq/locale/copyq_nb.qm
+/usr/share/copyq/locale/copyq_nl.qm
+/usr/share/copyq/locale/copyq_pl.qm
+/usr/share/copyq/locale/copyq_pt_BR.qm
+/usr/share/copyq/locale/copyq_pt_PT.qm
+/usr/share/copyq/locale/copyq_ru.qm
+/usr/share/copyq/locale/copyq_sk.qm
+/usr/share/copyq/locale/copyq_sv.qm
+/usr/share/copyq/locale/copyq_tr.qm
+/usr/share/copyq/locale/copyq_uk.qm
+/usr/share/copyq/locale/copyq_zh_CN.qm
+/usr/share/copyq/locale/copyq_zh_TW.qm
+/usr/lib64/copyq/plugins/libitemdata.so
+/usr/lib64/copyq/plugins/libitemencrypted.so
+/usr/lib64/copyq/plugins/libitemfakevim.so
+/usr/lib64/copyq/plugins/libitemimage.so
+/usr/lib64/copyq/plugins/libitemnotes.so
+/usr/lib64/copyq/plugins/libitempinned.so
+/usr/lib64/copyq/plugins/libitemtags.so
+/usr/lib64/copyq/plugins/libitemtext.so
+/usr/lib64/copyq/plugins/libitemsync.so
+/usr/lib64/copyq/plugins/libitemweb.so
\ No newline at end of file
diff --git a/CopyQ-3.0.2/plugins/CMakeLists.txt b/CopyQ-3.0.2/plugins/CMakeLists.txt
new file mode 100644
index 0000000..1790b47
--- /dev/null
+++ b/CopyQ-3.0.2/plugins/CMakeLists.txt
@@ -0,0 +1,65 @@
+macro (copyq_add_plugin)
+ set(copyq_pkg ${ARGV0})
+
+ file(GLOB copyq_plugin_SOURCES
+ ${copyq_plugin_${copyq_pkg}_SOURCES}
+ *.cpp
+ ../../src/item/itemwidget.cpp
+ )
+ file(GLOB copyq_plugin_FORMS
+ ${copyq_plugin_${copyq_pkg}_FORMS}
+ *.ui
+ )
+
+ if (WITH_TESTS)
+ file(GLOB copyq_plugin_SOURCES ${copyq_plugin_SOURCES} tests/*.cpp)
+ endif (WITH_TESTS)
+
+ include_directories(${CMAKE_CURRENT_BINARY_DIR} ../../src)
+
+ if (WITH_QT5)
+ include_directories(${Qt5Widgets_INCLUDES})
+ add_definitions(${Qt5Widgets_DEFINITIONS})
+ qt5_wrap_ui(copyq_plugin_FORMS_HEADERS ${copyq_plugin_FORMS})
+ qt5_add_resources(copyq_plugin_RCC ${copyq_plugin_${copyq_pkg}_RESOURCES})
+ else()
+ include_directories(${QT_INCLUDES})
+ add_definitions(${QT_DEFINITIONS})
+ qt4_wrap_ui(copyq_plugin_FORMS_HEADERS ${copyq_plugin_FORMS})
+ qt4_add_resources(copyq_plugin_RCC ${copyq_plugin_${copyq_pkg}_RESOURCES})
+ endif()
+
+ add_library(${copyq_pkg} MODULE
+ ${copyq_plugin_SOURCES}
+ ${copyq_plugin_FORMS_HEADERS}
+ ${copyq_plugin_RCC}
+ )
+
+ set_target_properties(${copyq_pkg} PROPERTIES
+ COMPILE_DEFINITIONS "${copyq_plugin_${copyq_pkg}_DEFINITIONS}")
+
+ if (WITH_QT5)
+ qt5_use_modules(${copyq_pkg} Widgets ${copyq_Qt5_Modules} ${copyq_plugin_${copyq_pkg}_Qt5_Modules})
+ else()
+ include(${QT_USE_FILE})
+ endif()
+
+ target_link_libraries(${copyq_pkg} ${QT_LIBRARIES} ${copyq_plugin_${copyq_pkg}_LIBRARIES})
+
+ if (${CMAKE_SYSTEM_NAME} MATCHES "Linux")
+ install(TARGETS ${copyq_pkg} DESTINATION ${PLUGIN_INSTALL_PREFIX})
+ endif()
+endmacro()
+
+set(LIBRARY_OUTPUT_PATH ${PROJECT_BINARY_DIR}/plugins)
+
+add_subdirectory("itemdata")
+add_subdirectory("itemencrypted")
+add_subdirectory("itemfakevim")
+add_subdirectory("itemimage")
+add_subdirectory("itemnotes")
+add_subdirectory("itempinned")
+add_subdirectory("itemtags")
+add_subdirectory("itemtext")
+add_subdirectory("itemsync")
+add_subdirectory("itemweb")
diff --git a/CopyQ-3.0.2/plugins/itemdata/CMakeLists.txt b/CopyQ-3.0.2/plugins/itemdata/CMakeLists.txt
new file mode 100644
index 0000000..c7a70be
--- /dev/null
+++ b/CopyQ-3.0.2/plugins/itemdata/CMakeLists.txt
@@ -0,0 +1,8 @@
+set(copyq_plugin_itemdata_SOURCES
+ ../../src/common/log.cpp
+ ../../src/common/mimetypes.cpp
+ ../../src/common/textdata.cpp
+ )
+
+copyq_add_plugin(itemdata)
+
diff --git a/CopyQ-3.0.2/plugins/itemdata/itemdata.cpp b/CopyQ-3.0.2/plugins/itemdata/itemdata.cpp
new file mode 100644
index 0000000..299a49d
--- /dev/null
+++ b/CopyQ-3.0.2/plugins/itemdata/itemdata.cpp
@@ -0,0 +1,212 @@
+/*
+ Copyright (c) 2014, Lukas Holecek
+
+ This file is part of CopyQ.
+
+ CopyQ 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 3 of the License, or
+ (at your option) any later version.
+
+ CopyQ 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.
+
+ You should have received a copy of the GNU General Public License
+ along with CopyQ. If not, see .
+*/
+
+#include "itemdata.h"
+#include "ui_itemdatasettings.h"
+
+#include "common/contenttype.h"
+#include "common/mimetypes.h"
+#include "common/textdata.h"
+
+#include
+#include
+#include
+#include
+#include
+
+namespace {
+
+// Limit number of characters for performance reasons.
+const int defaultMaxBytes = 256;
+
+QString hexData(const QByteArray &data)
+{
+ if ( data.isEmpty() )
+ return QString();
+
+ QString result;
+ QString chars;
+
+ int i = 0;
+ forever {
+ if (i > 0) {
+ if ( (i % 2) == 0 )
+ result.append( QString(" ") );
+ if ( (i % 16) == 0 ) {
+ result.append(" ");
+ result.append(chars);
+ result.append( QString("\n") );
+ chars.clear();
+ if (i >= data.size() )
+ break;
+ }
+ }
+ if ( (i % 16) == 0 ) {
+ result.append( QString("%1: ").arg(QString::number(i, 16), 4, QChar('0')) );
+ }
+ if (i < data.size() ) {
+ QChar c = data[i];
+ result.append( QString("%1").arg(QString::number(c.unicode(), 16), 2, QChar('0')) );
+ chars.append( c.isPrint() ? escapeHtml(QString(c)) : QString(".") );
+ } else {
+ result.append( QString(" ") );
+ }
+
+ ++i;
+ }
+
+ return result;
+}
+
+QString stringFromBytes(const QByteArray &bytes, const QString &format)
+{
+ QTextCodec *codec = QTextCodec::codecForName("utf-8");
+ if (format == QLatin1String("text/html"))
+ codec = QTextCodec::codecForHtml(bytes, codec);
+ return codec->toUnicode(bytes);
+}
+
+bool emptyIntersection(const QStringList &lhs, const QStringList &rhs)
+{
+ for (const auto &l : lhs) {
+ if ( rhs.contains(l) )
+ return false;
+ }
+
+ return true;
+}
+
+} // namespace
+
+ItemData::ItemData(const QModelIndex &index, int maxBytes, QWidget *parent)
+ : QLabel(parent)
+ , ItemWidget(this)
+{
+ setTextInteractionFlags(Qt::TextSelectableByMouse);
+ setContentsMargins(4, 4, 4, 4);
+ setTextFormat(Qt::RichText);
+
+ QString text;
+
+ const QVariantMap data = index.data(contentType::data).toMap();
+ for ( const auto &format : data.keys() ) {
+ QByteArray bytes = data[format].toByteArray();
+ const int size = bytes.size();
+ bool trimmed = size > maxBytes;
+ if (trimmed)
+ bytes = bytes.left(maxBytes);
+
+ bool hasText = format.startsWith("text/") ||
+ format.startsWith("application/x-copyq-owner-window-title");
+ const QString content = hasText ? escapeHtml(stringFromBytes(bytes, format)) : hexData(bytes);
+ text.append( QString("