History

Alex Jbanca 9be2a8d799 feat(Community Overview): Trigger chart data updates on specific actions + optimise the backend calls This commit includes the following changes: 1. Request from backend the messages count in a specific interval as opposed to all messages timestamps in that interval. 2. Update the chart end date before refreshing the data 3. Fix metrics type parsing in community service 4. Fix a bug where the new incoming data was not processed by ChartJs without a hover event on the chart. The fix here is to manually request paint() on model changes.d Issues found and not handled here: 1. On large communities the backend request can take 3 minutes to complete 2. CPU usage can easily go to 100% when switching chart tabs on large communities. All the requests are processed by the backend.		2023-08-07 11:12:21 +03:00
..
doc	feat(@desktop/wallet): add support for more NFTs media types	2023-04-11 12:40:38 -03:00
include/StatusQ	feat(ModelUtils): modelToArray: roles param made optional, support for nested models	2023-07-28 12:49:14 +02:00
sandbox	fix(StatusQ): Allow two lines text content in StatusToastMessage	2023-07-28 10:03:10 +03:00
sanity_checker	fix(StatusQ): StatusQ is QML module (#10207 )	2023-04-14 11:18:56 +03:00
scripts	fix(StatusQ/Sandbox): move and update build script	2023-02-20 20:36:05 +01:00
src	feat(Community Overview): Trigger chart data updates on specific actions + optimise the backend calls	2023-08-07 11:12:21 +03:00
tests	fix(Sandbox): Fixed hot reloading. Fixed MacOS arm64 builds. (#10562 )	2023-05-05 19:05:44 +03:00
CHANGELOG.md	chore: remove dictionary	2023-06-09 14:50:08 -04:00
CMakeLists.txt	feat: New design flows to integrate Revealing addresses...	2023-07-19 12:44:16 +02:00
README.md	fix(StatusQ/Sandbox): move and update build script	2023-02-20 20:36:05 +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 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