status-desktop/ui/StatusQ
Lukáš Tinkl 9327b483a4 fix(BeforeGetStartedModal): fix padding and (line) spacings
additionally correct the way a font is propagated from a QQC2 Control
down to our components

Fixes #6515
2022-10-28 19:19:42 +02:00
..
doc feat(StatusChart): Adding chart component (#893) 2022-09-21 18:20:15 +02:00
sandbox chore(StatusQ): fix Sandbox release build 2022-10-27 11:40:00 +02:00
src fix(BeforeGetStartedModal): fix padding and (line) spacings 2022-10-28 19:19:42 +02:00
tests fix(tests): fix building tests 2022-09-21 18:20:13 +02: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 chore: cut v0.25.0 release 2022-09-21 18:20:07 +02:00
CMakeLists.txt Fix building x86_64 solution on Mac M1 2022-09-21 18:20:12 +02: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