status-desktop/ui/StatusQ
belalshehab d0f0537c56 feat(wallet)_: add loadingIndicatorSize and mirror properties to StatusButton
- Added `loadingIndicatorSize` property to `StatusBaseButton` to allow customization of loading indicator size.
- Introduced `mirror` property in `StatusIcon` to support icon mirroring.

resolves: #1365
2024-07-04 00:19:42 +03:00
..
doc
include/StatusQ feat(StatusQ): Generic attachd type for providing model count 2024-07-01 13:59:20 +02:00
sandbox feat: Add initial support for ChartJs plugins (#14433) 2024-06-04 13:08:16 +03:00
sanity_checker
scripts
src feat(wallet)_: add loadingIndicatorSize and mirror properties to StatusButton 2024-07-04 00:19:42 +03:00
tests feat(StatusQ): Generic attachd type for providing model count 2024-07-01 13:59:20 +02:00
CHANGELOG.md
CMakeLists.txt feat(StatusQ): Generic attachd type for providing model count 2024-07-01 13:59:20 +02:00
README.md

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
$ ./scripts/build

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

$ ./build/sandbox/Sandbox