Re: Porting to Qt5

2013-04-09 Thread Sebastian Sauer
On 04/09/2013 03:36 AM, Kevin Krammer wrote: On Monday, 2013-04-08, Boudewijn Rempt wrote: On Mon, 8 Apr 2013, Kevin Krammer wrote: On Monday, 2013-04-08, Boudewijn Rempt wrote: * replace kconfig with qsettings Doesn't that lose all support for OSV and admin default values, immutable settings

Re: Porting to Qt5

2013-04-08 Thread Kevin Krammer
On Monday, 2013-04-08, Boudewijn Rempt wrote: > On Mon, 8 Apr 2013, Kevin Krammer wrote: > > On Monday, 2013-04-08, Boudewijn Rempt wrote: > >> * replace kconfig with qsettings > > > > Doesn't that lose all support for OSV and admin default values, immutable > > settings, build time generated conf

Re: Porting to Qt5

2013-04-08 Thread Kevin Krammer
On Monday, 2013-04-08, Sven Langkamp wrote: > On Mon, Apr 8, 2013 at 10:22 PM, Kevin Krammer wrote: > > On Monday, 2013-04-08, Boudewijn Rempt wrote: > > > * replace kconfig with qsettings > > > > Doesn't that lose all support for OSV and admin default values, immutable > > settings, build time g

Re: Porting to Qt5

2013-04-08 Thread Boudewijn Rempt
On Mon, 8 Apr 2013, Kevin Krammer wrote: On Monday, 2013-04-08, Boudewijn Rempt wrote: * replace kconfig with qsettings Doesn't that lose all support for OSV and admin default values, immutable settings, build time generated config access instead of typo-prone string based access, and so on?

Re: Porting to Qt5

2013-04-08 Thread Sven Langkamp
On Mon, Apr 8, 2013 at 10:22 PM, Kevin Krammer wrote: > On Monday, 2013-04-08, Boudewijn Rempt wrote: > > > * replace kconfig with qsettings > > Doesn't that lose all support for OSV and admin default values, immutable > settings, build time generated config access instead of typo-prone string >

Re: Porting to Qt5

2013-04-08 Thread Kevin Krammer
On Monday, 2013-04-08, Boudewijn Rempt wrote: > * replace kconfig with qsettings Doesn't that lose all support for OSV and admin default values, immutable settings, build time generated config access instead of typo-prone string based access, and so on? Cheers, Kevin -- Kevin Krammer, KDE de

Re: Porting to Qt5

2013-04-08 Thread Sebastian Sauer
On 04/08/2013 06:05 PM, Boudewijn Rempt wrote: Well, I'm fine with having moc_bla.cpp includes where Q_PRIVATE_SLOT is used. I don't think there's any real problem there. Its a problem when somebody switches cmake<=>qmake (both directions) cause of there moc filename incompatibilities. Anyhow,

Re: Porting to Qt5

2013-04-08 Thread Boudewijn Rempt
On Mon, 8 Apr 2013, Sebastian Sauer wrote: Q_PRIVATE_SLOTS is indeed a problem. For moc-includes: The fundamental problem here is that qmake uses a different moc filename layout then cmake. It cannot be changed in qmake to match to the cmake ones. Lukely this days we got automoc and that means

Re: Porting to Qt5

2013-04-08 Thread Sebastian Sauer
Wow, wow. Fan-tas-tic work! On 04/08/2013 04:49 PM, Boudewijn Rempt wrote: Hi, No doubt you've seen my qt5 porting branch. I was surprised at how far I came, even though I was tempted to bang my head against my desk a couple of times (especially over the Q_PRIVATE_SLOT thing -- while all I h