168492376
/
qskinny
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
A lightweight framework on top of the Qt scene graph and only few classes from Qt/Quick. It is usable from C++ and/or QML.
2,544 Commits 10 Branches 0 Tags 48 MiB
C++ 96.9%
CMake 2.2%
GLSL 0.4%
QML 0.3%
C 0.2%
Go to file
Uwe Rathmann 6a11179cc9 Merge branch 'master' into features/drawer 2023-10-30 17:10:03 +01:00
.github/workflows Add windows style 2023-05-09 07:49:48 +02:00
cmake BSD-3-Clause license 2023-04-06 09:23:37 +02:00
doc QskGestureRecognizer using event filtering 2023-10-05 08:59:30 +02:00
examples layout issues fixed 2023-10-17 14:32:22 +02:00
inputcontext BSD-3-Clause license 2023-04-06 09:23:37 +02:00
playground much easier implementation used - the only hack is about updating the 2023-10-27 07:58:27 +02:00
qmlexport progress bars: Introduce progress ring and refactor 2023-08-09 08:33:05 +02:00
skins popup duration changed 2023-10-24 11:40:00 +02:00
src QskMenu using position for transitioning, QskSlideIn code removed 2023-10-30 16:59:17 +01:00
support respect the ordering from the skin factories instead of sorting them 2023-06-20 09:20:51 +02:00
tools BSD-3-Clause license 2023-04-06 09:23:37 +02:00
.clang-format fix lower case 2023-08-09 08:30:56 +02:00
.gitignore bye,bye qmake, say hello to cmake 2023-04-05 17:47:15 +02:00
.qmake.conf project file include mechanism based on QMAKEFEATURES 2019-03-31 13:05:25 +02:00
.uncrustify upgraded to uncrustify 0.76.0 - still not happy with the C++ beautifier 2023-02-28 15:49:42 +01:00
CMakeLists.txt BSD-3-Clause license 2023-04-06 09:23:37 +02:00
COPYING BSD-3-Clause license 2023-04-06 09:23:37 +02:00
README.md BSD-3-Clause license 2023-04-06 09:23:37 +02:00

README.md

QSkinny

CMake Build Matrix

The (Q)Skinny library is a framework built on top of the Qt scene graph and very few core classes from Qt/Quick. It offers a set of lightweight controls, that can be used from C++ and/or QML.

Doing the implementation in C++ allows to make use of the "scene graph" classes. Building controls from scene graph nodes allows for a lighter implementation than found with stacking "heavier" objects like QObject or QQuickItem. Offering a full featured C++ API allows the application code to benefit from following the same strategies.

Being "skinny" also means a design that separates concerns between the API and logic of the controls themselves, the styling of these controls, and the delegated rendering of the controls to the screen.

The code already provides a solid fundament for an automotive GUI with currently ~300K lines of pure C++ code. As expected it results in a good startup performance and a low memory footprint.

Nontheless QSkinny is lacking in areas like documentation or appealing default skins. The QML API has not been completed after reaching a proof of concept state. Furthermore the current selection of the implemented controls is limited to the needs of the driving projects.

QSkinny is supposed to run on all platforms being supported by Qt/Quick. But so far only Linux is actively tested. It might support all versions Qt >= 5.15, but you can rely on:

  • Qt 5.15
  • current long term supported ( LTS ) version of Qt
  • current version of Qt

On debian bullseye these packages need to be installed: build-essential qt-qmake qtbase5-dev qtbase5-private-dev qtdeclarative5-dev qtdeclarative5-private-dev libqt5svg5-dev.

Optional: When enabling the hunspell feature the following package needs to be installed: libhunspell-dev

Optional: When enabling the pinyin feature the following package needs to be installed: libimepinyin-dev

If you want to know more about QSkinny - or even like to give it a specific direction - please contact support@qskinny.org.

IOT dashboard

Contributing to QSkinny

QSkinny is licensed under the BSD 3 Clause License ( https://opensource.org/license/bsd-3-clause ). However we want to be able to offer more licenses on request.

If you are fine with these terms, you are welcome to contribute to QSkinny by completing the following steps:

  1. Agree to the terms of the Contributor Agreement. You can create a pull request first, then the licensing bot will check automatically whether you already signed the Agreement or not. If you have not signed it yet, it will take you to the Agreement to agree.
  2. Submit your pull request for review.