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.
189 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 b083479b21 using QString() instead of QString::null 2018-01-16 20:34:54 +01:00
doc rcc: Use the right binary when invoking manually (#35) 2017-07-26 13:18:01 +02:00
examples QskScrollArea once more changed, this time again without having to copy 2018-01-16 20:26:18 +01:00
inputcontext making clazy happier 2017-10-30 08:33:43 +01:00
playground skins factories can be loaded as plugins 2018-01-03 11:57:05 +01:00
skins some auto scrolling modes added 2018-01-16 12:13:38 +01:00
src using QString() instead of QString::null 2018-01-16 20:34:54 +01:00
support iterating over all fonts 2018-01-06 17:57:33 +01:00
tools initial commit 2017-07-21 18:21:34 +02:00
.gitignore playing with the inputpanel example to get the virtual keyboard running 2017-07-28 13:06:59 +02:00
COPYING initial commit 2017-07-21 18:21:34 +02:00
README.md README changed 2017-07-30 14:31:28 +02:00
TODO initial commit 2017-07-21 18:21:34 +02:00
qskconfig.pri don't autoenable sanitize in debug mode - compilation time is too slow 2017-12-12 20:14:31 +01:00
qskinny.pro skins factories can be loaded as plugins 2018-01-03 11:57:05 +01:00

README.md

QSkinny

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 current selection of implemented controls is driven by the needs of specific projects and therefore may feel a bit random. Conceptually, though, any type of control fits into QSkinny, as long as it is usable from C++ (as opposed to only QML).

This is a screenshot of a sample automotive UI (see examples/automotive):

Automotive screenshot