status-desktop/ui/StatusQ
Dario Gabriel Lipicar 1fc9dec4d4 feat(@desktop/wallet): handle very small currency amounts
Fixes #9013
2023-01-17 18:21:35 -03:00
..
doc feat(@desktop/wallet): Implement loading animation 2023-01-12 14:49:41 +01:00
sandbox fix(@desktop): use system locale across the application 2023-01-17 16:39:56 -03:00
sanity_checker feat(StatusQ): SanityChecker app for imports validation 2022-11-04 12:01:59 +01:00
src feat(@desktop/wallet): handle very small currency amounts 2023-01-17 18:21:35 -03:00
tests fix(wallet): fix rename account modal states 2023-01-05 22:16:44 +04:00
vendor bump vendor/SortFilterProxyModel 2022-09-21 18:20:12 +02:00
.gitmodules chore(git): add vendor/SortFilterProxyModel 2022-09-21 18:20:12 +02:00
CHANGELOG.md
CMakeLists.txt feat(StatusQ): SanityChecker app for imports validation 2022-11-04 12:01:59 +01:00
README.md chore: update README and build script 2022-09-21 18:20:12 +02:00

README.md

StatusQ

An emerging reusable QML UI component library for Status applications.

Usage

StatusQ introduces a module namespace that semantically groups components so they can be easily imported. These modules are:

Provided components can be viewed and tested in the sandbox application that comes with this repository. Other than that, modules and components can be used as expected.

Example:

import Status.Core 0.1
import Status.Controls 0.1

StatusInput {
  ...
}

Viewing and testing components

To make viewing and testing components easy, we've added a sandbox application to this repository in which StatusQ components are being build. This is the first place where components see the light of the world and can be run in a proper application environment.

Using Qt Creator

The easiest way to run the sandbox application is to simply open the provided CMakeLists.txt file using Qt Creator.

Using command line interface

To run the sandbox from within a command line interface, run the following commands:

$ git clone https://github.com/status-im/StatusQ
$ cd StatusQ
$ git submodule update --init
$ ./sandbox/scripts/build

Once that is done, the sandbox can be started with the generated executable:

$ ./build/sandbox/Sandbox