On Monday 24 August 2015 15:34:27 Milian Wolff wrote:
On Monday, August 24, 2015 2:48:14 PM CEST David Faure wrote:
On Monday 24 August 2015 13:04:24 Milian Wolff wrote:
[QK]LockFile was too unreliable on linux
That sounds like judging QLockFile based on how badly KLockFile worked :)
On Monday, August 24, 2015 2:48:14 PM CEST David Faure wrote:
On Monday 24 August 2015 13:04:24 Milian Wolff wrote:
[QK]LockFile was too unreliable on linux
That sounds like judging QLockFile based on how badly KLockFile worked :)
IOW, it doesn't sound like you actually tried Qt5's
On Monday 24 August 2015 13:04:24 Milian Wolff wrote:
[QK]LockFile was too unreliable on linux
That sounds like judging QLockFile based on how badly KLockFile worked :)
IOW, it doesn't sound like you actually tried Qt5's QLockFile.
Anyhow, if DBus works, DBus works. I just wanted to avoid FUD
On Monday 24 August 2015 01:03:22 Kevin Funk wrote:
On Saturday 22 August 2015 11:34:38 David Faure wrote:
On Wednesday 19 August 2015 09:08:35 Boudewijn Rempt wrote:
A windows or osx application for the masses must:
* not have any pre or post install procedures
* not start any process
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
- kglobalaccel5
- kioslave
- klauncher
KGlobalAccel should only be started if there is something trying to
interact with KGlobalAccel
On Saturday 22 August 2015 11:34:38 David Faure wrote:
On Wednesday 19 August 2015 09:08:35 Boudewijn Rempt wrote:
A windows or osx application for the masses must:
* not have any pre or post install procedures
* not start any process except the application itself
* avoid ipc as much as
On Monday, August 24, 2015 1:03:22 AM CEST Kevin Funk wrote:
On Saturday 22 August 2015 11:34:38 David Faure wrote:
On Wednesday 19 August 2015 09:08:35 Boudewijn Rempt wrote:
A windows or osx application for the masses must:
* not have any pre or post install procedures
* not start
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
- kglobalaccel5
- kioslave
- klauncher
KGlobalAccel should only be
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
-
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
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
On Wednesday 19 August 2015 09:08:35 Boudewijn Rempt wrote:
A windows or osx application for the masses must:
* not have any pre or post install procedures
* not start any process except the application itself
* avoid ipc as much as possible
* find all resources and plugins relative to itself
12 matches
Mail list logo
