d9feeff1a9
* Include auto generated object names for all Icons. This will help Squish tests easily identify Icons. Which is used in test case https://github.com/status-im/status-desktop/issues/6274 * Include auto generated object names for all Icons. This will help Squish tests easily identify Icons. Which is used in test case https://github.com/status-im/status-desktop/issues/6274 * Include auto generated object names for all Icons. This will help Squish tests easily identify Icons. Which is used in test case https://github.com/status-im/status-desktop/issues/6274 * refactor(isContact): rename isMutualContact to isContact BREAKING CHANGE: isMutualContact is replaced by isContact anywhere it was used * fix(StatusStackModal): init the next/finish buttons call `updateRightButtons()` also on creation to correctly initialize the Next and Finish buttons in derived classes, when one overrrides these can be seen in the Backup Seed dialog where the Next button is not enabled even though all 3 boxes are checked * feat(StatusFontSettings): Add StatusFontSettings component to change StatusMenuItems font attributes (#749) Required by #6090 * fix(StatusPinInput): `forceFocus` function exposed * fix(StatusTagSelector): corrected font size in to label Needed for https://github.com/status-im/status-desktop/issues/6349 * fix(StatusActivityCenterButton): fixed actvity icon position (#763) Closes https://github.com/status-im/status-desktop/issues/6350 * Include auto generated object names for all Icons. This will help Squish tests easily identify Icons. Which is used in test case https://github.com/status-im/status-desktop/issues/6274 * Include auto generated object names for all Icons. This will help Squish tests easily identify Icons. Which is used in test case https://github.com/status-im/status-desktop/issues/6274 * Include auto generated object names for all Icons. This will help Squish tests easily identify Icons. Which is used in test case https://github.com/status-im/status-desktop/issues/6274 Co-authored-by: Jonathan Rainville <rainville.jonathan@gmail.com> Co-authored-by: Lukáš Tinkl <lukast@status.im> Co-authored-by: Michał Iskierko <61889657+endulab@users.noreply.github.com> Co-authored-by: Sale Djenic <aleksandardjenic@status.im> Co-authored-by: Alexandra Betouni <31625338+alexandraB99@users.noreply.github.com>
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:
- StatusQ.Core
- StatusQ.Core.Theme
- StatusQ.Core.Utils
- StatusQ.Components
- StatusQ.Controls
- StatusQ.Layout
- StatusQ.Platform
- StatusQ.Popups
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