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.
41 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 f3ebc74f44 playing with the inputpanel example to get the virtual keyboard running 2017-07-28 13:06:59 +02:00
doc rcc: Use the right binary when invoking manually (#35) 2017-07-26 13:18:01 +02:00
examples RadioControl removed from automotive example. It is not yet used and 2017-07-27 15:52:16 +02:00
inputcontext playing with the inputpanel example to get the virtual keyboard running 2017-07-28 13:06:59 +02:00
playground playing with the inputpanel example to get the virtual keyboard running 2017-07-28 13:06:59 +02:00
src playing with the inputpanel example to get the virtual keyboard running 2017-07-28 13:06:59 +02:00
support better debug infos about shortcuts 2017-07-26 13:21:10 +02: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 rcc: Use the right binary when invoking manually (#35) 2017-07-26 13:18:01 +02:00
TODO initial commit 2017-07-21 18:21:34 +02:00
qskconfig.pri initial commit 2017-07-21 18:21:34 +02:00
qskinny.pro QskLineEdit/QskImage moved to playground 2017-07-24 07:48:36 +02:00

README.md

QSkinny

The (Q)Skinny library contains a set of lightweight Qt Quick Controls.

It can be used from C++ and/or QML application code.

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