From 784f5ee16ce2c8aab64bdbea4dfccc33e7857cff Mon Sep 17 00:00:00 2001 From: Uwe Rathmann Date: Sat, 29 Sep 2018 18:29:51 +0200 Subject: [PATCH] README changed --- README.md | 23 +++++++++++++++++++---- 1 file changed, 19 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 061342da..c06621f0 100644 --- a/README.md +++ b/README.md @@ -15,11 +15,26 @@ 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). +The code already provides a solid fundament for an application with +currently ~150K lines of pure C++/GUI code. As expected it results +in a good startup performance a nd low memory footprint. +Nontheless the current state of the project is lacking in areas like +documentation or offering appealing default skins. Furthermore +the current selection of implemented controls is limited by the needs +of the driving projects. + +QSkinny is sopposed to run in all environments, that are supported by Qt/Quick, +but only Linux is actively tested so far. + +Currently it supports all version of Qt >= 5.6, but it is intended to always support: + +- Qt 5.6 +- The current long term supported ( LTS ) version of Qt +- The current version of Qt + +If you want to know more about the (Q)Skinny or even like to give it a specific +direction you can contact support@qskinny.org. This is a screenshot of a sample automotive UI (see examples/automotive):