5b9e4faa8a
This is required to control the resource consumption in case of no usage of wallet connect Hence we load the WebEngineView only if we have active pairings and such that SDK events are expected from the paired dapps. Also: - Moved the generic WebEngineView communication bridge to StatusQ - Added basic tests for WebEngineLoader - Add a way to know when wallet is loaded (`walletReady`) - Add storybook support for mock of nim sections as context properties Updates: #12639 |
||
---|---|---|
.. | ||
.docker | ||
doc | ||
lib | ||
pch | ||
test | ||
.gitignore | ||
.gitmodules | ||
CHANGELOG.md | ||
CMakeLists.txt | ||
DOtherSide.pc.cmake | ||
LICENSE | ||
README.md | ||
meson.build |
README.md
DOtherSide
C language library for creating bindings for the Qt QML language.
Documentation: https://filcuc.github.io/DOtherSide/index.html
Currently the DOtherSide library is used by the following bindings:
- nimqml, QML bindings for the Nim programming language
- dqml, QML bindings for the D programming language
- qml-rust, QML bindings for the Rust programming language
Supported features
The following features are implementable from a binding language
- Creating custom QObject
- Creating custom QAbstractListModels
- Creating custom properties, signals and slots
- Creating from QML QObject defined in the binded language
- Creating from Singleton QML QObject defined in the binded language
Prebuilt binaries
Windows
Currently we provide the prebuilt binaries for windows through the github releases page
Linux
Currently we provide the prebuilt binaries for the following Linux distributions through the OpenSUSE OBS service
Archlinux
: here
Change log
The project change log can be read here.
Supported platforms
Currently we support the following platforms/compilers:
- Linux both 32/64bit with gcc
- Windows 32/64bit with Visual Studio 2013|2015 Community Edition
Build requirements
You need the following software:
- Qt 5.4 or higher
- Linux: gcc 4.8 or later with c++11 support or higher
- Windows: Visual Studio 2013|2015 Community Edition (Windows) or higher
Build instructions:
- Open a shell terminal inside the cloned repo
- mkdir build && cd build
- cmake ..
- make
Install Instructions
Once you built the package just type
make install
by default cmake will install to the default CMAKE prefix. If you want to customize this location type the following command during the build steps when invoking cmake
cmake -DCMAKE_INSTALL_PREFIX:PATH=/path/to/install/prefix path/to/CMakeLists.txt