Reusable Status QML components
Go to file
Pascal Precht 041c11fb94 feat(StatusBadge): introduce `borderColor` and `hoverBorderColor`
`StatusBadge` uses a border with same color as its underlying component
to create "fake space" (see `StatusNavTabButton`).

The color depends on the parent component background and its state,
which the `StatusBadge` doesn't know about by itself, so the border color
has to be set explicity whereever it's desired.

This commit introduces (default) colors for the border based on where
badge is used.
2021-05-26 15:32:59 +02:00
sandbox feat(StatusBadge): introduce `borderColor` and `hoverBorderColor` 2021-05-26 15:32:59 +02:00
src feat(StatusBadge): introduce `borderColor` and `hoverBorderColor` 2021-05-26 15:32:59 +02:00
.gitignore feat: Set up catalog app (sandbox) 2021-05-05 07:55:43 +02:00
README.md chore(README): add StatusQ.Layout module to readme 2021-05-20 11:23:59 +02:00

README.md

Status QML

An emerging reusable 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 sandbox.pro 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/sandbox
$ qmake sandbox.pro -spec macx-clang CONFIG+=debug CONFIG+=x86_64 && /usr/bin/make qmake_all
$ make

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

$ ./bin