In updating some frameworks I took a look at the kdelibs coding style
(Is there a frameworks coding style, if not maybe it should be
created?) and especially the Qt Includes section seems a bit backwards
from what I see in actual code in frameworks.
<a href="https://techbase.kde.org/Policies/Kdelibs_Coding_Style#Qt_Includes" title="https://techbase.kde.org/Policies/Kdelibs_Coding_Style#Qt_Includes">https://techbase.kde.org/Policies/Kdelibs_Coding_Style#Qt_Includes</a> it
suggests using QtCore/QString instead of QString for example but I've
not seen QtWidgets/QButton or similar in include statements in the
frameworks I've dealt with so far. Are we suggesting the opposite for
that section at least? Should we put together a Frameworks coding
policy (since kdelibs coding policy is what is documented there, but
frameworks aren't kdelibs) or update that page to what we suggest for
frameworks coding policy? I'm willing to do the wiki changes/make a
new page, just would like some feedback before I get started I guess.
Or if such a policy already exists, maybe we should link to it from
the Policies wiki page.
|SDDM-KCM In Review||7|
|How and what does (plasma theme) caching operate? / KSharedDataCache issue?||3|
|Review Request 110834: Cache the result of the KDE::stat calls in KDirListerCache::slotFileDirty||13|
|X11 expert help needed||6|
|CI Requirements - Lessons Not Learnt?||3|
|Review Request: Fix FindXine.cmake to use pkg-config instead of xine-config||14|
|Update the feature plan!||3|
|Moving KDots to KDE Review||5|
|Review Request 122403: [OS X] adaptations to phonon component.||1|