I raised the issue on python-dev again, let's see what happens. In
case they accept this then at least for the python 3 version the
python fork could be removed after a few changes on my side (for
python 2 it would have to stay, but python 2 is legacy stuff anyways,
and updates to both my and the
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/107970/
---
Review request for kde-workspace.
Description
---
I've added support
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/107983/
---
Review request for kdelibs, kwin, Aaron J. Seigo, Marco Martin, Martin
On Wed, Nov 7, 2012 at 8:11 PM, Albert Astals Cid aa...@kde.org wrote:
The data classes are finally done - all of them now use d-pointers and
none
are qobject; I've added the qobject-parsers as Kevin suggested, please
give
it a look.
You sure? I still see a lots of d-pointers missing
Hi,
what about adapting the Kdelibs Coding Style to the upcoming preparations for
the porting to Qt5? A lot of (KDE) projects follow that kdelibs one, but there
is (at least?) one rule which seems to conflict with the recommendations for
the preparations:
--- 8 ---
Qt Includes
If you add
