a01749e2ba
* rcc: Use the right binary when invoking manually Otherwise we could run into the following error: rcc: could not exec '/usr/lib/x86_64-linux-gnu/qt4/bin/rcc': No such file or directory Makefile:626: recipe for target 'rcc/qrc_images.cpp' failed make: *** [rcc/qrc_images.cpp] Error 1 * README: add automotive screenshot (fixes #32)
27 lines
1.1 KiB
Markdown
27 lines
1.1 KiB
Markdown
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](https://github.com/uwerat/qskinny/blob/master/doc/automotive-screenshot.jpg?raw=true)
|