Re: Policy regarding QtWebKit and QtScript

2015-12-29 Thread Lisandro Damián Nicanor Pérez Meyer
On Friday 25 December 2015 13:43:22 Nicolás Alvarez wrote:
[snip]
> The linking step needs 4GB of RAM

At least on the qtwebkit case that's the amount of RAM without generating 
debugging symbols (or maybe using stabs).

I also know that Allan has worked toward deembedding stuff from QtWebEngine. 
Sadly my available time and build power has proven to not be enough to 
properly test this fact :(

-- 
Programming today is a race between software engineers striving to build
bigger and better idiot-proof programs, and the Universe trying to produce
bigger and better idiots. So far, the Universe is winning.
  Anonymous

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.


Re: Policy regarding QtWebKit and QtScript

2015-12-29 Thread Adriaan de Groot
On Wednesday 30 December 2015 01:34:46 Vadim Zhukov wrote:
> There is a little chance QtWebEngine will be ported on OpenBSD: if
> someone will come in and fix Chromium and QtWebEngine to bundle less,
> at least. I won't volunteer: handling a few hundreds of KDE ports +
> ports of Qt itself is already big enough task for me.
> 
> So, again, it was my seeing, both for today and tomorrow. Now I'm back
> to porting other KDE5 stuff. Thank you for reading!

Thank you, Vadim. I spent an hour or two on qtwebengine today. I got the 
feeling that the motto is "y0 dawg, i hear you like build systems so i put a 
buildsystyem in your buildsystem so you can buildsystem while you 
buildsystem". It is a frustrating experience.

I'm trying hard to not make this sound like whining, really.

 - Why am I building ninja when it's already packaged externally?
 - Why am I building yasm?
 - Same applies to most of the bundled stuff. A lot of the FreeBSD patches for 
Chromium itself are, indeed, unbundlings. But those need to be re-done for 
webengine, because who knows how the versions differ.
 - The qmake and gyp (horse pucky!) are strongly tied into linux/mac/boot2qt, 
so finding all the bits and pieces that need adjusting is tricky.
 - Example, I thought I had bunged freebsd-clang into the system properly, but 
gyp is still trying to discover the assembler version by calling gcc.
 - Example from qt3d (so external to this discussion), using a broken OffsetOf 
in a bundled third party library.

This sounds like a case where the unbundling OSsen -- OpenBSD, FreeBSD, 
probably some of the Linuxen -- can and should get together to help make more 
of Qt 5.6 a truly cross-platform development environment. (Randa?)

[ade]


Re: Policy regarding QtWebKit and QtScript

2015-12-29 Thread Allan Sandfeld Jensen
On Tuesday 29 December 2015, Adriaan de Groot wrote:
> On Wednesday 30 December 2015 01:34:46 Vadim Zhukov wrote:
> > There is a little chance QtWebEngine will be ported on OpenBSD: if
> > someone will come in and fix Chromium and QtWebEngine to bundle less,
> > at least. I won't volunteer: handling a few hundreds of KDE ports +
> > ports of Qt itself is already big enough task for me.
> > 
> > So, again, it was my seeing, both for today and tomorrow. Now I'm back
> > to porting other KDE5 stuff. Thank you for reading!
> 
> Thank you, Vadim. I spent an hour or two on qtwebengine today. I got the
> feeling that the motto is "y0 dawg, i hear you like build systems so i put
> a buildsystyem in your buildsystem so you can buildsystem while you
> buildsystem". It is a frustrating experience.
> 
> I'm trying hard to not make this sound like whining, really.
> 
>  - Why am I building ninja when it's already packaged externally?
a) That is a how Chromium does it and b) it is really convenient on platforms 
that doesn't have package managers that can easily download a prebuild version 
of ninja (most platforms). Adding that Chromium tend to depend on specific 
versions, it not affecting the shipped result, and is relatively fast to 
build, it is probably not worth the trouble.

>  - Why am I building yasm?
>  - Same applies to most of the bundled stuff. A lot of the FreeBSD patches
> for Chromium itself are, indeed, unbundlings. But those need to be re-done
> for webengine, because who knows how the versions differ.
We have already done third-party library unbundling in Qt 5.6.

>  - The qmake and gyp (horse pucky!) are strongly tied into
> linux/mac/boot2qt, so finding all the bits and pieces that need adjusting
> is tricky.
The linux parts probably just need to be split into general posix/unix parts 
and linux parts, but yes it has to happen several places.

Best regards
`Allan


Re: Review Request 125910: Fix for Bug 334525 - Gwenview hangs when switching from normal to full screen mode

2015-12-29 Thread Johannes Stefan

---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125910/
---

(Updated Dec. 29, 2015, 8:54 p.m.)


Status
--

This change has been marked as submitted.


Review request for kdelibs and Martin Klapetek.


Changes
---

Submitted with commit 3f080d44af41d0158d7b5c51269449e78d5b128f by Martin 
Klapetek on behalf of Johannes Stefan to branch master.


Bugs: 334525
http://bugs.kde.org/show_bug.cgi?id=334525


Repository: kdelibs


Description
---

Setting default reason for going into fullscreen mode


Diffs
-

  kdeui/notifications/knotificationrestrictions.cpp 818edea 

Diff: https://git.reviewboard.kde.org/r/125910/diff/


Testing
---

Compiled an tested - DBus Log as expected:

# begin DBUS-log #
method call sender=:1.223 -> dest=org.freedesktop.ScreenSaver serial=56 
path=/ScreenSaver; interface=org.freedesktop.ScreenSaver; member=Inhibit
   string "Gwenview"
   string "no_reason_specified"
method call sender=:1.6 -> dest=:1.3 serial=588 path=/org/gnome/SessionManager; 
interface=org.gnome.SessionManager; member=Inhibit
   string "Gwenview"
   uint32 0
   string "no_reason_specified"
   uint32 8
signal sender=:1.3 -> dest=(null destination) serial=351 
path=/org/gnome/SessionManager; interface=org.freedesktop.DBus.Properties; 
member=PropertiesChanged
   string "org.gnome.SessionManager"
   array [
  dict entry(
 string "InhibitedActions"
 variant uint32 8
  )
   ]
   array [
   ]
signal sender=:1.3 -> dest=(null destination) serial=352 
path=/org/gnome/SessionManager; interface=org.gnome.SessionManager; 
member=InhibitorAdded
   object path "/org/gnome/SessionManager/Inhibitor29"
method return sender=:1.3 -> dest=:1.6 reply_serial=588
   uint32 1169992534
method call sender=:1.4 -> dest=:1.21 serial=56 
path=/org/gnome/Mutter/IdleMonitor/Core; 
interface=org.gnome.Mutter.IdleMonitor; member=RemoveWatch
   uint32 35
method call sender=:1.6 -> dest=org.freedesktop.DBus serial=589 
path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
   string 
"type='signal',sender='org.freedesktop.DBus',interface='org.freedesktop.DBus',member='NameOwnerChanged',path='/org/freedesktop/DBus',arg0=':1.223'"
method call sender=:1.6 -> dest=org.freedesktop.DBus serial=590 
path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=GetNameOwner
   string ":1.223"
method return sender=:1.6 -> dest=:1.223 reply_serial=56
   uint32 1169992534
method call sender=:1.6 -> dest=:1.21 serial=592 
path=/org/gnome/Mutter/DisplayConfig; 
interface=org.freedesktop.DBus.Properties; member=Set
   string "org.gnome.Mutter.DisplayConfig"
   string "PowerSaveMode"
   variant   int32 0
method call sender=:1.21 -> dest=:1.3 serial=1073 
path=/org/gnome/SessionManager; interface=org.gnome.SessionManager; 
member=IsInhibited
   uint32 16
method call sender=:1.21 -> dest=org.freedesktop.DBus serial=1074 
path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=RemoveMatch
   string 
"type='signal',sender='org.freedesktop.DBus',interface='org.freedesktop.DBus',member='NameOwnerChanged',path='/org/freedesktop/DBus',arg0=':1.4'"
method return sender=:1.21 -> dest=:1.4 reply_serial=56
method return sender=:1.3 -> dest=:1.21 reply_serial=1073
   boolean false
# end of DBUS-log #


Thanks,

Johannes Stefan



Jenkins-kde-ci: kdelibs KDE-4.14 stable-qt4 » Linux,gcc - Build # 47 - Still Unstable!

2015-12-29 Thread no-reply

GENERAL INFO

BUILD UNSTABLE
Build URL: 
https://build.kde.org/job/kdelibs%20KDE-4.14%20stable-qt4/PLATFORM=Linux,compiler=gcc/47/
Project: PLATFORM=Linux,compiler=gcc
Date of build: Tue, 29 Dec 2015 08:29:36 +
Build duration: 11 min

CHANGE SET
Revision a5b86628debea250f6bde70156ca44482d30231c by Pino Toscano: (Fix typo in 
apidox of KWidgetItemDelegate)
  change: edit kdeui/itemviews/kwidgetitemdelegate.h


JUNIT RESULTS

Name: (root) Failed: 1 test(s), Passed: 163 test(s), Skipped: 0 test(s), Total: 
164 test(s)Failed: TestSuite.kdecore-kmimetype_nomimetypes

COBERTURA RESULTS

Cobertura Coverage Report
  

By packages
  

Jenkins-kde-ci: kdelibs KDE-4.14 latest-qt4 » Linux,gcc - Build # 50 - Still Unstable!

2015-12-29 Thread no-reply

GENERAL INFO

BUILD UNSTABLE
Build URL: 
https://build.kde.org/job/kdelibs%20KDE-4.14%20latest-qt4/PLATFORM=Linux,compiler=gcc/50/
Project: PLATFORM=Linux,compiler=gcc
Date of build: Tue, 29 Dec 2015 08:29:36 +
Build duration: 11 min

CHANGE SET
Revision a5b86628debea250f6bde70156ca44482d30231c by Pino Toscano: (Fix typo in 
apidox of KWidgetItemDelegate)
  change: edit kdeui/itemviews/kwidgetitemdelegate.h


JUNIT RESULTS

Name: (root) Failed: 1 test(s), Passed: 163 test(s), Skipped: 0 test(s), Total: 
164 test(s)Failed: TestSuite.kdecore-kmimetype_nomimetypes

COBERTURA RESULTS

Cobertura Coverage Report
  

By packages