Re: Plugin locator performance ballpark

On Monday 09 September 2013 16:48:05 David Faure wrote: On Monday 09 September 2013 14:23:10 Sebastian Kügler wrote: Martin Grässlin asked if we could offer an async API for this. Opinions? This task is mostly I/O, and a bit of CPU. Portable async I/O requires doing it in a thread. To

Re: kinterprocesswindowing, drop it or not?

On Thursday 12 September 2013 16:18:12 Aurélien Gâteau wrote: Hi, I started working on the KInterProcessWindowing (kiw) framework, which is expected to go into tier2 because it depends on KWindowSystem (tier1). kiw is made of two set of files: kmessagebox_kiw.*: KMessageBox functions to

Re: Splitting out a KX11Extras frameworks from KWindowSystems

On Monday 16 September 2013 16:51:45 Aurélien Gâteau wrote: On Monday 16 September 2013 15:07:37 Martin Graesslin wrote: Hi, KWindowSystems is a framework which looks to me like a KX11Extras framework. Most of the things inside this framework are X11 specific. Some API even has XLib

Re: EcmQt4To5Porting

On Friday 04 October 2013 10:51:07 Martin Klapetek wrote: On Fri, Oct 4, 2013 at 9:22 AM, David Faure fa...@kde.org wrote: On Wednesday 02 October 2013 14:07:31 Martin Klapetek wrote: There were 2 files recently removed from ECM which broke attica's build, this puts the removed files as

Re: workspace fails in dateandtime kcm

On Sunday 20 October 2013 11:44:48 Christoph Feck wrote: Hi, I am getting this weird error during make (not make install): /bin/sh: /local/git/KDE/base/kde-workspace- frameworks/kcontrol/dateandtime/kcmclock_actions.actions: Permission denied make[2]: ***

Re: Accessing the private of KGlobalShortcut in kglobalaccel

On Friday 22 November 2013 15:39:35 Nicolás Alvarez wrote: Why is the daemon needed? Why can't global shortcuts handling be done in-process by the library? a) not all window systems allow to read the keyboard. b) The daemon does handling like only one application can take a global shortcut. If

Re: KToolInvokation

On Sunday 01 December 2013 18:42:58 Dominik Haumann wrote: Hi Aleix, KToolInvocation::invokeHelp() was removed. We used it like this: KToolInvocation::invokeHelp(advanced-editing-tools-commandline,kate); According to https://git.reviewboard.kde.org/r/111298/, is the preferred

Suggestion: create an own framework for KGlobalAccel

Hi, at the moment KGlobalAccel is part of XmlGui which I consider semantically wrong. Global shortcuts have nothing to do with XmlGui and there are quite some examples for applications which need global shortcuts but do not use xml gui (e.g. everything in the desktop shell). My suggestion is to

Re: KPageDialog - What happened to source compatibility?

On Saturday 14 December 2013 16:18:44 Albert Astals Cid wrote: I think to remember one of the goals was that the KF5 would be as source compatible as possible. Now i see that KPageDialog is not a KDialog anymore and thus setButtons, setDefaultButton, setButtonGuiItem, etc are not available

Re: KPageDialog - What happened to source compatibility?

On Saturday 14 December 2013 16:40:23 Albert Astals Cid wrote: El Dissabte, 14 de desembre de 2013, a les 16:30:04, Martin Graesslin va escriure: On Saturday 14 December 2013 16:18:44 Albert Astals Cid wrote: I think to remember one of the goals was that the KF5 would be as source

Re: Fwd: Tracking bugs in Frameworks

On Monday 16 December 2013 11:58:35 David Edmundson wrote: I think if we did that it would be a good idea to prefix the names with a common element like frameworks-coreaddons frameworks-kio etc. I don't think it needs the prefix. For a description, we have the product description in bugzilla.

Re: Fwd: Tracking bugs in Frameworks

On Monday 16 December 2013 19:01:25 David Edmundson wrote: On Mon, Dec 16, 2013 at 6:08 PM, Martin Graesslin mgraess...@kde.org wrote: On Monday 16 December 2013 11:58:35 David Edmundson wrote: I think if we did that it would be a good idea to prefix the names with a common element like

Re: Framework metadata

On Wednesday 18 December 2013 21:35:33 Christophe Giboudeaux wrote: On Wednesday 18 December 2013 19:50:58 Alex Merry wrote: On 18/12/13 17:54, Aurélien Gâteau wrote: We need to have at least a COPYING file in there, with the full content of the license. I believe this was already

Re: Framework metadata

On Thursday 19 December 2013 21:22:36 you wrote: On Thu, Dec 19, 2013 at 9:15 PM, Martin Graesslin mgraess...@kde.org wrote: On Wednesday 18 December 2013 21:35:33 Christophe Giboudeaux wrote: On Wednesday 18 December 2013 19:50:58 Alex Merry wrote: On 18/12/13 17:54, Aurélien Gâteau

Re: Framework metadata

On Thursday 19 December 2013 14:35:29 Aurélien Gâteau wrote: On Thu, 19 Dec 2013 12:13:08 +0200, Giorgos Tsiapaliokas wrote: I definitely like the idea but I don't like xml/rdf. Why don't we just use json? Because DOAP is an existing format, so it avoids reinventing the wheel. Reminder:

Re: Macro naming

On Monday 23 December 2013 10:36:22 Alex Merry wrote: On 23/12/13 01:42, Alex Merry wrote: On 23/12/13 01:27, Aleix Pol wrote: On Mon, Dec 23, 2013 at 1:17 AM, Alex Merry k...@randomguy3.me.uk mailto:k...@randomguy3.me.uk wrote: Currently, we are not consistent about CMake macro

Re: KF5 include problems on the build.kde.org?

On Saturday 04 January 2014 15:04:58 Friedrich W. H. Kossebau wrote: Hi, I am currently struggling to have the KF5 port of Okteta not only build locally (what it does fine), but also on KDE's build server: could anybody hint to me why on the build server the file KLocalizedString is not

Re: KDE-wide Animation settings

On Saturday 04 January 2014 20:52:43 David Faure wrote: On Saturday 04 January 2014 20:19:43 Hugo Pereira Da Costa wrote: The first problem is that with kf5, the style configuration kcm expects a libkstyle_oxygen_config.so *plugin* for this configuration, whereas it was

Re: KTextEditor Frameworks question

On Saturday 04 January 2014 19:40:46 Christoph Cullmann wrote: On Saturday 04 January 2014 19:18:56 Christoph Cullmann wrote: Hi, I cleanup the frameworks branch in kate.git to only have libktexteditor lib and the KTextEditor/ktexteditor includes to be installed as public API.

Re: KDE-wide Animation settings

On Sunday 05 January 2014 10:10:48 you wrote: On 01/05/2014 09:57 AM, Hugo Pereira Da Costa wrote: On 01/05/2014 09:42 AM, Martin Graesslin wrote: On Saturday 04 January 2014 20:52:43 David Faure wrote: On Saturday 04 January 2014 20:19:43 Hugo Pereira Da Costa wrote: The first problem

Re: kguiaddons uses qpa headers?

On Sunday 23 February 2014 17:47:48 David Faure wrote: On Sunday 23 February 2014 17:02:55 John Layt wrote: Hi, I'm building all of Frameworks from scratch for the first time, using the openSUSE packages for Qt 5.2, and qguiaddons fails with: [ 24%] Building CXX object

Re: Runtime conflict with KF5Plasma and KDE 4 in same prefix

On Monday 24 February 2014 05:33:37 Michael Palimaka wrote: Hi, I have run into a strange issue when KDE 4 and KF5Plasma are installed into the same prefix (I can reliably reproduce the issue by installing/uninstalling KF5Plasma and restarting KDE). Simply, the vertical bar key | does not

Re: KLibrary: what is it good for?

On Wednesday 19 March 2014 15:19:12 Alex Merry wrote: On 19/03/14 14:29, Alex Merry wrote: While trying to clean up KDE 4 references in KService, I've been looking at KLibrary. This basically does two things: it has a factory() method that has been deprecated since before kdelibs

Re: KDE(Libs)4Support rename

On Wednesday 09 April 2014 19:33:20 Alex Merry wrote: On 09/04/14 18:38, Aleix Pol wrote: What happens with the cmake side? are we going to have to rename all KF5::KDE4Support for KF5::KDELibs4Support? Yes, that's what the changes I've got queued up require. wouldn't it be possible to

Re: kcmshell4 in frameworks and workspace repos

On Tuesday 29 April 2014 21:27:04 Burkhard Lück wrote: Hi, grepping for kcmshell4 in all frameworks and workspace repos gives me 4 hits in frameworks and 14 hits in workspace in 6 different repos. That is obviously wrong and should be fixed, right? If so, should I file a RR for each

Re: ki18n_wrap_ui and libraries

On Tuesday 29 April 2014 21:27:29 Chusslove Illich wrote: [: Martin Gräßlin :] If my understanding is correct one needs to define TRANSLATION_DOMAIN before including KLocalizedString for library code. But the CMake macro ki18n_wrap_ui does not allow to define the TRANSLATION_DOMAIN.

Re: Writing a Frameworks book at Randa

On Saturday 03 May 2014 23:56:53 Valorie Zimmerman wrote: I know I said On Sat, May 3, 2014 at 2:14 AM, Valorie Zimmerman valorie.zimmer...@gmail.com wrote: Time is short, so this is the last time I'll write. Think about what you want in your Frameworks book and commit to making it

Re: Issues for Qt5/KF5/KDE/CI system on OSX/MacPorts

On Saturday 24 May 2014 12:28:52 mk-li...@email.de wrote: 2) KGlobalAccel is also marked invalid for OSX: This framework also builds and deploys, but we had quite a discussion lately about kglobalaccel integration on MacPorts/KDE 4.12.* in order to get KDE build fine on MacPorts [2]

Re: Loading Qt 5 translations

On Monday 09 June 2014 00:04:03 Albert Astals Cid wrote: El Dimarts, 27 de maig de 2014, a les 07:08:45, Aurélien Gâteau va escriure: On Mon, May 26, 2014, at 9:41, Alexander Potashev wrote: 2014-05-26 18:17 GMT+04:00 Aurélien Gâteau agat...@kde.org: Not sure where we could put this.

Re: Oxygen + KF5 + Qt5

On Thursday 11 July 2013 10:52:02 Hugo Pereira Da Costa wrote: - the code that pass menu shadows (in the form of pixmap handles as X properties) to kwin has been disabled because: I do not know how to paint on an X11 pixmap with Qt5, and anyway this will likely be rewritten in kwin I recommend

Re: find_package(XCB ...) ?

On Sunday 28 July 2013 13:43:50 Sebastian Kügler wrote: Hi Martin, I'm facing some challenges building kde-workspace on top of Frameworks. XCB is not found, do you know which packages I need to have it found through find_package? Same as kde-workspace on Qt4. Do you have an error message?

Re: symbol lookup error in each application linking KDE4Support

On Saturday 27 July 2013 12:47:53 you wrote: On Wednesday 24 July 2013 12:01:07 Martin Graesslin wrote: Hi, when I try to run binaries which links KDE4Support (e.g. kdeinit5) I get the following symbol lookup error: [...]lib/x86_64-linux-gnu/libKDE4Support.so.5: undefined symbol

Re: symbol lookup error in each application linking KDE4Support

On Monday 29 July 2013 11:13:32 David Faure wrote: 2) check your LD_LIBRARY_PATH (empty is ok), and check thanks, that was the trick. LD_LIBRARY_PATH had of course my normal kde (4) setup included. After unsetting the variable kdeinit5 works and now I'm scared as I don't have an excuse anymore

Re: Ki18n mostly ready

On Monday 05 August 2013 16:19:07 Sebastian Kügler wrote: Hi Chusslove, On Friday, August 02, 2013 12:00:50 Chusslove Illich wrote: [: David Faure :] There's no way to keep the [insertCatalog] method for source compatibility and implement it somehow on top of the new solution?

Re: Ki18n mostly ready

On Monday 05 August 2013 20:57:33 Chusslove Illich wrote: My notion of source compatibility was that it builds and works, not only that it builds :) Is there really a point of leaving in dummy methods just so that the build can proceed, even if they do nothing? As I mentioned, my intention was

Re: Updating CMake requirement to 2.8.12 RC 1

On Wednesday 21 August 2013 08:40:43 Kevin Ottens wrote: Hello, On Tuesday 20 August 2013 23:23:30 Alexander Neundorf wrote: On Tuesday 20 August 2013, Stephen Kelly wrote: Alexander Neundorf wrote: please wait with updating the required version until 2.8.12 final is out.

Re: Updating CMake requirement to 2.8.12 RC 1

On Friday 23 August 2013 09:14:05 David Faure wrote: On Friday 23 August 2013 06:51:23 Martin Graesslin wrote: Given that it's already lots of work to keep up with the constant breakage due to changes in frameworks the outlook of also having breakage in cmake is nothing I look forward

Re: Is this task done?

On Saturday 31 August 2013 15:59:41 Albert Astals Cid wrote: Hi guys, been browsing http://community.kde.org/Frameworks/Epics/kdelibs_cleanups and seen Update QCommandLineParser from the version that landed in qtbase dev and fix compilation (including plasma-framework). At least one thing

Re: XCB vs. KModifierKeyInfoProvider

On Monday 02 September 2013 10:39:53 you wrote: On Monday 02 September 2013 09:05:27 Martin Gräßlin wrote: 3) I just don't like it and would feel very uncomfortable given that we don't have unit tests and that this could break in future if xkb.h becomes available. Why not declare the

Whoopsie in KF5::WindowSystem 5.3.0

Hi all, unfortunately we have an embarrassing bug [1] in KWindowSystem 5.3.0 which can crash any application making use of KWindowSystem on the X11 Platform. This is fixed with commit [2]. I recommend to either do a 5.3.1 release for KWindowSystem with just that commit added or at least that

Re: Supporting MSVC2010 in ktexteditor framework

On Wednesday 05 November 2014 08:53:42 Mirko Boehm wrote: Hi, On 05 Nov 2014, at 04:33, Nicolás Alvarez nicolas.alva...@gmail.com wrote: So, I hereby propose making an exception and bumping the minimum compiler version *for ktexteditor only* to MSVC2012. Opinions? I propose to

Re: Where are my systray icons cont'd

On Thursday 27 November 2014 21:28:21 Jan Grulich wrote: On Thursday 27 of November 2014 21:10 Kevin Funk wrote: Heya, I'm still missing my beloved systray icons for a few applications in Plasma 5 on Ubuntu 14.10 (using distro provided packages). I have every package installed

Re: ksycoca improvements (Re: assert in kservicetypefactory.cpp)

On Monday, August 24, 2015 10:39:57 AM CEST you wrote: On Monday 24 August 2015 10:00:43 Martin Gräßlin wrote: Am 2015-08-24 01:03, schrieb Kevin Funk: Right now whenever I start kdevelop I get the following daemons up and running on Windows: - dbus-daemon - kded5 -

Re: ksycoca improvements (Re: assert in kservicetypefactory.cpp)

On Monday, August 24, 2015 10:58:30 AM CEST Martin Graesslin wrote: On Monday, August 24, 2015 10:39:57 AM CEST you wrote: On Monday 24 August 2015 10:00:43 Martin Gräßlin wrote: Am 2015-08-24 01:03, schrieb Kevin Funk: Right now whenever I start kdevelop I get the following daemons up

Re: ksycoca improvements (Re: assert in kservicetypefactory.cpp)

On Monday, August 24, 2015 11:08:08 AM CEST Martin Graesslin wrote: I think that kglobalaccel5 is invoked as soon as KXmlGui gets involved (which KDevelop makes use of). Code in kxmlgui.git somewhat agrees: There are references to KGlobalAccel::self() in, which will initialize

Re: icons packages with frameworks

On Wednesday, October 21, 2015 4:17:57 PM CEST Jonathan Riddell wrote: > Oxygen icons used to be part of KDE Applications and it's regeneration > by the VDG has it moved to Plasma as part of desktop integration, this > gives us problems with the version numbers going from 15.04 to 5.5 and > I plan

Re: Build and test failures with Qt 5.6 and Qt 5.3

On Wednesday, November 11, 2015 10:22:13 AM CET Jan Kundrát wrote: > On Tuesday, 10 November 2015 08:34:02 CET, Martin Graesslin wrote: > > Yes, most tests don't require a WM. Especially the Net* tests > > simulate being a > > window manager. Only the KWindow* tests

Frameworks API documentation broken

Hi all, I just wanted to raise awareness of the fact that the Frameworks API documentation on api.kde.org is completely broken. Currently one only gets error 404 when clicking on the framework links and also in the search I cannot find e.g. the frameworks variant of KAboutData. Cheers Martin

Re: Build and test failures with Qt 5.6 and Qt 5.3

On Saturday, November 7, 2015 11:59:48 AM CET David Faure wrote: > > - [5.6] kwindowsystem: KWindowInfoX11Test fails tests > > Martin, can you take a look at > http://ci-logs.kde.flaska.net/0c/0c4039dc8d4c3fa9eed18a4f5604a90648fe3e84/re >

Re: Moving KWayland to frameworks

On Thursday, November 5, 2015 10:50:06 AM CET Martin Graesslin wrote: > 2. We use Qt 5.4. Given David's suggestion on having the last three released Qt releases supported, this issue will resolve itself once Qt 5.6 is released. Given that this is on the horizon I will delay the move of KWayl

Re: Build and test failures with Qt 5.6 and Qt 5.3

On Monday, November 9, 2015 6:00:43 PM CET Jan Kundrát wrote: > On Monday, 9 November 2015 08:21:21 CET, Martin Graesslin wrote: > > I'm sorry, but I'm not able to reproduce the failure on my > > local Qt 5.6 setup. > > The failures look like there is no WM running on the

Re: KGlobalAccel on ~Linux?

On Friday, November 13, 2015 5:24:51 PM CET René J.V. Bertin wrote: > Hi, > > KDE4's kglobalaccel works just fine on Mac OS X; is there a reason why the > KF5 wouldn't? because nobody ported it to Qt's new native event filter. I would love to see this enabled again for the non Linux platforms.

Re: KGlobalAccel on ~Linux?

On Friday, November 13, 2015 5:54:01 PM CET René J. V. Bertin wrote: > Martin Graesslin wrote: > > because nobody ported it to Qt's new native event filter. I would love to > > see this enabled again for the non Linux platforms. > > Hmm, I see. That's something I should look

Re: KIdleTime: early and/or failing/rejected timeout detection?

On Tuesday, November 17, 2015 5:04:09 PM CET René J. V. Bertin wrote: > > I can say for Wayland as I wrote that recently: > I'm guessing Wayland will provide a mechanism that's inspired by what Xcb > provides? eh no. As I control both the server (hello KWin) and the client (hello KWayland) I

Re: KIdleTime: early and/or failing/rejected timeout detection?

On Tuesday, November 17, 2015 2:59:57 PM CET René J.V. Bertin wrote: > KIdleTime really seems to have captured my attention - it's after all very > closely related to "problems" I've had to solve more than a few times in a > previous life. > > Currently, the MS Windows and OS X backends have 2

Moving KWayland to frameworks

Hi, after the Plasma 5.5 release I would like to move KWayland to frameworks. The main reason is that it is oddly placed in plasma-workspace as it's also a library useful for applications (example kde-connect uses it already). KWayland is designed to be a tier1/integration framework. The

Re: Policy for Dependencies

On Tuesday, October 13, 2015 10:07:18 PM CEST Jaroslaw Staniek wrote: > Hi, > Just wanted to say I'd like to minimize dependencies for Kexi on Windows > too, among other things. > > With my realistic hat on, risky ideas are like: > - depending on kdecoration to just have default icons I hope

X11 on Windows

Hi frameworks and windows devs, from the release announcement of the latest frameworks release I learned that there were multiple changes to disable finding X11 on Windows (e.g. [1]). I think such changes are wrong and I have spoken against such changes (they are wrong, CMake supports

Re: X11 on Windows

On Monday, October 12, 2015 10:01:42 AM CEST Jaroslaw Staniek wrote: > On 12 October 2015 at 08:33, Martin Graesslin <mgraess...@kde.org> wrote: > > Hi frameworks and windows devs, > > > > from the release announcement of the latest frameworks release I learned &

Re: Policy for Dependencies

On Tuesday, October 13, 2015 8:42:43 AM CEST Christoph Cullmann wrote: > Hi, thanks for raising this topic. I think it's very important that we have a general strategy for frameworks and not have thousands of micro-fixes in various frameworks. > 1) "Normal" deployment like we do in on Linux =>

Re: Policy for Dependencies

On Tuesday, October 13, 2015 2:20:31 PM CEST Christoph Cullmann wrote: > Hi, > > different take on that below: > > Hi, > > > >> On Tuesday, October 13, 2015 8:42:43 AM CEST Christoph Cullmann wrote: > >>> Hi, > >> > >> thanks for raising this topic. I think it's very important that we have a >

Re: KIdleTime : provide a settable resolution for the polling backends?

On Tuesday, November 17, 2015 8:42:31 AM CET Martin Graesslin wrote: > On Monday, November 16, 2015 1:31:02 PM CET René J.V. Bertin wrote: > > Hi, > > > > Working on modernising the OS X plugin for KIdleTime, I realised that > > there > > is no mechanism fores

Re: KIdleTime : provide a settable resolution for the polling backends?

On Monday, November 16, 2015 1:31:02 PM CET René J.V. Bertin wrote: > Hi, > > Working on modernising the OS X plugin for KIdleTime, I realised that there > is no mechanism foreseen to set the frequency at which the current system > idle time should be sampled on those platforms that need to use a

Re: Problem investigating a heap-use-after-free in kwindowsystem

On Friday, October 2, 2015 8:38:20 PM CEST Michael Pyne wrote: > On Fri, October 2, 2015 23:59:00 Albert Astals Cid wrote: > > El Friday 02 October 2015, a les 22:24:00, Martin Graesslin va escriure: > > > Hi all, > > > > > > I added a new unit test to kw

Problem investigating a heap-use-after-free in kwindowsystem

Hi all, I added a new unit test to kwin today [1] and it failed on the CI system due to the enabled ASAN with an error in kwindowsystem. I'm able to reproduce it locally, but fail to understand it. To me the code and the test conditions looks correct. Relevant part of the bt: #0 0x7f5198ac2c84

Re: RFC: split platformtheme plugin from frameworkintegration and move to kde/workspace

On Monday, December 7, 2015 3:54:31 PM CET Mark Gaiser wrote: > While at it. Why does frameworkintegration force [1] specific fonts upon > the user? > > It's fine that apparently some folks prefer Oxygen fonts over all else, but > i thoroughly dislike it. > I always end up blacklisting it in my

RFC: split platformtheme plugin from frameworkintegration and move to kde/workspace

Hi all, based on the discussion in [1] I propose that we split out platformtheme plugin from frameworkintegration into a dedicated repository and move it to kde/workspace to be released together with Plasma 5.6. The main reasoning is that this plugin only gets loaded with env variables set in

Re: Moving KWayland to frameworks

On Thursday, November 5, 2015 11:10:49 AM CET Kevin Ottens wrote: > Hello, > > On Thursday 05 November 2015 10:50:06 Martin Graesslin wrote: > > There are two things which make the move to frameworks difficult and I > > don't see a solution to it at the moment: > &g

Re: RFC: split platformtheme plugin from frameworkintegration and move to kde/workspace

On Tuesday, December 8, 2015 6:03:47 PM CET Mark Gaiser wrote: > I thought the frameworkintegration plugin was exactly that and usable for > any platform if they wish to use it. > Or is my assumption wrong and is it really only for Plasma and should > others stay away from it? well obviously it's

Re: [OS X/Wayland] using WIds created by a different process to create KMessageBox'es and other widgets/windows

On Wednesday, December 9, 2015 1:29:41 PM CET René J.V. Bertin wrote: > KWindowSystem::setMainWindow() is a different matter. Firstly, it does NOT > use the plugin architecture currently, but simply assumes that > QWindow::fromWinId() will always work (and never crash). oh that explains a lot...

Re: RFC: split platformtheme plugin from frameworkintegration and move to kde/workspace

On Wednesday, December 9, 2015 4:03:24 PM CET Aleix Pol wrote: > On Wed, Dec 9, 2015 at 3:56 PM, Mark Gaiser <mark...@gmail.com> wrote: > > On Wed, Dec 9, 2015 at 8:24 AM, Martin Graesslin <mgraess...@kde.org> wrote: > >> On Tuesday, December 8, 2015 6:03:47 PM C

Re: Moving KWayland to frameworks

On Wednesday, December 9, 2015 6:14:47 PM CET Kevin Ottens wrote: > > I just started looking into doing the replacement and noticed that I'm > > also > > using: > > * Non-static data member initializers (N2756), gcc 4.7 > > * Range-based for (N2930), gcc 4.6 > > Note that if you do that with Qt

Re: Moving KWayland to frameworks

On Thursday, December 10, 2015 1:07:42 PM CET Boudhayan Gupta wrote: > On 10 December 2015 at 12:32, Martin Graesslin <mgraess...@kde.org> wrote: > > yes, that's the annoying one which is lots of work and lots of possible > > regressions. I'm not sure whether I'm willing to

Re: kdeinit freezes on Wayland in OOM protection

On Friday, November 27, 2015 1:05:26 PM CET Michael Pyne wrote: > On Thu, November 26, 2015 13:16:04 Martin Graesslin wrote: > > we are facing a problem during the startup of Plasma on Wayland. If OOM > > protection is enabled for kdeinit and we already have a running X server, >

Re: RFC: split platformtheme plugin from frameworkintegration and move to kde/workspace

On Monday, December 14, 2015 2:40:16 PM CET Mark Gaiser wrote: > On Mon, Dec 14, 2015 at 1:37 PM, Marco Martin wrote: > > On Thursday 10 December 2015, Mark Gaiser wrote: > > > It's not just a barrier in my head. It's a waste of resources if one > > > package that doesn't need

Re: Draft split for qpt plugin from frameworkintegration

On Thursday, December 17, 2015 4:32:48 PM CET Aleix Pol wrote: > On Wed, Dec 16, 2015 at 4:12 PM, Martin Graesslin <mgraess...@kde.org> wrote: > > Hi all, > > > > following up on [1] I have prepared a split of frameworkintegration to > > move > > the QPT

Re: Draft split for qpt plugin from frameworkintegration

forgot CC to plasma On Thursday, December 17, 2015 4:32:48 PM CET Aleix Pol wrote: > On Wed, Dec 16, 2015 at 4:12 PM, Martin Graesslin <mgraess...@kde.org> wrote: > > Hi all, > > > > following up on [1] I have prepared a split of frameworkintegration to

Re: Draft split for qpt plugin from frameworkintegration

On Thursday, December 17, 2015 5:48:47 PM CET Martin Graesslin wrote: > On Thursday, December 17, 2015 4:32:48 PM CET Aleix Pol wrote: > > On Wed, Dec 16, 2015 at 4:12 PM, Martin Graesslin <mgraess...@kde.org> > > wrote: > > > Hi all, > > > > >

Draft split for qpt plugin from frameworkintegration

Hi all, following up on [1] I have prepared a split of frameworkintegration to move the QPT plugin into a dedicated repository. You can find it in [2]. Please have a look at the split repo to verify that it looks fine. If everything is OK, I'll request a new repo from sysadmins. Some general

Re: RFC: split platformtheme plugin from frameworkintegration and move to kde/workspace

On Thursday, December 10, 2015 2:39:36 PM CET Mark Gaiser wrote: > > That is why I don't get your point. It just doesn't make sense to me and > > it > > sounds being based on wrong assumptions. > > Yes, it will. Here is the proof (taking archlinux as example since it is > very much like upstream

Re: RFC: split platformtheme plugin from frameworkintegration and move to kde/workspace

On Thursday, December 24, 2015 12:16:13 PM CET Simon Lees wrote: > Hi All, > > Sorry for double posting, but after chatting with someone on IRC we > discovered that exporting QT_QPA_PLATFORMTHEME=kde or > QT_QPA_PLATFORMTHEME=gtk2 fixes the issue. For now I can just patch > enlightenment to

Re: setting default widgetStyle (and ColorScheme)

On Saturday, November 28, 2015 7:58:47 PM CET René J. V. Bertin wrote: > Olivier Goffart wrote: > > A pure KF5 appliation would anyway use the KDE platform theme plugin > > provided by KDE Frameworks. (in frameworkintegration) > > (So in other words: that code should not be executed when kde

Re: setting default widgetStyle (and ColorScheme)

On Monday, November 30, 2015 11:06:57 AM CET René J. V. Bertin wrote: > Martin Graesslin wrote: > > In my opinion: no. I even think the frameworkintegration framework should > > get removed from frameworks and moved into Plasma Workspace. Because > > that's what it is

Scope of framework integration plugin?

Hi all, there is currently a review request to add OSX specific changes to framework integration plugin [1]. This seems wrong to me. I think our framework integration plugin is about integration Qt applications into the Plasma workspace. In my opinion it should not be used anywhere else. Not

Re: Scope of framework integration plugin?

On Monday, November 30, 2015 12:59:02 PM CET Luigi Toscano wrote: > On Monday 30 of November 2015 12:48:26 Martin Graesslin wrote: > > Hi all, > > > > there is currently a review request to add OSX specific changes to > > framework integration plugin [1]. > > &g

Re: Scope of framework integration plugin?

On Monday, November 30, 2015 1:02:01 PM CET Aleix Pol wrote: > On Mon, Nov 30, 2015 at 12:48 PM, Martin Graesslin <mgraess...@kde.org> wrote: > > Hi all, > > > > there is currently a review request to add OSX specific changes to > > framework integration plug

Re: setting default widgetStyle (and ColorScheme)

On Monday, November 30, 2015 1:17:20 PM CET René J. V. Bertin wrote: > Martin Graesslin wrote: > > Is this going to turn into another shouting match? sorry what? > > > That's not the point! Any user can use whatever theme they want. The > > question is whether we shou

Re: setting default widgetStyle (and ColorScheme)

On Monday, November 30, 2015 3:01:40 PM CET René J. V. Bertin wrote: > Martin Graesslin wrote: > > what you put on review board is in my opinion not a minimal modification. > > That are lots of ifdefs and each ifdef is a huge burden for the > > framework. It means > ... &g

Re: Purpose as a KDE Framework

On Tuesday, December 1, 2015 3:01:10 PM CET Aleix Pol wrote: > Hi, > I've been working on Purpose since some months now, with the intention > of becoming a framework some day. Some information about it can be > read here: >

kdeinit freezes on Wayland in OOM protection

Hi all, we are facing a problem during the startup of Plasma on Wayland. If OOM protection is enabled for kdeinit and we already have a running X server, kdeinit freezes dead. I'm sorry for having ignored the issue for too long and had just disabled OOM protection on my system, so I never hit

Re: Review Request 126078: [OS X] modernising the KIdleTime plugin (WIP!)

On Wednesday, November 18, 2015 5:28:27 PM CET René J.V. Bertin wrote: > On Wednesday November 18 2015 15:01:59 Martin Gräßlin wrote: > > idiotic > > If we're starting to call names arguing indeed becomes pointless as the > apparent lack of actual reading my arguments already suggested. It leaves

Re: KIdleTime: early and/or failing/rejected timeout detection?

On Tuesday, November 17, 2015 6:33:17 PM CET René J. V. Bertin wrote: > Martin Graesslin wrote: > > NO POLLING! > > > > If you cannot do that on OSX, I really think it's better to not provide > > it. If you think it's unfair that there is a backend for X11 which >

Re: Where to put kwayland integration plugins

On Monday, June 6, 2016 11:26:58 AM CEST Aleix Pol wrote: > On Mon, Jun 6, 2016 at 8:32 AM, Martin Graesslin <mgraess...@kde.org> wrote: > > Hi framework-developers, > > > > in Plasma we have a repository called kwayland-integration. It provides a > >

Re: LGPL for Breeze QStyle and qtquickcontrols?

On Monday, June 6, 2016 12:17:11 PM CEST Jaroslaw Staniek wrote: > On 30 May 2016 at 17:11, Michael Pyne <mp...@kde.org> wrote: > > On Mon, May 30, 2016 14:42:43 Martin Graesslin wrote: > > > On Saturday, May 28, 2016 11:24:52 PM CEST Michael Pyne wrote: > > >

Re: LGPL for Breeze QStyle and qtquickcontrols?

On Monday, June 6, 2016 1:29:51 PM CEST Jaroslaw Staniek wrote: > On 6 June 2016 at 13:04, Martin Graesslin <mgraess...@kde.org> wrote: > > On Monday, June 6, 2016 12:17:11 PM CEST Jaroslaw Staniek wrote: > > > On 30 May 2016 at 17:11, Michael Pyne <mp...@kde.org>

Re: Replacing the "- name: All" platform wildcard

On Wednesday, June 15, 2016 10:16:19 AM CEST Andreas Cord-Landwehr wrote: > Hey all, > > in preparation for getting information about Android as supported platform > on api.kde.org, I would like to purge the "- name: All" platform wildcard > from all metainfo.yaml files and replace it by: > -

Re: Replacing the "- name: All" platform wildcard

On Wednesday, June 15, 2016 11:18:40 AM CEST Andreas Cord-Landwehr wrote: > On Wednesday, June 15, 2016 11:01:14 AM CEST Martin Graesslin wrote: > > On Wednesday, June 15, 2016 10:16:19 AM CEST Andreas Cord-Landwehr wrote: > > > Hey all, > > > > > > in prepa

Where to put kwayland integration plugins

Hi framework-developers, in Plasma we have a repository called kwayland-integration. It provides a plugin for: * KWindowSystem * KIdleTime using the KWayland client API. Thus it makes these frameworks functional on windowing system Wayland. I want to move the plugins into frameworks and are

Re: LGPL for Breeze QStyle and qtquickcontrols?

On Saturday, May 28, 2016 11:24:52 PM CEST Michael Pyne wrote: > On Sat, May 28, 2016 14:53:54 Jaroslaw Staniek wrote: > > All in all, If nobody just noted an issue with the licensing above maybe > > nobody tried to place/distribute a non-GPL software on top of Plasma? That > > would be the worst

Re: kwindowsystem crashes

On Monday, May 30, 2016 11:36:54 AM CEST Kurt Hindenburg wrote: > There are a number of lines that division by zero could happen in > frameworks/kwindowsystem/src/platforms/xcb/kwindowsystem.cpp if > displayGeometry returns a 0 QRect. I think that is what is happening with > bug 349512. urgh.

  1   2   >