Open LeonMatthesKDAB opened 8 months ago
Also note that we may want to move some existing types out of CXX-Qt-lib into extra. Which remains to be discussed :)
qmargins for example ? Not sure that it's used by default no ?
Initially I went through the QML basic types https://doc.qt.io/qt-5/qtqml-typesystem-basictypes.html and tried to wrap those as "fundamental types" that we require, note how that has point, rect, size. And then note that QRect has API like QRect::marginsAdded, so margins are a curious one :-)
CXX-Qt-lib-extra lives for the moment in official repo. We will split after 0.7. I added QCommandLineParser/QCommandOption/QElipsedTimer.
I added QApplication in #869 In review for the moment we must find a solution for implement inherit class
Add QStandardPaths ? It can be useful. We can define setTestModeEnabled
we have discussed many times already, that we don't want to wrap everything in CXX-Qt-lib. As the maintenance burden of this would be quite high.
However, like with
KDToolBox
, we could have a repository of useful things that people have already done, but may not have the time to maintain.This would be what
CXX-Qt-lib-extra
is. A collection of wrapped Qt types that we don't really maintain ourselves, but just add whatever we or others find useful. The barrier to add types here should be quite low, not every part of the API has to be wrapped, just adding stuff is useful, even if it's not complete.On a technical level, I propose the following:
CXX-Qt-lib-extra
independent repository toKDABLabs
.CXX-Qt-lib-extra
depend on the current stable release of CXX-Qt. (we don't want to have to drag every part of CXX-Qt-lib-extra through every internal CXX-Qt change).cxx-qt
for the bridges (currently blocked on #598For a draft guideline of when to add something to CXX-Qt-lib directly vs. just to CXX-Qt-lib-extra:
lib-extra
tolib
, if/when it turns out this type is used regularly.Looking forward to hear about your opinions :)