Re: [Development] [meta-qt5] Qt5.8 qdbuscpp2xml broken for kde baloo?

14.02.2017, 00:48, "Andreas Müller via Development" : > On Mon, Feb 13, 2017 at 5:22 PM, Thiago Macieira > wrote: >>  Em segunda-feira, 13 de fevereiro de 2017, às 09:29:55 PST, Andreas Müller >> via >>  Development escreveu: >>>  On Sat,

Re: [Development] Gerrit issue

13.02.2017, 15:26, "Balázs Meskó" : > Hi! > > Sorry for sending this mail to this list, but the localization list seems > quite dead, and the actual problem *is* a development issue. > > I am trying to push the Hungarian localization for Qt 5.6. I am running git

Re: [Development] Feature Freeze Exception: QStringView

07.02.2017, 20:03, "Vincas Dargis" : > 2017.02.06 18:38, Thiago Macieira rašė: >>  Yes, but it's very hard to measure. I do agree in shrinking our code however >>  much we can (which is why I'd like to suppress the unwind tables >> completely). > > Sorry for off-topic, but I

[Development] [Announcement] QtWebKit Technology Preview 5

Hi all, QtWebKit Technology Preview 5 is out. Highlights of these release are: * WebGL, accelerated compositing and accelerated 2D canvas are supported now. Accelerated compositing is disabled by default for now, it is known to cause minor artifacts on some sites. * MinGW compiler is now

Re: [Development] HEADS-UP: 5.6 / LTS is now open for business

04.02.2017, 01:23, "Oswald Buddenhagen" : > moin, > > we finally managed to add a cherry-pick validator to the sanity bot, so > i dared to open the 5.6 branch for staging again. > > caveat: patchsets created before the final forward merge got a positive > review while

Re: [Development] Request moving project to playground area

03.02.2017, 01:07, "Milian Wolff" : > On Donnerstag, 2. Februar 2017 20:38:00 CET Hamed Masafi wrote: >>  Project Name: Nut (currently renamed to ORM) >> >>  Description: ORM is a project aimed to help users working with databases. >>  Developer will write his/her own

Re: [Development] GPL tooling in Qt module?

01.02.2017, 20:01, "Sean Harmer" : > Hi, > > as part of the current animation support in Qt3D we've written an addon for > blender that is able to export all the animation clips in a blender file to a > format that Qt 3D can use (json based). > > As such addons need to run

Re: [Development] Shall we turn on /utf-8 compiler option when build qt for Windows?

30.01.2017, 14:24, "Simon, Hausmann" : > Making a warning go away for compilers that we know support utf-8 may not > come at the price of your life :) > > I for one am all in favor of requiring just the Qt source code (not talking > about customer code) to be encoded in a

Re: [Development] Shall we turn on /utf-8 compiler option when build qt for Windows?

30.01.2017, 14:37, "Viktor Engelmann" : > Am 30.01.2017 um 12:23 schrieb Simon, Hausmann: >> Making a warning go away for compilers that we know support utf-8 may not >> come at the price of your life :) >> >> I for one am all in favor of requiring just the Qt source

Re: [Development] Policy for examples with large resources?

27.01.2017, 19:41, "Oswald Buddenhagen" : > On Fri, Jan 27, 2017 at 03:48:54PM +, Sean Harmer wrote: >>  Is there a way we can get a git-lfs repo set up as a submodule to be >>  referenced by the qt3d repo? > > sure. you just need to prototype a solution which i can

Re: [Development] Windows: Trying to join to a multicast group as a receiver with specific interface always uses default interface

27.01.2017, 12:11, "Konrad Rosenbaum" : > Hi Thiago, > > On Fri, January 27, 2017 04:49, Thiago Macieira wrote: >>  If it is IPv4, the priority for your issue has just dropped to the floor. >>  I >>  won't debug IPv4 multicast on Windows, on principle. > >>  I will review IPv4

Re: [Development] Qt5 k1om x100 Xeon PHI Cross Compilation

26.01.2017, 22:00, "ƦOB COASTN" : > Greetings, > > The cross-compilation of Qt5 and additional modules adds support for headless > Qt5 applications to run as native k1om co-processor applications. > > Files that required modification include 'configure' and >

Re: [Development] Texture image loading library

20.01.2017, 00:22, "Oswald Buddenhagen" : > On Thu, Jan 19, 2017 at 07:34:08PM +0100, Giuseppe D'Angelo wrote: >>  Nonetheless, since such loaders would be useful in more than one place >>  (qtbase, qtdeclarative, qt3d) I think that the best place for them would >>  be

Re: [Development] invokeMethod() with function pointers

16.01.2017, 12:34, "Olivier Goffart" : > On Samstag, 14. Januar 2017 17:28:01 CET Benjamin TERRIER wrote: >>  Hi everyone, >> >>  I'm trying to contribute by making QMetaObject::invokeMethod() take function >>  pointers instead of function names. >> >>  I've come up with

Re: [Development] invokeMethod() with function pointers

14.01.2017, 20:42, "Thiago Macieira" : > On sábado, 14 de janeiro de 2017 17:28:01 PST Benjamin TERRIER wrote: >>  I've uploaded my change as a draft on gerrit: >>  https://codereview.qt-project.org/#/c/182339/ > > No one can see it while it's a draft. You have to

Re: [Development] Reusing Qt code (or: saving .ico files)

13.01.2017, 13:29, "René J.V. Bertin" : > Hello, > > Can someone please have a look at the KDE RR below and tell us whether or not > it's OK to include qicohandler.* the way I propose in the patch under review? > There are some whitespace changes and I added a preprocessor

Re: [Development] Proposal for "container-oriented deterministic memory manager"

Oh, looks like you are going to learn about lots of other wonderful memory allocators soon. There is no real need to keep us informed about each of them (I guess most of interested folks are already well-aware of them), but please make sure you've studied prior art thoroughly before designing

Re: [Development] Proposal for "container-oriented deterministic memory manager"

05.01.2017, 23:06, "André Pönitz" : > On Thu, Jan 05, 2017 at 07:57:54AM -0600, Thiago Macieira wrote: >>  Em quinta-feira, 5 de janeiro de 2017, às 07:26:52 CST, Phil Bouchard >>  escreveu: >>  > > AFAIU QtQuickCompiler has nothing to do with memory management, its main >>

Re: [Development] Proposal for "container-oriented deterministic memory manager"

06.01.2017, 02:06, "Phil Bouchard" : > On 01/05/2017 03:09 PM, André Pönitz wrote: >>  On Thu, Jan 05, 2017 at 07:57:54AM -0600, Thiago Macieira wrote: >>>  Em quinta-feira, 5 de janeiro de 2017, às 07:26:52 CST, Phil Bouchard >>>  escreveu: >  AFAIU QtQuickCompiler has

Re: [Development] Proposal for "container-oriented deterministic memory manager"

05.01.2017, 03:46, "Phil Bouchard" : > On 01/02/2017 04:50 PM, Phil Bouchard wrote: >>  On 12/29/2016 04:14 AM, Simon Hausmann wrote: >>>  Hi, >> >>  Sorry for the delay... >> >>  First I would like to point out this popular Javascript test runs 1.5 >>  faster using Qt over

Re: [Development] Nominating Konstantin Tokarev for Approver status

der.blasche=qt...@qt-project.org> on behalf of > Allan Sandfeld Jensen <k...@carewolf.com> > Sent: Monday, 5 December 2016 1:23:45 PM > To: development@qt-project.org > Subject: [Development] Nominating Konstantin Tokarev for Approver status > > Hi all, > >

Re: [Development] Proposal for "container-oriented deterministic memory manager"

27.12.2016, 05:51, "Phil Bouchard" : > On 12/26/2016 07:37 PM, Thiago Macieira wrote: >>  Em segunda-feira, 26 de dezembro de 2016, às 18:04:45 BRST, Phil Bouchard >>  escreveu: >>>  No I didn't write any paper on the subject yet (I already have n side >>>  projects to

Re: [Development] Proposal for "container-oriented deterministic memory manager"

26.12.2016, 07:02, "Phil Bouchard" <philipp...@gmail.com>: > On 12/25/2016 04:05 PM, Thiago Macieira wrote: >>  Em domingo, 25 de dezembro de 2016, às 22:15:48 BRST, Konstantin Tokarev >>  escreveu: >>>>  I know the GC randomly kicks in so it fits t

Re: [Development] Proposal for "container-oriented deterministic memory manager"

25.12.2016, 22:35, "Phil Bouchard" <philipp...@gmail.com>: > On 12/25/2016 02:15 PM, Konstantin Tokarev wrote: >>  25.12.2016, 08:50, "Phil Bouchard" <philipp...@gmail.com>: >>>  On 12/25/2016 12:25 AM, Konstantin Tokarev wrote: >>>>

Re: [Development] Proposal for "container-oriented deterministic memory manager"

25.12.2016, 08:50, "Phil Bouchard" <philipp...@gmail.com>: > On 12/25/2016 12:25 AM, Konstantin Tokarev wrote: >>>  Greetings, >>> >>>  I am a QML developer and it came to my attention that the animation is >>>  sluggish because of the in

Re: [Development] Proposal for "container-oriented deterministic memory manager"

> Greetings, > > I am a QML developer and it came to my attention that the animation is > sluggish because of the internal garbage collector. Do you have any proofs that GC is to blame here? > I know about the > QtQuickCompiler that could speed up the rendering but it still uses a > garbage

Re: [Development] qtwebkit

16.12.2016, 13:25, "Harald Vistnes" : > Silly me, I forgot to run qmake, just tried to run nmake/jom. It's > compiling now, hopefully without problems. > > Thanks for your help! I you are using widgets API, consider trying QtWebKit TP4 from [1]. There are

Re: [Development] A new approach for Qt main()

12.12.2016, 13:08, "Benjamin TERRIER" : > 2016-12-12 10:56 GMT+01:00 Mark De Wit : >>  I have an application based on qt-solutions qtwinmigrate sample. >> >>  Because we're integrating Qt into an existing MFC application, we're not >> even running

Re: [Development] A new approach for Qt main()

09.12.2016, 20:11, "Thiago Macieira" : >  Em sexta-feira, 9 de dezembro de 2016, às 11:10:15 PST, Matthew Woehlke >  escreveu: >>   Also, how does this work if someone wants to subclass Q*Application? >>   (Again, I have projects that do that...) > >  But why do they

Re: [Development] Proposal: Use -qt-zlib configuration in official MinGW builds

29.11.2016, 13:19, "Kai Koehne" <kai.koe...@qt.io>: >>  -Original Message- >>  From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- >>  project.org] On Behalf Of Konstantin Tokarev >>  Sent: Monday, November 28, 2016 3:11 PM >&g

Re: [Development] Proposal: Use -qt-zlib configuration in official MinGW builds

29.11.2016, 13:02, "Konrad Rosenbaum" <kon...@silmor.de>: > Hi, > > On Monday 28 November 2016 17:11:19 Konstantin Tokarev wrote: >>  Currently, MinGW builds in Coin use -system-zlib configuration. It happens >>  because MinGW is shipped with zlib head

Re: [Development] Qt 5.9

29.11.2016, 10:43, "Jake Petroules" : > I don't know what sort of cross build and deployment environment you've set > up, but I've worked with Qt Creator developing on actual embedded Linux > hardware and the code-deploy-test cycle is lightning fast; no slower than >

[Development] Proposal: Use -qt-zlib configuration in official MinGW builds

Hello, Currently, MinGW builds in Coin use -system-zlib configuration. It happens because MinGW is shipped with zlib headers and libz.a. However, linking zlib to several Qt modules (at least, QtCore, QtGui, QtNetwork, and QtSvg) is suboptimal, while with -system-zlib one copy in QtCore is shared

Re: [Development] build [any] qt-based project ising cmake , outside of qtcreator

25.11.2016, 22:12, "Ernst Maurer" : > hello > > just faced with a requirement to build qt/cmake based project from command > line or another IDE, and could not. what is a qtcreator magic which helps to > do this successfully? > > tried to build simplest sample project

Re: [Development] Summary ABI compabilty

25.11.2016, 03:38, "Kevin Kofler" : > Lars Knoll wrote: >>  There are a lot of good arguments towards using the STL and libstdc++ >>  more, as it will allow us to interoperate better with the C++ standard, >>  and provides a couple of things that we really want to use. So

Re: [Development] Qt 5.9

23.11.2016, 13:26, "Massimo Callegari via Development" : > Hi, > is there any chance Qt 5.9 can support MSYS2 out of the box ? > > For us Linux users, MSYS2 feels like home, and it's the most convenient > environment to work with external dependencies simply by

Re: [Development] Qt 5.9

23.11.2016, 05:32, "Thiago Macieira" : > On quarta-feira, 23 de novembro de 2016 02:06:14 PST Jake Petroules wrote: >>  > If we still have time, I'd like to see MinGW 64-bit for 5.8, so we can >>  > drop >>  > the 32-bit binary build in time for 5.9. >>  > >>  >

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

21.11.2016, 15:26, "Giuseppe D'Angelo" : > On Mon, Nov 21, 2016 at 12:58 PM, Oswald Buddenhagen > wrote: >>>  Any idea to how to actually make this work? >>  how about taking the existing processes seriously and exercising social >>  pressure on

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

19.11.2016, 09:46, "Marc Mutz" <marc.m...@kdab.com>: > On Saturday 19 November 2016 02:17:27 Konstantin Tokarev wrote: >>  > If we do nothing else, we should at least use owner whereever >>  > possible. >> >>  Wouldn't it be a better

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

17.11.2016, 13:33, "Marc Mutz" : > On Thursday 17 November 2016 10:46:24 Edward Welbourne wrote: >>  On quarta-feira, 16 de novembro de 2016 17:11:02 PST Marco Bubke wrote: >>  >> Like you maybe have learned there are C++ Core Guidelines. They are >>  >> already very

Re: [Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

18.11.2016, 01:03, "Thiago Macieira" : > On quinta-feira, 17 de novembro de 2016 11:35:54 PST Marc Mutz wrote: >>  The bigger problem is that while owner does not affect the ABI, all other >>  GSL types do, and we're back to our §$%&!§ rule that we can't accept other

Re: [Development] QtQuickControls for desktop: what's the plan?

10.11.2016, 17:08, "Marco Martin" : > On Thursday 10 November 2016 11:11:35 Olivier Goffart wrote: >>  Writing and polishing styles to pixel perfection is indeed lot of work. And >>  QStyle has the advantage hat it already exists. However one can copy-paste >>  the code to

Re: [Development] Neat feature in gerrit: drafts

10.11.2016, 19:18, "Edward Welbourne" : > A review puzzled several of us today by (apparently) starting at patch > set 6. Jesus had discovered a gerrit feature we hadn't heard of: > drafts. FYI, it was around for ages, since 2.3 release > If you push to refs/drafts/blah

Re: [Development] Branch for adding Q_DECL_OVERRIDEs

27.10.2016, 19:44, "Rolland Dudemaine" : > Using the GHS compiler, i see thousands of examples of this. > To the point that (bad practice warning!) I disabled the warning. Better take clang-tidy and fix up things automatically > > --Rolland >

Re: [Development] Build Qt on Solaris 10 Fail

19.10.2016, 18:30, "Fabio Santos via Development" : > Hi Thiago, > > Thanks for your help... now I'm using solaris-g++-64 > > (./configure -platform solaris-g++-64) configure command works fine, but > gmake  had problems see: > > g++ -m64

Re: [Development] Build Qt on Solaris 10 Fail

18.10.2016, 21:47, "Fabio Santos via Development" : > Hi all, > > I'm new here and trying to compile Qt on solaris sparc 10, But I receive a > error during gmake command, see: I think CC is not supported, it's a very peculiar C++ compiler and it does not have C++11

Re: [Development] Backporting the "stop unloading plugins" change to 5.6

17.10.2016, 15:48, "Thiago Macieira" : > Em segunda-feira, 17 de outubro de 2016, às 13:32:04 PDT, Giuseppe D'Angelo > escreveu: >>  Il 14/10/2016 19:44, Thiago Macieira ha scritto: >>  >> > We are talking in this change about QFactoryLoader, which is a Qt API >>  >> >

Re: [Development] Backporting the "stop unloading plugins" change to 5.6

13.10.2016, 20:39, "André Pönitz" <apoen...@t-online.de>: > On Thu, Oct 13, 2016 at 08:01:57PM +0300, Konstantin Tokarev wrote: >>  > I still consider the approach of not unloading plugins fundamentally >>  > wrong. It only deepens the trench between Qt a

Re: [Development] Backporting the "stop unloading plugins" change to 5.6

13.10.2016, 19:39, "André Pönitz" : > On Thu, Oct 13, 2016 at 03:30:22PM +0100, Sergio Martins wrote: >>  On 2016-10-12 20:59, Thiago Macieira wrote: >>  >Hello >>  > >>  >We've got a number of issues that got fixed in 5.7 by the change that made >>  >QFactoryLoader stop

Re: [Development] Notes on "Managing Qt's branches" session @ QCS 2016

04.10.2016, 14:04, "Edward Welbourne" : > Marc Mutz said: >>  I just came to realise another reason against cherry-picking: >> >>  Qt 5.6 is C++98-only while 5.7+ is C++11. That means patches that will >>  be developed against 5.7+ will very likely have C++11 constructs

Re: [Development] Using semicolons in JS (QML)

30.09.2016, 15:19, "Kai Koehne" : > Hi, > > It’s Friday, so time for some bikeshedding ;) > > As you might know, the semicolon as a statement separator in JavaScript is > optional. That is, most of the time you can just separate commands > > by newlines. There are a few

Re: [Development] QDataStream: blackbox or document all versions?

26.09.2016, 13:29, "Shawn Rutledge" : > On Sep 26, 2016, at 11:34, Simon Hausmann wrote: > >> Hi, >> >> I'm very much in favor of using a proper schema based system such as >> protocol buffers if we decide >> to remove the black box from

Re: [Development] QDataStream: blackbox or document all versions?

26.09.2016, 12:35, "Simon Hausmann" : > Hi, > > I'm very much in favor of using a proper schema based system such as protocol > buffers if we decide > > to remove the black box from serialization. They don't appear to be > connected, but the moment you > > need to deal

Re: [Development] QDataStream: blackbox or document all versions?

26.09.2016, 10:15, "Thiago Macieira" <thiago.macie...@intel.com>: > On segunda-feira, 26 de setembro de 2016 00:42:12 PDT Konstantin Tokarev > wrote: >>  Option 3: restore documentation of version 12 and declare that it's the only >>  format version that is mea

Re: [Development] QDataStream: blackbox or document all versions?

25.09.2016, 06:58, "Thiago Macieira" : > A thread[1] on the interest mailing list started when someone asked for the > docs for the current format of the QDataStream wire protocol, to which I > replied that it doesn't exist as we don't maintain such docs. > > Long

Re: [Development] QDataStream: blackbox or document all versions?

26.09.2016, 00:12, "Konstantin Tokarev" <annu...@yandex.ru>: > 25.09.2016, 06:58, "Thiago Macieira" <thiago.macie...@intel.com>: >>  A thread[1] on the interest mailing list started when someone asked for the >>  docs for the current form

Re: [Development] QDataStream: blackbox or document all versions?

25.09.2016, 06:58, "Thiago Macieira" : > A thread[1] on the interest mailing list started when someone asked for the > docs for the current format of the QDataStream wire protocol, to which I > replied that it doesn't exist as we don't maintain such docs. > > Long

Re: [Development] linuxdeployqt

21.09.2016, 20:41, "Thiago Macieira" : > On quarta-feira, 21 de setembro de 2016 19:24:34 PDT Oswald Buddenhagen wrote: >>  > and you can then search the >>  > paths from /etc/ld.so.conf & /etc/ld.so.conf.d/*. >> >>  that will suffer from x-build issues again. > >

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

21.09.2016, 12:34, "Friedemann Kleint" : > Hi, > > technically speaking: is using the .rst format set in stone? I find this > difficult to handle; one needs a local web server to view it AFAIK. .md > comes to mind as alternative? Are you implying that you need local web

Re: [Development] Notes on "Qt Build Systems" @ QtCon 2016

20.09.2016, 22:21, "Matthew Woehlke" : > On 2016-09-15 02:57, Oswald Buddenhagen wrote: >>  On Wed, Sep 14, 2016 at 12:05:15PM +0200, Stephen Kelly via Development >> wrote: >>>  I want to understand Qbs and what it can do with a dynamic build graph >>>  which CMake

Re: [Development] Notes on "Qt Build Systems" @ QtCon 2016

20.09.2016, 22:11, "Matthew Woehlke" : > That works with e.g. make/ninja, but not so well with VS, but that's a > VS failing that I don't see how Qbs could overcome, given that VS *is* > the build tool and doesn't AFAIK support dynamic build graphs. QBS does not use

Re: [Development] linuxdeployqt

19.09.2016, 19:06, "Thiago Macieira" : > On segunda-feira, 19 de setembro de 2016 17:58:22 PDT Kevin Kofler wrote: >>  Louai Al-Khanji wrote: >>  > From a quick look it seems to be mostly well written. I do wonder whether >>  > it might be better to use a tool other

Re: [Development] NSURLConnection backend in 5.6.2

13.09.2016, 21:33, "Jake Petroules" : >  Because the APIs are deprecated by Apple so they would have had to be > removed/changed soon anyways, especially when an alternative (which is the > default now) is already available. AFAIK they cannot remove API from released

Re: [Development] QBS module git cloning

10.09.2016, 01:10, "Ernst Maurer" : > Each time, when I'm trying to clone qt creator I'm getting the error related > with QBS >  (I'm not an active developer, and I do this probably monthly) > Do I something wrong? because it happens always when I'm trying to get >

Re: [Development] Qt API review with clazy

10.09.2016, 18:29, "Sergio Martins" : > Hi, > > I've been developing a Qt oriented clang compiler plugin called clazy [1]. > > It has about 50 custom checks/warnings for common Qt and C++ mistakes. > I would like to propose clazy to be used to sanitize API of new Qt

Re: [Development] Notes on "Managing Qt's branches" session @ QCS 2016

10.09.2016, 15:32, "Marc Mutz" : > Hi Lars, > > On Friday 09 September 2016 15:21:04 Lars Knoll wrote: >>  A cherry-picking approach for the LTS branch can make sense, as it >>  distributes the burden of bringing the bug fix to both the stable and LTS >>  branch over all

Re: [Development] Notes on "Qt Build Systems" @ QtCon 2016

08.09.2016, 15:03, "Bo Thorsen" : > Den 08-09-2016 kl. 13:47 skrev Milian Wolff: >>  On Donnerstag, 8. September 2016 13:41:21 CEST Bo Thorsen wrote: >>>  Den 05-09-2016 kl. 20:49 skrev Milian Wolff: >  As an incredibly simple example, make is inherently limited in that

Re: [Development] Notes on "Qt Build Systems" @ QtCon 2016

07.09.2016, 14:17, "BogDan Vatra" : > On marți, 6 septembrie 2016 17:35:03 EEST Cristian Adam wrote: >>  On Tue, Sep 6, 2016 at 5:14 PM, Kevin Kofler wrote: >>  > I guess somebody could even get CMake to write Qbs files, it would just be >>  > one more

Re: [Development] Notes on "Qt Build Systems" @ QtCon 2016

06.09.2016, 18:24, "Jake Petroules" : >> On Sep 6, 2016, at 5:14 PM, Kevin Kofler wrote: >> >> Ch'Gans wrote: >>> I never wanted to use CMake b/c for me it look like a gross hack >>> (Reminds me of GNU M4). >> >> The CMake language is much easier to

Re: [Development] [FYI] on gerrit change retargeting requests

06.09.2016, 12:44, "Oswald Buddenhagen" : > On Mon, Sep 05, 2016 at 09:17:59PM +, J-P Nurmi wrote: >>  On 05 Sep 2016, at 19:27, Marc Mutz wrote: >>  > It's not about restricting what a user can do. It's simply missing >>  > implementation, and

Re: [Development] Notes on "Qt Build Systems" @ QtCon 2016

05.09.2016, 16:38, "Kevin Kofler" : > Andrew Knight wrote: >>  - (Tobias) Cmake is the "worst" system in Qt Creator because CMake >>  doesn't give enough feedback to the IDE. We need first-class support for >>  CMake in Qt Creator, though, so that is irrelevant to the

Re: [Development] [Interest] [Announcement] QtWebKit Technology Preview 3

19.08.2016, 22:08, "Jason H" : >>  Hello everyone, >> >>  We are pleased to announce QtWebKit Technology Preview 3! >> >>  Highlights of this release are: >> >>  * NPAPI and Qt plugins are finally supported on X11 and Windows (not on >> macOS >>  yet, sorry) >> >>  * Bulk of the

[Development] [Announcement] QtWebKit Technology Preview 3

Hello everyone, We are pleased to announce QtWebKit Technology Preview 3! Highlights of this release are: * NPAPI and Qt plugins are finally supported on X11 and Windows (not on macOS yet, sorry) * Bulk of the patches which have never been in the trunk of webkit.org was merged from Qt

Re: [Development] Adding 3rdpary libraries to QtSerialBus

12.08.2016, 07:32, "Alexander Nassian" : > Interesting enough that Qt itself switched the OSS license to v3 ... Don't mix up changing license of your project to more restrictive with using restrictively licensed 3rd party libraries. > >>  Am 11.08.2016 um 22:22

Re: [Development] Revisiting high-DPI configuration options

20.07.2016, 21:08, "Thiago Macieira" : > On quarta-feira, 20 de julho de 2016 21:03:48 PDT Prav wrote: >>  > Startup. >> >>  Approximately how many icons app have to have to see influence on app's >>  startup? > > That depends on the complexity of your SVG icons and

Re: [Development] Revisiting high-DPI configuration options

20.07.2016, 20:12, "Prav" : > Hello, Everyone. > >>  That's one reason, but there are two more equally, if not more important: >>  1) SVG rendering is orders of magnitude slower than PNG. Icon-heavy >>  applications suffer if they use it. > > Why SVG support of QIcon can

[Development] Why QFontDatabase::hasFamily() is marked as internal?

Hello, Are there any reasons not to make QFontDatabase::hasFamily() a part of public API? -- Regards, Konstantin ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Use of Standard Library containers in Qt source code

01.07.2016, 21:37, "Thiago Macieira" : > Premises not under discussion: > > Qt source code is product and meant to be read by our users > Qt source code must be clean and readable > > The above is not up for debate. > > For some time now, we've had a

[Development] [Announcement] QtWebKit Technology Preview 2

Hi all, We are pleased to announce QtWebKit Technology Preview 2. You can find download links below [1]. This release includes bug fixes and improvements as compared to Technology Preview 1 [2]. Restored Web APIs to improve feature parity with QtWebKit 5.7:

Re: [Development] tarball fetches from code.qt.io?

18.06.2016, 21:37, "René J.V. Bertin" <rjvber...@gmail.com>: > On Saturday June 18 2016 20:36:51 Konstantin Tokarev wrote: > >>  > Also, 5.6.2? Now that 5.7.0 is out? I'm a bit confused, are there reasons >> not to update to 5.7 apart from the fact it came

Re: [Development] tarball fetches from code.qt.io?

17.06.2016, 15:34, "René J.V. Bertin" <rjvber...@gmail.com>: > On Friday June 17 2016 13:17:23 Konstantin Tokarev wrote: > > Hi Konstantin, > >>  This error was caused by a real problem in QtWebKit sources when it is >> compiled >>  with -mmacos

Re: [Development] tarball fetches from code.qt.io?

18.03.2016, 21:25, "René J. V. Bertin" : > Oswald Buddenhagen wrote: > >>  On Fri, Mar 18, 2016 at 12:54:25PM +0100, René J. V. Bertin wrote: >>>  Is that correct? Trying this currently fails because at some point headers >>>  are not found that are expected in a QtWebkit

Re: [Development] QtSingleApplication in Qt proper?

16.06.2016, 11:07, "Kevin Funk" : > On Donnerstag, 16. Juni 2016 03:43:29 CEST Kevin Kofler wrote: >>  Kevin Funk wrote: >>  > To come to the point: We'd like to be able to use QtSingleApplication, >>  > without having to copy it to every KDE application's repository out there >>  

Re: [Development] Can we use std::unique_ptr in Qt base/modules sources since Qt5.7 ?

15.06.2016, 18:02, "Thiago Macieira" : > On quarta-feira, 15 de junho de 2016 15:44:09 PDT Giuseppe D'Angelo wrote: >>  Il 14/06/2016 19:01, Sune Vuorela ha scritto: >>  > You can pass your own classes as handlers, provided that they have a >>  > public static function

Re: [Development] Can we use std::unique_ptr in Qt base/modules sources since Qt5.7 ?

14.06.2016, 18:03, "Bo Thorsen" : > Den 13-06-2016 kl. 12:16 skrev Denis Shienkov: >>>  QScopedPointer? >> >>  Do you have real example? ;) > > Well, as Sean wrote it lacks the move, but if all you're after is to use > it for a pointer in a class or make a local dynamically

Re: [Development] QtWebKit is coming back

annulen/webkit/wiki/Building-QtWebKit-on-OS-X > > Stephen Chu > > On 6/4/16, 3:20 PM, "Development on behalf of Konstantin Tokarev" > <development-bounces+stephen.chu=mathworks@qt-project.org on behalf of > annu...@yandex.ru> wrote: > >> Hi all, >

Re: [Development] QtWebKit is coming back

Allan, Thanks for write-up, I'd like to add just a few side notes 08.06.2016, 22:49, "Allan Sandfeld Jensen" : >  I was asked how we used to structure and develop QtWebKit, and how it would >  relate to the new project. So here some background and my thoughts: > >  The way

Re: [Development] QtWebKit is coming back

a few instructions. > > Stephen Chu > > On 6/4/16, 3:20 PM, "Development on behalf of Konstantin Tokarev" > <development-bounces+stephen.chu=mathworks@qt-project.org on behalf of > annu...@yandex.ru> wrote: > >> Hi all, >> >> As some

Re: [Development] QtWebKit is coming back

07.06.2016, 09:47, "Florian Bruhin" : > * Lars Knoll [2016-06-07 06:38:35 +]: >>  Ok, in this case a separate repo is maybe a better strategy. >>  WebKitQt (as Allan proposed) might be a good name in this case :) > > I don't want to start any

Re: [Development] QtWebKit is coming back

t; Cheers, > Lars > > On 04/06/16 22:40, "Development on behalf of Thiago Macieira" > <development-bounces+lars.knoll=qt...@qt-project.org on behalf of > thiago.macie...@intel.com> wrote: > >> Em sábado, 4 de junho de 2016, às 22:20:14 BRT, Konstantin Tokarev escr

Re: [Development] QtWebKit is coming back

on behalf of Thiago Macieira" > <development-bounces+lars.knoll=qt...@qt-project.org on behalf of > thiago.macie...@intel.com> wrote: > >> Em sábado, 4 de junho de 2016, às 22:20:14 BRT, Konstantin Tokarev escreveu: >>>  2. Is it OK to use "QtWebKit" nam

[Development] QtWebKit is coming back

Hi all, As some of you may already know, there is an ongoing effort to revive QtWebKit by updating its WebKit engine to the current state of upstream at webkit.org [1]. While it still haven't reached feature parity with QtWebkit module hosted by Qt Project, its Widgets API is already in a

Re: [Development] commas in ctor-init-lists

01.06.2016, 15:41, "Marc Mutz" : > Hi, > > There seems to have been a silent underground move to uglify the Qt sources > , by using commas to introduce lines > . I have no idea where this came from It's codified by WebKit coding style, and many people here have contributed

Re: [Development] commas in ctor-init-lists

01.06.2016, 16:50, "Jędrzej Nowacki" : > On Wednesday 01 of June 2016 15:16:01 Andreas Aardal Hanssen wrote: >>  > Den 1. jun. 2016 kl. 15.06 skrev Mark Gaiser : >>  > ... >>  > Funny in the coding style you mention. For operators: "An operator at the >>

Re: [Development] QtWebkit to vcxproj

27.05.2016, 09:47, "raven-worx Software" : > Oswald Buddenhagen wrote: > >>  note that vcxproj support for the build of qt as a whole has been >>  dropped a while ago, which is reflected by incomplete projects being >>  generated. you may be able

Re: [Development] Move assignment without move constructors

23.05.2016, 19:25, "Giuseppe D'Angelo" <giuseppe.dang...@kdab.com>: > Il 23/05/2016 18:11, Konstantin Tokarev ha scritto: >>  Hello, >> >>  I've stumbled upon QPixmap having operator=(QPixmap&&) but missing >> QPixmap(QPixmap&

[Development] Move assignment without move constructors

Hello, I've stumbled upon QPixmap having operator=(QPixmap&&) but missing QPixmap(QPixmap&&), however it seems like there are a lot of Qt classes in the same situation, for example: QDir QFileInfo QProcessEnvironment QStorageInfo QUrlQuery QMimeType QCollatorSortKey QCommandLineOption

Re: [Development] Short QDateTime optimisation

02.05.2016, 10:44, "Thiago Macieira" : > Hello > > https://codereview.qt-project.org/157714 > > I've just pushed one large commit that changes QDateTime to support a "short > QDateTime Optimisation". Inspired by the SSO mechanism used in libc++ and > similar to what

Re: [Development] CI for Qt WebKit

11.04.2016, 23:34, "Knoll Lars" : > Hi, > > we’re planning on doing a slight adjustments to how Qt WebKit and other > unsupported modules are CI tested for 5.7 and onwards. Basically, they will > not be tested as part of qt5.git integrations anymore and thus won’t

Re: [Development] gerrit : using branches (was: pointers to use it cleverly/efficiently?)

04.04.2016, 12:32, "René J. V. Bertin" : > Welbourne Edward wrote: > > Hi, > >>>  What works well for me e.g. before doing a commit is what I think of >>>  as manual rebasing: I remove my patches one way or another, git-pull, >>>  and then reapply the patch(es). >> >>  

<    1   2   3   4   5   6   7   >