On Thursday 29 January 2015 12:25:57 Jan Kundrát wrote:
> On Wednesday, 28 January 2015 13:14:14 CEST, Martin Gräßlin wrote:
> > Navigation through the code is difficult, you cannot see the
> > complete change in one, but have to go through each file. This
> > is something I consider as unfortunate
On Saturday 31 January 2015 20:37:31 Christoph Feck wrote:
> On Saturday 31 January 2015 20:07:42 Eike Hein wrote:
> > [...] Qt is using gerrit and we intend to remain a major stakeholde
> > in Qt development, which means a sizable number of KDE developers
> > need to be familiar with gerrit anyway
On Thursday, August 20, 2015 05:42:39 PM Thomas Lübking wrote:
> On Donnerstag, 20. August 2015 17:22:26 CEST, Sebastian Kügler wrote:
> > That means that we need at least two ways to start a session.
>
> startkde.common.d
> startkde.wayland.d
> startkde.x11.d
>
> ls -1 | sort -t=/ -k2
>
> profi
Hi all,
back in KDE4 days the workspace libraries were listed on api.kde.org [1]. But
for the current version we don't have any API docs available. The section
"Other KDE Software" [2] lists KDE Support, KDE Extragear and Playground but
apparently nothing from what used to be KDE SC.
Does anyb
sunderstood the problem.
>
> > On Thu, Sep 10, 2015 at 1:50 PM, Allen Winter wrote:
> > > On Thursday, September 10, 2015 10:57:10 AM Martin Graesslin wrote:
> > >> Hi all,
> > >>
> > >> back in KDE4 days the workspace libraries were listed
rictor that's probably a bad
idea).
Cheers
Martin
>
> Then at least the apidox will be generated.
>
> Step 2: I need to muck with the EBN scripts so the apidox are written
> to someplace other than the default kde4 location.
>
> On Tuesday, September 15, 2015 09:23:0
:37 AM Martin Gräßlin wrote:
> > Am 2015-09-10 21:50, schrieb Allen Winter:
> > > On Thursday, September 10, 2015 10:57:10 AM Martin Graesslin wrote:
> > >> Hi all,
> > >>
> > >> back in KDE4 days the workspace libraries were listed on api
On Saturday, September 19, 2015 1:11:24 PM CEST Allen Winter wrote:
> On Saturday, September 19, 2015 07:03:40 PM Martin Graesslin wrote:
> > On Saturday, September 19, 2015 12:54:57 PM CEST you wrote:
> > > http://api.kde.org/4.x-api/workspace-apidocs/kwayland/html/index.
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
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
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
On Friday, December 4, 2015 11:28:03 AM CET Jan Kundrát wrote:
> On Friday, 4 December 2015 10:56:42 CET, Ben Cooksley wrote:
> > Note that in the long run with DMARC looming you will need to switch
> > to #2 anyway, and keeping your current behaviour will likely lead to
> > mail from people who us
On Tuesday, December 8, 2015 8:21:03 PM CET Ben Cooksley wrote:
> On Tue, Dec 8, 2015 at 2:19 AM, Martin Graesslin wrote:
> > On Friday, December 4, 2015 11:28:03 AM CET Jan Kundrát wrote:
> >> On Friday, 4 December 2015 10:56:42 CET, Ben Cooksley wrote:
> >> >
On Tuesday, December 8, 2015 9:51:50 AM CET Martin Graesslin wrote:
> On Tuesday, December 8, 2015 8:21:03 PM CET Ben Cooksley wrote:
> > On Tue, Dec 8, 2015 at 2:19 AM, Martin Graesslin
wrote:
> > > On Friday, December 4, 2015 11:28:03 AM CET Jan Kundrát wrote:
> > >&
On Tuesday, December 8, 2015 10:54:13 PM CET Ben Cooksley wrote:
> On Tue, Dec 8, 2015 at 10:33 PM, Martin Graesslin
wrote:
> > On Tuesday, December 8, 2015 9:51:50 AM CET Martin Graesslin wrote:
> >> On Tuesday, December 8, 2015 8:21:03 PM CET Ben Cooksley wrote:
> >>
On Wednesday, December 9, 2015 2:09:01 AM CET Valorie Zimmerman wrote:
> We *can* do this, we need to do this, and Ben doesn't have time to do
> all the work himself. So we need to do our part to help.
That's what I suggested in one of my mails. We need to tackle this as a
coordinated project whe
On Friday, February 26, 2016 10:37:10 PM CET Ben Cooksley wrote:
> Hi all,
>
> I've been hammering away at some of the builds on our Jenkins Sandbox,
> and have found it isn't possible to get polkit-qt-1 to build.
>
> This blocks the entire KDE 4 chain, among other things.
>
> Could someone plea
On Tuesday, March 1, 2016 7:37:55 PM CET Mark Gaiser wrote:
> Op 29 feb. 2016 11:10 p.m. schreef "Thiago Macieira" :
> > On segunda-feira, 29 de fevereiro de 2016 21:42:11 PST Sven Brauch wrote:
> > > Hey,
> > >
> > > On 02/28/2016 03:58 PM, Luigi Toscano wrote:
> > > > This is what I use:
> > > >
On Monday, February 29, 2016 9:42:11 PM CET Sven Brauch wrote:
> Hey,
>
> On 02/28/2016 03:58 PM, Luigi Toscano wrote:
> > This is what I use:
> > export QT_QPA_PLATFORMTHEME=kde
> >
> > and you need the integration plugin installed. It used to be part of
> > Frameworks (frameworksintegration),
On Wednesday, March 2, 2016 11:08:30 AM CET Mark Gaiser wrote:
> On Wed, Mar 2, 2016 at 9:42 AM, Martin Graesslin wrote:
> > On Monday, February 29, 2016 9:42:11 PM CET Sven Brauch wrote:
> > > Hey,
> > >
> > > On 02/28/2016 03:58 PM, Luigi Tosca
On Wednesday, March 2, 2016 11:46:01 AM CET Sven Brauch wrote:
> Hey,
>
> On 03/02/2016 11:19 AM, Martin Graesslin wrote:
> > No, because everything in the current plugin is Plasma specific.
>
> Meh. In some kind of theoretical view you are right, I do see that.
> Pragma
On Wednesday, March 2, 2016 12:09:17 PM CET Sven Brauch wrote:
> On 03/02/2016 11:56 AM, Thomas Lübking wrote:
> > Imo that's a more issue: IPC is I/O, ie. unreliable. You cannot provide
> > functionality that relies on working IPC, but hard-relying on it is bad
> > design (nb. that the failing kde
On Sunday, March 6, 2016 1:48:13 AM CET Kevin Kofler wrote:
> Martin Graesslin wrote:
> > No, because everything in the current plugin is Plasma specific. If we
> > want to change the font, we will do so!
>
> Forcing a default font as you have done is a bad idea even on Pl
e and also hand-picked patches for QtWayland.
Thank you for helping our great Wayland endeavour.
If you have any questions please do not hesitate to ask!
Cheers
Martin Graesslin
signature.asc
Description: This is a digitally signed message part.
On Tuesday, October 11, 2016 10:23:06 PM CEST Luca Beltrame wrote:
> Il giorno Tue, 11 Oct 2016 14:14:45 +0200
>
> Martin Graesslin ha scritto:
> > Such isos have the latest code and also hand-picked patches for
> > QtWayland.
>
> Can we have a list of these
On Wednesday, October 12, 2016 2:05:25 PM CEST Kevin Kofler wrote:
> Hi,
>
> one major issue is that QtWebEngine does not work on Wayland at this time,
> at least not if it is built with desktop OpenGL. See:
> https://bugreports.qt.io/browse/QTBUG-55384
>
> This affects kdepim applications (at le
On Tuesday, October 11, 2016 2:14:45 PM CEST Martin Graesslin wrote:
> Hello KDE application developers,
>
> with Plasma 5.8 we have reached a quite solid state in the Wayland porting
> efforts. A state where you can start to test whether your application works
> correctly on Wa
On Saturday 02 November 2013 12:53:14 Boudewijn Rempt wrote:
> Okay... Couple of questions:
>
> * screenshot: which theme/color scheme should be used (btw, for Krita, on
> Gnome3, Plastique is hard-coded, because other themes are broken.)
You want to sell your app to the user: use what makes it lo
On Wednesday 11 December 2013 19:59:51 Albert Astals Cid wrote:
> Hi guys, seems that 4.12 is hit by a pretty bad regression in
> KItemWidgetDelegate (patches that don't seem to have been reviewed, but I
> won't fight that now)
>
> More info at https://bugs.kde.org/show_bug.cgi?id=328528
>
> It s
On Friday 27 December 2013 18:31:19 Ivan Čukić wrote:
> It just *needs* to be smooth and stable. It would be awful if the first
> impression of baloo was the same as with the first releases of plasma and
> nepomuk.
Maybe the Nepomuk/Baloo developers could think about a fallback plan in case
proble
On Tuesday 31 December 2013 12:15:09 David Faure wrote:
> > QSystemTrayIcon => KNotificationItem
>
> No clue. I can't even find KNotificationItem in KF5 anywhere !?!?
> In fact it doesn't exist in kdelibs4 either.
>
> I think it got replaced with KStatusNotifierItem since 4.4 ?
> That one is
On Monday 06 January 2014 07:52:50 Kevin Ottens wrote:
> The current list of modules is there:
> http://community.kde.org/Frameworks/List
>
> As you can see there's quite some holes in the table, and quite a few
> entries marked unmaintained. KDE Frameworks as a set of technologies will
> only be
On Thursday 20 February 2014 18:54:32 Matthias Klumpp wrote:
> Hi!
> I am working on bringing AppData to KDE. AppData is a XML-based
> metadata format to enhance information displayed about applications in
> software-centers. It, for example, includes long descriptions of an
> application, homepage
On Wednesday 07 May 2014 19:42:21 Albert Astals Cid wrote:
> El Dimecres, 7 de maig de 2014, a les 10:11:37, Martin Gräßlin va escriure:
> > Hi all,
> >
> > I need some advice. The new GTK+ release
>
> For those that don't follow much the GTK+ world, which release number is
> that?
3.12.1 - mino
On Wednesday 03 September 2014 14:36:48 Paulo Lieuthier wrote:
> Hello everyone,
>
> I'm a LXQt contributor and I've been working on getting it rid of Xlib calls
> by using KF5's WindowSystem. It looks nice so far.
>
> The problem I'm having now is that I can't get the taskbar to indicate a
> win
On Sunday 18 March 2012 20:01:01 Casian Andrei wrote:
> Hello,
taking it to the KWin mailinglist as that's the relevant list in case this
proposal would be accepted.
First of all thanks for considering doing a GSoC project around KWin.
> I need your guidance in order to create a decent proposal.
On Monday 24 December 2012 17:12:22 Weng Xuetian wrote:
> I think some action need to be taken before the release, some possible
> solutions.
> 1. Revert the changes of new plasma air theme, so old shadow can be used.
> and try to fix all the things in KDE 4.11
Personal opinion: the change should b
On Wednesday 06 February 2013 22:41:25 Myriam Schweingruber wrote:
> Hi all,
>
> On Wed, Feb 6, 2013 at 10:20 PM, Frank Reininghaus
>
> wrote:
> > Am 06.02.2013 18:57 schrieb "Kevin Krammer":
> >> Hi folks,
> >>
> >> at FOSDEM I was approached by a person who asked me to relay his
> >> dissatis
On Sunday 10 February 2013 16:40:06 Jekyll Wu wrote:
> On 2013年02月07日 18:29, Martin Gräßlin wrote:
> > Also spend a moment and look at the report. There is multiple times
> > written
> > that we don't want any further comments on the bug and that doesn't help
> > anything. Still attachements, still
On Saturday 02 March 2013 00:37:25 Ivan Čukić wrote:
> > gcc -std=c++11 -fPIE -E -dM -I$QTDIR/include -include QtCore/qglobal.h
> > -xc++ /dev/null | grep Q_COMPILER
> >
> > That will give you the full listing of detected features, matching exactly
> > what will be available at compile-time.
>
>
On Saturday 04 May 2013 22:34:04 Kevin Kofler wrote:
> On Friday 03 May 2013 at 17:04:44, Matthias Klumpp wrote:
> > @Kevin: I am only remotely following this issue, but as PackageKit
> > developer, I would of course like to see our project in Plasma
> > Workspaces as soon as possible. But I don't
On Monday 08 July 2013 20:06:51 Albert Astals Cid wrote:
> El Dilluns, 8 de juliol de 2013, a les 14:03:19, Scott Kitterman va
escriure:
> > Albert Astals Cid wrote:
> > >El Dilluns, 8 de juliol de 2013, a les 11:25:42, Scott Kitterman va
> > >
> > >escriure:
> > >> On Monday, July 08, 2013 04:59
On Tuesday 09 July 2013 18:57:41 Albert Astals Cid wrote:
> So the kde-workspace dudes decided they don't want a 4.12 release and that
> they'll do a LTS 4.11, fine, how do we fix that branch wise?
I don't see how that affects branching.
* 4.11 is branched from master
* master is opened for feature
On Wednesday 10 July 2013 01:25:06 Andras Mantia wrote:
> On Tuesday, July 09, 2013 11:45:39 PM Martin Graesslin wrote:
> > * master is opened for feature development and will lead to Plasma
> > Workspaces 2 (or whatever the release will be called in the end).
>
> Do
On Wednesday 10 July 2013 17:13:11 Sune Vuorela wrote:
> On 2013-07-10, Aaron J. Seigo wrote:
> >=3D=3D On scheduling mainenance releases
> >
> > in a longer 4 month cycle, i=E2=80=99d cut that to 8 weeks and keep jus=
> > t the one=20
> > update.
> >
> > this would ease the burdon on our releas
On Monday 15 July 2013 14:42:14 Sebastian Kügler wrote:
> Hey,
>
> On Tuesday, July 09, 2013 18:57:41 Albert Astals Cid wrote:
> > So the kde-workspace dudes decided they don't want a 4.12 release and that
> > they'll do a LTS 4.11, fine, how do we fix that branch wise?
>
> After carefully readin
On Thursday 18 July 2013 10:26:06 Sebastian Kügler wrote:
> - master stays on 4.11, receives bugfixes, our releases are based on this
> branch and their version number will stay 4.11
how do we prevent that people commit features into master? I would prefer if
we lock down master in gitolite so t
On Friday 19 July 2013 01:39:47 Michael Jansen wrote:
> On Friday, July 19, 2013 12:21:21 AM David Faure wrote:
> > After more live discussion with Sebas and Marco plus Aaron over a video
> > chat, we came up with the following setup for the workspace repos (*) :
> >
> > - the development branch f
48 matches
Mail list logo
