status-desktop/ui/StatusQ
Lukáš Tinkl 375de59cfa chore(SharedAddressesPermissionsPanel): optimize the speed
- don't use the expensive `ExpressionFoo` in SFPM, just use
`AnyOf/AllOf` combinations where possible
- in HoldingsSelectionModel, don't call the `getTokenByKey` twice to
construct the `text`, once is enough
- lastly, rewrite the JS helper `PermissionsHelpers.getTokenByKey` to
C++; this method gets called recursively way too often from many places

In the longterm, we should provide a specific C++ transformation model
for SharedAddressesPermissionsPanel to follow the UI requirements more
closely; that way we'd be able to fix the issues here for good

Fixes #14276
2024-04-04 16:59:26 +02:00
..
doc feat(Communities): changes in import popup for private keys 2023-08-07 15:26:35 +03:00
include/StatusQ chore(SharedAddressesPermissionsPanel): optimize the speed 2024-04-04 16:59:26 +02:00
sandbox [ProfileShowcase] Updated delegates as per design + added web tab 2024-04-02 10:21:13 +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 chore(SharedAddressesPermissionsPanel): optimize the speed 2024-04-04 16:59:26 +02:00
tests feat(wallet) skip picking flags in the random emoji picker function 2024-03-20 11:56:03 +01:00
CHANGELOG.md chore: remove dictionary 2023-06-09 14:50:08 -04:00
CMakeLists.txt feat(wallet) save/load collectibles user handled state in DB 2024-03-27 20:26:15 +01: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