Reusable Status QML components
Go to file
Alexandra Betouni f1eff6700a feat(StatusQ/Controls): Adding StatusSeedPhraseInput control
Also added an example in Inputs page

Closes #567
2022-03-17 11:24:36 +01:00
doc feat(StatusPinInput): Introduce `StatusPinInput` control 2022-02-18 09:25:05 +01:00
sandbox feat(StatusQ/Controls): Adding StatusSeedPhraseInput control 2022-03-17 11:24:36 +01:00
src feat(StatusQ/Controls): Adding StatusSeedPhraseInput control 2022-03-17 11:24:36 +01:00
tests/TestControls test(StatusInput): Add initial basic tests 2022-03-14 02:43:01 -07:00
.gitignore docs(StatusInput): Initial basic docs plus validationMode 2022-03-14 02:43:01 -07:00
CHANGELOG.md chore: cut v0.25.0 release 2022-03-07 19:11:38 +01:00
README.md feat(StatusChatListAndCategories): add drag and drop support for cate… (#349) 2021-08-26 15:33:45 -04:00
statusq.qrc feat(StatusQ/Controls): Adding StatusSeedPhraseInput control 2022-03-17 11:24:36 +01: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 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
$ ./scripts/build

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

$ ./bin/sandbox

More Documentation available on the wiki