uwerat
uwerat
Qt offers a homebrew designsystem "Fusion": https://doc.qt.io/qt-6/qtquickcontrols-fusion.html We do not have a proper specification ( beside the code ) and Fusion differs between Qt/Quick and Qt/Widgets. It looks the same...
We need a control for scrollbars. The current implementation of QskScrollView implements the scroll bars as subcontrols to avoid 2 additional QQuickItems ( horizontal/vertical scroll bar ). However this makes...
Material defines 2 different types of visual feedback with the term "ripple". Flutter calls them Highlight and Splash. At the moment these effects need to be implemented by additional subcontrols...
While Qt takes care of keeping the public API stable this is not the case for the semi-public ( a.k.a as private ) headers. Unfortunately it is not possible to...
With Qt 6.6 a new renderer for QPainterPath ( also fonts ) has been introduced: https://www.qt.io/blog/smooth-vector-graphics-in-qt-quick According to the blog it gives better results - however it seems to be...
It might be good to have specific shaders for gradients made of 2 colors or less - a very common use case. These shaders do not need precalculated color ramps...
At the moment QskTabBar is a composite made of QskTabButtons, what does not match the philosophy of QSkinny to prefer scene graph node composition. I'm not sure if there is...
While the terms "widgets" and "controls" are somehow interchangeable "widget" usually ends in more intuitive class names ( QskInputWidget vs QskInputControl ) and avoids clashes with other terminologies ( f.e...
Instead of storing 3 different hints ( TextColor/StyleColor/LinkColor ) we can store them in one hint as QskTextColors
Not all Subcontrols are "rectangular" ( f.e arcs ) and the bounding rectangle might be not accurate enough for handling pointer/hover events. Might be better to use return a QPainterPath...