![](\"icons/logo.png\"){kind=logo}
\n\n# Qt Aseman\n\n- [What is QtAseman?](https://github.com/Aseman-Land/QtAseman#what-is-qtaseman)\n- [New in QtAseman 3.1.x](https://github.com/Aseman-Land/QtAseman#new-in-qtaseman-31x)\n- [How to Install](https://github.com/Aseman-Land/QtAseman#how-to-install)\n- [How to Build](https://github.com/Aseman-Land/QtAseman#how-to-build)\n- [How to create a QML application using QtAseman](https://github.com/Aseman-Land/QtAseman#how-to-create-a-qml-application-using-qtaseman)\n- [QtAseman QML modules](https://github.com/Aseman-Land/QtAseman#qtaseman-qml-modules)\n- [Documents](https://github.com/Aseman-Land/QtAseman#documents)\n- [Donation](https://github.com/Aseman-Land/QtAseman#donation)\n\n## What is QtAseman\n\nQtAseman is a set of tools, design patterns and architectures that we have developed over the years in various projects for wide range of uses. Now, with it's proven stability, we have decided to release this collection with the name QtAseman as an Open Source and Free tool under the LGPLv3 license.\n\n\n\nSome main features to use on QML are:\n\n- Viewport tools that provides unique page manager system (page, popup, stack, dialog and ...)\n- Gestures for viewports \n- Transparent statusbar and optional navigation bar on mobile devices\n- Some extra Qml controls components like Drawer, Header, TextField, CircularProgressBar and ...\n- BackHandler system\n- Font awesome and Material icons fonts\n- VideoPlayer component\n- Some graphical components like shadows for easy to use and better experiance\n- Network and Http Request handler\n- Models and Abstract models with better experience\n- Encrypt/Decrypt tools\n- Qt/C++ Like Hash, Map and List objects\n- Tools to get more device infos like deviceId, density, keyboard height, statusBar height and ...\n- Translation manager tools\n- Settings manager\n- Some other tools like file read/write methods, type convert methods and ...\n- Process executer tools from QML\n\n## New in QtAseman 3.9.x\n\n- QtAseman's Control Beta.\n It's a simple example:\n\n```js\nimport QtQuick 2.15\nimport AsemanQml.Controls.Beta 3.0\nimport AsemanQml.MaterialIcons 2.0\n\nWindow {\n title: qsTr(\"Hello World\")\n\n Style.primaryColor: \"#3f51b5\"\n Style.primaryTextColor: \"#fff\"\n \n Page {\n id: page\n anchors.fill: parent\n title: \"Home\"\n header: Header {\n width: parent.width\n }\n \n Button {\n id: btn\n anchors.centerIn: parent\n highlighted: true\n icon: MaterialIcons.mdi_dialpad\n text: \"Test Page\"\n onClicked: test_stack.open()\n }\n }\n\n StackPage {\n id: test_stack\n Page {\n id: testStack\n header: Header {\n height: 50\n width: parent.width\n }\n\n Button {\n anchors.centerIn: parent\n highlighted: true\n icon: MaterialIcons.mdi_chevron_left\n text: \"Back\"\n onClicked: test_stack.close()\n }\n }\n }\n}\n```\n\n\n\n## How to Install\n\nCurrently binary packages only available on the ubuntu (launchpad) repositories. To install it on the ubuntu 20.04 LTS:\n\n```bash\nsudo add-apt-repository ppa:aseman/qt-modules\nsudo apt install qt5aseman\n```\n\nand to install development files install `qt5aseman-dev` package.\non Arch you can use [AUR](https://aur.archlinux.org/packages/qt-aseman) (Thanks [molaeiali](https://github.com/molaeiali)):\n\n```bash\nyay -S qt-aseman\n```\n\n## How to build\n\nQtAseman uses standard Qt module mechanisms and it only depends on Qt libraries. Therefor it's quite easy to build on all platforms. Just clone it and build it easily:\n\n```bash\ngit clone https://github.com/Aseman-Land/QtAseman.git --recursive\ncd QtAseman\nmkdir build && cd build\nqmake -r ..\nmake -j2\nmake install\n```\n\nThe easiest way to build is to open it using QtCreator and click on the build icon :)\nAfterwards just run `make install` command to install it in the Qt location.\n\n### QtCreator Wizard\n\nIt will install automatically on Linux based operating systems.\n\nFor other Operating systems, to install QtCreator's wizards, Just copy `src/wizards/qtcreator/qtasemanapplication/` directory to `share/qtcreator/templates/wizards/projects/` directory of the QtCreator.\n\n## How to create a QML application using QtAseman\n\nOne of the main assets of QtAseman is that you can add it to your project without any extra change to the standard structure of the default QML app.\n\nSo To create an application using QtAseman, Just create a new QML project in your QtCreator and add AsemanQML module to the project. Now you can use all QtAseman components:\n\n```js\nimport AsemanQml.Controls 2.0\nimport QtQuick.Controls 2.12\n\nAsemanWindow {\n visible: true\n width: 480\n height: 720\n title: qsTr(\"QtAseman Example\")\n \n Label {\n anchors.centerIn: parent\n text: \"Hello World! :)\"\n }\n}\n```\n\nIf you wish to change any application attribute like applicationName or applicationOrganization you can create an `AsemanApp` object in the parent of `AsemanWindow`. Although it's completely optional and you can ignore it.\n\n```js\nimport AsemanQml.Controls 2.0\n\nAsemanApplication {\n id: app\n applicationAbout: \"QtAseman Application\"\n applicationDisplayName: \"QtAseman\"\n applicationId: \"be2a1f0c-34aa-44ed-8e65-4b1720e560b8\"\n organizationDomain: \"aseman.io\"\n \n AsemanWindow {\n visible: true\n width: 480\n height: 720\n }\n}\n```\n\nWe suggest you to also create an AsemanApplication object, because QtAseman handles config file paths better while this attributes is set.\n\n**Note**: In order to make all modules work correctly on android devices you must replace `io.aseman.android.AsemanApplication` and `io.aseman.android.AsemanActivity` with Qt's values in the android manifest file.\n\n## QtAseman QML Modules\n\nThere are many modules and components in QtAseman that will help you create applications without use of any extra C++ code.\nAlso QtAseman offers a great software architecture for each module that makes development much more easier and faster.\n\n### AsemanQml.Base\n\nAsemanQml.Base module provides many base and core modules for your application. For example modules like Device infos, Desktop functions tools, data type converters, lists, hashes and etc. are placed in Base module.\n\nhere is one of the main uses of Base module:\n\n```js\nimport AsemanQml.Controls 2.0\nimport AsemanQml.Base 2.0\n\nAsemanWindow {\n visible: true\n width: 480\n height: 720\n title: qsTr(\"QtAseman Example\")\n \n Rectangle {\n height: Devices.statusBarHeight\n width: parent.width\n color: \"blue\"\n }\n}\n```\n\nQtAseman makes mobile status bars transparent by default and `Devices.statusBarHeight` returns the status bar height of the device. The above example makes the status bar color blue. If there is no status bar on the device (like desktop operation systems) it returns zero as the result.\n\nYou can get other useful values like screen density, suggested font density, main OS folder locations, platform details, device type and etc. using `Devices` component.\n\nAlso there is `Tools` component that provides some extra tools for applications, like methods to read or write to/from files or methods to convert json to variant map or convert url to local path and etc.\n\nFor example below codes create sha256 hash:\n\n```js\nvar sha = Tools.hash(\"12345\", Tools.Sha256);\n```\n\nOr below codes read text from file:\n\n```js\nvar text = Tools.readText(\"/home/bardia/file.txt\");\n```\n\nThere is also a `Process` component that runs processes or a great back handler component named `BackHandler`.\n\n#### BackHandler\n\n`BackHandler` component provides back mechanism for your application. It's simple and easy to work with, plus all components of QtAseman support it by default, therefore it handles back actions automatically without the direct interference of developer.\n\nBelow example shows you how to use `BackHandler` component in your code:\n\n```js\n\nButton {\n anchors.centerIn: parent\n text: \"Show\"\n onClicked: subRect.visible = true\n}\n\nRectangle {\n id: subRect\n anchors.fill: parent\n visible: false\n onVisibleChanged: {\n if (visible)\n BackHandler.pushHandler(subRect, function(){ subRect.visible = false })\n else\n BackHandler.removeHandler(subRect)\n }\n\n Button {\n anchors.centerIn: parent\n text: \"Hide\"\n onClicked: BackHandler.back()\n }\n}\n```\n\nBeside clicking on the hide button to trigger back function, you can press Esc button or the physical back button of device. On mobile devices if there is no back function in the BackHandler stack and back() method is called, application will try to quit.\n\n**Note**: You must use AsemanWindow object to make Esc or Physical back button work.\n\n#### Settings\n\nCreates a settings file in a specific path and stores settings values there:\n\n````js\nSettings {\n id: settings\n category: \"General\"\n source: AsemanApp.homePath + \"/ui-settings.ini\"\n\n property bool languageInited: false\n property int nightMode: 0\n property int colorTheme: 0\n property int darkColorTheme: 3\n}\n````\n\nEvery change in setting's property is saved and can be restored within the next load of application.\n\n#### Translations\n\n`Translations` and `TranslationManager` provide functions and tools to manage translation in your application:\n\n```js\nTranslationManager {\n id: translationManager\n \n // Finds all lang-*.qm files in the sourceDirectory using three below lines\n sourceDirectory: \"../translations\"\n delimiters: \"-\"\n fileName: \"lang\"\n \n localeName: \"fa\"\n}\n\nButton {\n // Everytime translation changed to other language, Every refresher texts\n // will refreshed and translated to the new language\n text: qsTr(\"Dismiss\") + Translations.refresher\n}\n```\n\n#### RoundedItem\n\nIt renders every included child item as rounded. For example below code shows an image with rounded corners:\n\n```js\nRoundedItem {\n width: 100\n height: 100\n radius: 10\n \n Image {\n anchors.fill: parent\n source: \"image.png\"\n }\n}\n```\n\n#### DelegateSwitch\n\n`DelegateSwitch` provides a component to switch between two or more children components on the fly. For example:\n\n```js\nListView {\n model: 20\n delegate: DelegateSwitch {\n current: model.index % 2\n Component {\n Rectangle {\n width: 100; height: 40\n color: \"red\"\n }\n }\n Component {\n Rectangle {\n width: 40; height: 40\n color: \"blue\"\n }\n }\n }\n}\n```\n\nThis example shows red rectangles on even indexes and blue squeres on odd indexes.\n\n#### ReadMore\n\n To read more about Base module, please read [this document](documents/AsemanQml.Base.md).\n\n### AsemanQml.Controls\n\nControls module provides any control module like QtQuick.Controls. For example It provides `AsemanApplication ` , `AsemanWindow`, `SideMenu`, `Header` and many other components.\n\nBelow example shows a simple usage of the `Controls` component.\n\n```js\nimport QtQuick 2.9\nimport AsemanQml.Base 2.0\nimport AsemanQml.Controls 2.0\n\nAsemanWindow {\n visible: true\n width: 480\n height: 720\n title: qsTr(\"Hello World\")\n \n Header {\n width: parent.width\n text: \"Hello\"\n color: \"#18f\"\n }\n\n Drawer {\n id: menu\n anchors.fill: parent\n delegate: Rectangle {\n anchors.fill: parent\n color: \"#333\"\n }\n }\n\n HeaderMenuButton {\n id: btn\n /* \n * If BackHandler stack is not empty, It shows back \n * button instead of hamburger btn. \n */\n ratio: BackHandler.count? 1 : menu.percent\n onClicked: BackHandler.count? BackHandler.back() : menu.show()\n }\n}\n```\n\n### AsemanQml.Viewport\n\nViewport module provides a new design architecture for applications. \n\nThere is a `Viewport` component that provides a manage mechanism for your page, popup, dialogs and etc.\n\n[](https://youtu.be/hqBt8GOXQB0ase)\n\nBelow example shows you the usage of the `Viewport` component.\n\n```js\nimport AsemanQml.Viewport 2.0\n/*\n * Viewport component manage pages and Way of the they opened.\n * Like popups, pages, dialogs or ...\n * It also supports BackHandler by default like other QtAseman components\n */\nViewport {\n id: viewPort\n anchors.fill: parent\n mainItem: Page {\n // Main/Default Viewport item\n anchors.fill: parent\n\n Button {\n text: \"Open\"\n anchors.centerIn: parent\n \n // append hiComponent to the viewPort stack and open it as page\n // append() returns a refrence to the created ui object.\n // Types are: page, activity, popup, dialog, menu and drawer\n onClicked: viewPort.append(hiComponent, undefined, \"page\")\n }\n }\n}\n\nComponent {\n id: hiComponent\n Page {\n id: page\n anchors.fill: parent\n property int cnt\n\n Button {\n id: btn\n text: \"Open \" + (page.cnt+1)\n anchors.centerIn: parent\n \n // append method could also pass properties to the dest object\n onClicked: viewPort.append(hiComponent, {\"counter\": page.cnt+1}, \"popup\")\n }\n }\n}\n```\n\nThere is also an attached property, you can use to call append function in the Viewport's childeren components:\n\n```js\nViewport.viewport.append(...)\n```\n\n#### ViewportController\n\nUsing `ViewportController` components you won't need to create a complicated architecture. It helps you to make your architecture quite easy and dynamic.\n\nBelow example shows you how to create UI and open them easily in the apps.\n\nUsing this design architecture, you create separated UI files, link them to their specific path and just call them using controllers anywhere in the App.\n`ViewportController` opens them automatically in the `Viewport`.\n\n```js\nViewport {\n id: viewPort\n anchors.fill: parent\n mainItem: Page {\n anchors.fill: parent\n\n Button {\n text: \"Open\"\n anchors.centerIn: parent\n // Trigger the path and open UI item that linked to the path.\n // trigger() returns a refrence to the created ui object.\n onClicked: controller.trigger(\"main://test/bardia\")\n }\n }\n}\n\nViewportController {\n id: controller\n viewport: viewPort\n\n // Define all your UI routes that connect paths to UI components.\n ViewportControllerRoute {\n route: /main:\\/\\/test\\/.*/\n sourceComponent: hiComponent\n viewportType: \"popup\" \n }\n\n ViewportControllerRoute {\n route: /about:\\/\\/aseman\\/.*/\n // You can also use `source` property and pass component's url to it.\n sourceComponent: aboutComponent\n viewportType: \"page\" \n }\n}\n\nComponent {\n id: hiComponent\n Page {\n anchors.fill: parent\n \n Button {\n text: \"About\"\n anchors.centerIn: parent\n /*\n * You can also pass properties to object using js map\n * or using html query way (about://aseman/test?text=about&color=blue)\n */\n onClicked: controller.trigger(\"about://aseman/test\", {\"text\": \"about\"})\n }\n }\n}\nComponent {\n id: aboutComponent\n Label {\n anchors.fill: parent\n verticalAlignment: Text.AlignVCenter\n horizontalAlignment: Text.AlignHCenter\n \n // If you specify a url property, triggered url will put to this property\n property string url\n \n // If you specify a properties property, initial properties will put to this property\n property variant properties\n }\n}\n```\n\nThere is also an attached property, you can use to call trigger function in the Viewport's childeren components:\n\n```js\nMouseArea {\n onClicked: Viewport.controller.trigger(\"about://aseman/test\", {\"text\": \"about\"})\n}\n```\n\n`Viewport.controller` method returns first controller of the parent Viewport. If you wish to get all controllers as array, use `Viewport.allController` method instead.\n\n#### ViewportType Attached Property\n\nUsing `ViewportType` attached property, you can change some attributes on the current Viewport's type item:\n\n```js\nViewportType.gestureWidth: 10 // Change touch/mouse gesture area's width\nViewportType.touchToClose: false // Disable touch background to close feature\nViewportType.blockBack: true // Disable press back to close feature\nViewportType.open: false // Close current page of the viewport\nViewportType.transformOrigin: Qt.point(10, 20) // Sets transform origin on some types like menu\n```\n\n### AsemanQml.Network\n\nNetwork module provides components to send network requests. For Example `NetworkRequestManager` and `NetworkRequest` could send http requests like post, get, put and etc.\nBelow example shows you a simple usage of network module.\n\n```js\nimport AsemanQml.Network 2.0\n\nButton {\n text: \"Signup\"\n onClicked: networkManager.post(signInRequest) // get, post, put or ...\n}\n\nBusyIndicator { running: signInRequest.refreshing }\n\nNetworkRequestManager { id: networkManager }\n\nNetworkRequest {\n id: signInRequest\n contentType: NetworkRequest.TypeJson\n url: \"https://example.com/auth/signIn\"\n headers: {\n \"Authorization\": \"Bearer ...\",\n }\n\n // Properties will post as json file map\n property string username: \"test\"\n property string password: \"pass1234\"\n \n // If you specified url property with TypeForm, It will send file, Else send it as string\n property url filePath\n\n onServerError: ; // server error codes\n onClientError: ; // client error codes\n onSuccessfull: {\n // Response contains response map if it's json\n // or if not response text\n console.debug(response.token)\n }\n}\n```\n\nYou can create many simple request files in your project and every time you need them, just send them to the server using NetworkRequestManager and get your response.\n\n### AsemanQml.Models\n\nModels module provide some ready to use models like `CountriesModel` and `FileSystemModel` and Also provide a new Model mechanism that make works with models easier on the QML.\n\n#### AsemanListModel\n\nAsemanListModel provides a model component for advanced usage of QML. Below example shows how to use AsemanListModel in your code:\n\n```js\nAsemanListModel {\n id: model\n data: [\n {\n \"name\": \"bardia\",\n \"age\": 30 + 2 // It supports js values too.\n },\n {\n \"name\": \"amir\",\n \"age\": 31\n }\n ]\n // cachePath store model data to the file and restore it everytime\n // Application load again\n cachePath: AsemanApp.homePath + \"/ages.model\"\n}\n```\n\n**Note**: `AsemanApp.homePath` returns standard path to store config files.\n\nAnd You can manage your model using below methods:\n\n```js\nvar value = model.get(idx, \"propertyName\");\nvar allValues = model.get(idx); // allValues.propertyName is equal to value\nmodel.clear();\nmodel.append({\"name\", \"bardia\", \"age\": 30});\nvar data = model.data; // Get all data of the model as list\nvar json = Tools.variantToJson(data); // Convert data to json string\n```\n\n#### AsemanListModelSource\n\nYou can use `AsemanListModelSource` component to pass two or more different sources to the `AsemanListModel`:\n\n```js\nAsemanListModel {\n AsemanListModelSource {\n // obj is an object that has a result property, returns variant/array/map\n source: obj.result\n path: \"data->users[2]->childeren\"\n }\n AsemanListModelSource {\n source: { title: \"test\", list: [a, b, c, d] }\n path: \"list\"\n }\n}\n```\n\nIt useful when for example you want to merge two or more requests responses to one model.\n\n#### Model's Hints\n\nThere is a mechanism to arrange and change model's data in easier way without even one line JavaScript code using Aseman's Models mechanism.\nThis feature is Hints. You can rename keys (for example change user_name to userName), even change paths of them (for example change results.user.name to userName), change values formats (for example change gregorian date to jalali date), or ... using hints.\n\n```js\nAsemanListModel {\n ...\n\t\n // Copy \"results.user.name\" to \"userName\"\n ModelCopyHint {\n path: \"results->user->name\"\n targetPath: \"userName\"\n }\n \n // Make all \"results.user.nickname\" values upperCase\n ModelFormatHint {\n path: \"results->user->nickname\"\n method: function(arg) { return arg.toUpperCase() }\n }\n \n // Convert all keys to camel case.\n ModelCamelCaseHint {\n }\n \n // Delete \"results.images[0].caption\"\n ModelDeleteHint {\n\t\tpath: \"results->images[0]->caption\"\n }\n}\n```\n\n### AsemanQml.Sql\n\nSql module provides some tools to add SQL features to your applications. It supports SQLite, MySQL, PostgreSQL and also MSSQL. Below example shows how to use it:\n\n```js\nimport AsemanQml.Sql 2.0\n\nAsemanListModel {\n id: model\n data: mysql.select(\"INNER JOIN ...\", \"title LIKE :title and id > :id\", {title: \"hi%\", id: 10})\n // Also you can use it without join and also where arguments.\n}\n\nSqlObject {\n id: mysql\n databaseName: \"TestDB\"\n driver: SqlObject.MySQL\n host: \"127.0.0.1\"; port: 3306\n userName: \"user\"; password: \"password\"\n \n table: \"TestTable\"\n primaryKeys: [\"id\"]\n property int id: 10\n property string title\n property date updateTime\n \n Component.onCompleted: {\n \t// It fetchs title and updateTime of id=10 to title and updateTime properties\n fetch();\n \n title = \"Hi :)\"\n update(); // Update value,\n }\n}\n\nSqlObject {\n id: sqlite\n databaseName: \"/Path/to/db\"\n driver: SqlObject.SQLite\n \n Component.onCompleted: {\n var result = query(\"SOME QUERY\");\n // You can use queryAsync(\"SOME QUERY\", {...binds...}, function(res){...})\n // Method to run queries in async mode\n console.debug( Tools.variantToJson(result) );\n }\n}\n```\n\n### AsemanQml.MaterialIcons and AsemanQml.Awesome\n\nThese two modules provide access to the MaterialIcons and FontAwesome font icons. The usage is easy:\n\n```js\nimport AsemanQml.MaterialIcons 2.0\nimport AsemanQml.Awesome 2.0\n\nLabel {\n font.family: Awesome.family\n text: Awesome.fa_github\n}\nLabel {\n font.family: MaterialIcons.family\n text: MaterialIcons.mdi_github\n}\n```\n\n## Advanced options using C++\n\nIf you need to access advanced options or create components inherited from QtAseman or even have further use using C++ simply add below line to your `.pro` file and use components there:\n\n```\nQT += asemancore asemangui asemanqml asemannetwork asemanwidgets asemangeo\n```\n\n### AsemanHttpServer\n\nAsemanHttpServer is a [qhttp](https://github.com/azadkuh/qhttp) fork, that create routing API for it. So it's async, thread supports and easy to use:\n\n```c++\nAsemanHttpServer server;\n\n// Sync\nserver.route(\"/hello/sync\", AsemanHttpServer::HttpMethod::GET, [](const AsemanHttpServer::Request &) {\n return QStringLiteral(\"Hello Sync\");\n});\n\n// ASync\nserver.route(\"/hello/async\", AsemanHttpServer::HttpMethod::GET, [](const AsemanHttpServer::Request &, AsemanHttpServer::Responder *responder) {\n responder->write(QStringLiteral(\"Hello ASync\"));\n});\n\n// ASync Threaded (It will run on another thread automatically)\nserver.route(\"/hello/async\", AsemanHttpServer::HttpMethod::GET, [](const AsemanHttpServer::Request &, AsemanHttpServer::Responder *responder) {\n // Runs on another thread\n responder->write(QStringLiteral(\"Hello ASync\"));\n}, true);\n```\n\n## Documents\n\nWe have started to document all modules and their essential details using Doxygen standards we will put them in documents folder, but the full documentation process is under developing and not completed yet.\n\n## Donation\n\n[Help us to keep QtAseman up to date](https://aseman-land.github.io/QtAseman)\n"
},
{
"path": "SourceDiary.sh",
"content": "#! /bin/sh\n# Set the home if not already set.\nif [ \"${ASEMAN_SRC_PATH}\" = \"\" ]; then\n ASEMAN_SRC_PATH=\"`echo $0 | grep ^/`\"\n if [ \"$ASEMAN_SRC_PATH\" = \"\" ]; then\n\tASEMAN_SRC_PATH=\"$PWD\"/\"$0\"\n fi\n cd `dirname $ASEMAN_SRC_PATH`\n ASEMAN_SRC_PATH=$PWD\n cd -\nfi\n\ncd $ASEMAN_SRC_PATH\nOUTPUT=\"`find -name '*.h' -type f` `find -name '*.cpp' -type f` `find -name '*.ui' -type f` `find -name '*.qrc' -type f` `find -name '*.pro' -type f` `find -name '*.pri' -type f` `find -name '*.qml' -type f` `find -name '*.py' -type f` `find -name '*.java' -type f` `find -name '*.js' -type f` `find -name '*.html' -type f` `find -name '*xml' -type f` `find -name '*.ts' -type f` \"\n\nwc -mwl $OUTPUT\necho \" in the \"`echo $OUTPUT | wc -w`\" Files\"\n"
},
{
"path": "aseman.pri",
"content": "DEFINES += QASEMAN_STATIC\r\ninclude (src/src.pri)\r\n"
},
{
"path": "aseman.pro",
"content": "load(qt_parts)\r\nsystem($$[QT_INSTALL_BINS]/syncqt.pl -version 3.1.5 -outdir $$OUT_PWD)\r\n"
},
{
"path": "debian/.directory",
"content": "[Dolphin]\nGroupedSorting=true\nSortRole=type\nTimestamp=2020,4,18,0,53,2\nVersion=4\nViewMode=1\n"
},
{
"path": "debian/changelog",
"content": "qtaseman (3.1.5-1aseman-focal) focal; urgency=medium\n\n * Add error callback to queryAsync.\n * Add statusBarStyle on iOS\n\n -- Aseman IO