Re: Allow to add a ActionButton in KPageDialog

2014-07-03 Thread Kevin Ottens
On Thursday 03 July 2014 19:50:35 laurent Montel wrote: > Hi, > During kdepim porting I saw that it was not possible to add a ActionButton > as QButtonBox is protected. > => we can do it if we create a derived class. > But it’s not a very easy method for just add a button. > > I would like to add

Re: [Kde-hardware-devel] OSX/MacPorts KDE CI System: Build failed for framework solid

2014-07-03 Thread Marko Käning
Hi Kai Uwe & Kevin, I've put the patch from your kde-hardware-devel response [1] into the OSX KDE CI system and it built just fine - like it did before. This means, all frameworks of tiers 1 to 4 (i.e. also porting aids stuff) as documented on [2] build again just fine on OSX by now. :-) So, ple

kdelibs4support FindGettext

2014-07-03 Thread Jonathan Riddell
kdelibs4support ships an old copy of FindGettext.cmake. This is incompatible with the version shipping in cmake and causes some compile failures. Can I remove it? Jonathan ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mai

Allow to add a ActionButton in KPageDialog

2014-07-03 Thread laurent Montel
Hi, During kdepim porting I saw that it was not possible to add a ActionButton as QButtonBox is protected. => we can do it if we create a derived class. But it’s not a very easy method for just add a button. I would like to add a new method to do it. I created a patch for it. What do you think a

Re: Directory structure under share/

2014-07-03 Thread Aleix Pol
On Thu, Jul 3, 2014 at 6:45 PM, Nicolás Alvarez wrote: > The subdirectories of prefix/share/ that KF5 installs seem > inconsistent. For example, KAuth installs some data files in > share/kf5/kauth, while KService services go to share/kservices5. > > Do we prefix things with kf5/ or not? Or is the

Directory structure under share/

2014-07-03 Thread Nicolás Alvarez
The subdirectories of prefix/share/ that KF5 installs seem inconsistent. For example, KAuth installs some data files in share/kf5/kauth, while KService services go to share/kservices5. Do we prefix things with kf5/ or not? Or is there a reason why some are prefixed and some aren't? -- Nicolás __

Re: OSX/MacPorts KDE CI System: Build failed for framework solid

2014-07-03 Thread Nicolás Alvarez
2014-07-03 3:31 GMT-03:00 Kevin Ottens : > Hello, > > On Wednesday 02 July 2014 08:33:01 Marko Käning wrote: >> on OSX solid fails to build because of this: >> >> --- >> /Users/marko/WC/KDECI-builds/solid/src/solid/devices/backends/iokit/iokitdev >> ice.cpp:227:25: error: allocating an object of ab

Re: [Kde-hardware-devel] OSX/MacPorts KDE CI System: Build failed for framework solid

2014-07-03 Thread Kevin Ottens
On Thursday 03 July 2014 13:31:16 Kevin Ottens wrote: > On Thursday 03 July 2014 10:08:13 David Faure wrote: > > On Thursday 03 July 2014 09:22:45 Kevin Ottens wrote: > > > On Thursday 03 July 2014 09:12:17 Marko Käning wrote: > > > > > Please pick one ASAP. > > > > > > > > Yes, please! > > > > >

Re: [Kde-hardware-devel] OSX/MacPorts KDE CI System: Build failed for framework solid

2014-07-03 Thread Kevin Ottens
On Thursday 03 July 2014 10:08:13 David Faure wrote: > On Thursday 03 July 2014 09:22:45 Kevin Ottens wrote: > > On Thursday 03 July 2014 09:12:17 Marko Käning wrote: > > > > Please pick one ASAP. > > > > > > Yes, please! > > > > You can help us there though, please locally revert the commit I >

Re: Review Request 118263: Port polkit-kde-agent to KF5::KDELibs4Support and KF5::IconThemes

2014-07-03 Thread Aleix Pol Gonzalez
--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/118263/#review61531 --- Ship it! What's the point of letting it compile against Qt4 a

Re: Need help to port to new QT5 plugins

2014-07-03 Thread Aleix Pol
On Thu, Jul 3, 2014 at 9:59 AM, laurent Montel wrote: > Finally we investigated it with Volker and moc doesn’t expand macro. > So plugins can’t create with a macro + template. > > But it doesn’t return an error when about it. > > So I expanded manually macro in each plugins and now I can load the

Re: Review Request 118263: Port polkit-kde-agent to KF5::KDELibs4Support and KF5::IconThemes

2014-07-03 Thread Martin Bříza
--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/118263/ --- (Updated July 3, 2014, 8:48 a.m.) Review request for KDE Frameworks and P

Re: [kde-promo] KDE Frameworks 5 promo

2014-07-03 Thread Jos Poortvliet
On Tuesday 01 July 2014 23:13:24 David Faure wrote: > On Tuesday 01 July 2014 16:16:48 Jonathan Riddell wrote: > > KDE Frameworks 5 gets its first release this week, anyone want to help me > > with a Dot story and release announcement? > > For linking from the announcement, I committed source-kf-5

Re: OSX/MacPorts KDE CI System: Build failed for framework solid

2014-07-03 Thread David Faure
On Thursday 03 July 2014 09:22:45 Kevin Ottens wrote: > On Thursday 03 July 2014 09:12:17 Marko Käning wrote: > > > Please pick one ASAP. > > > > Yes, please! > > You can help us there though, please locally revert the commit I mentioned, > and confirm if that fixes the build for solid and allows

Re: Need help to port to new QT5 plugins

2014-07-03 Thread laurent Montel
Finally we investigated it with Volker and moc doesn’t expand macro. So plugins can’t create with a macro + template. But it doesn’t return an error when about it. So I expanded manually macro in each plugins and now I can load them. (kmail can be launch (but akonadiserver crashs now but it’s an

Re: OSX/MacPorts KDE CI System: Build failed for framework solid

2014-07-03 Thread Kevin Ottens
On Thursday 03 July 2014 09:12:17 Marko Käning wrote: > > Please pick one ASAP. > > Yes, please! You can help us there though, please locally revert the commit I mentioned, and confirm if that fixes the build for solid and allows to build all the way up to tier 3. I guess you might need to reve

Re: OSX/MacPorts KDE CI System: Build failed for framework solid

2014-07-03 Thread Marko Käning
Hi all, > It looks like there's a need to pay more attention to the multi-platform > aspects of libsolid when reviewing. which is why we were trying to get the OSX CI system to work during the last weeks/months. > Now we have the following choices: > ... Point 1) seems like a no-option to me