status-desktop/ui/StatusQ
Lukáš Tinkl 2c46764829 fix(MembersTabPanel): Buttons in the Member tab do not work
- move the MouseArea into `background` so that it doesn't obscure the
potential action buttons
- fixup SB page

Fixes #16426
2024-10-03 14:34:12 +02:00
..
doc feat(Communities): changes in import popup for private keys 2023-08-07 15:26:35 +03:00
include/StatusQ StatusQ: ConstantRole - custom SFPM proxy role added (#16405) 2024-09-25 15:13:53 -04:00
sandbox chore(StatusMemberListItem): refactor to use ItemDelegate 2024-09-12 15:04:22 +02:00
sanity_checker
scripts
src fix(MembersTabPanel): Buttons in the Member tab do not work 2024-10-03 14:34:12 +02:00
tests StatusQ: ConstantRole - custom SFPM proxy role added (#16405) 2024-09-25 15:13:53 -04:00
CHANGELOG.md chore: remove dictionary 2023-06-09 14:50:08 -04:00
CMakeLists.txt StatusQ: ConstantRole - custom SFPM proxy role added (#16405) 2024-09-25 15:13:53 -04: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