Re: [Development] new "debugsupport" module and API

On 19/05/14 15:39, "Ulf Hermann" wrote: >> Please don't. quick1 is especially usefull on platforms without any >>OpenGL. >> And quick1 can be built without qtdeclarative. Most of the current >> dependencies are optional, and even qtwebkit depending on qtdeclarative >>is >> artificial in qt.pro. q

Re: [Development] Proposal: removing the release branches after the release

On 26/05/14 21:59, "Thiago Macieira" wrote: >I've just seen that all the Qt repositories got a 5.3.0 branch (including >those for which a release not called "5.3.0" was produced). > >I'm proposing to reverse that. There's no point in having those branches, >since after the code is tagged and rel

Re: [Development] Bringing Qt's high-dpi support to more platforms

On 26/05/14 23:58, "Portale Alessandro" wrote: >> From: Sorvig Morten [morten.sor...@digia.com] >> Sent: Monday, May 26, 2014 14:03 >> >> On 23 May 2014, at 18:30, Thiago Macieira >>wrote: >> >> > Em sex 23 maio 2014, às 07:20:42, Sorvig Morten escreveu: >> >> Adding support to QtWayland looks

[Development] Qt 5.3 released

Hi, I’m happy to announce that we have just released Qt 5.3. You can find more details at my blog post at http://blog.qt.digia.com/blog/2014/05/20/qt-5-3-released/ . A big thanks goes to everybody who helped make the release happen. Cheers, Lars ___

Re: [Development] Modules in qtbase (was: Re: new "debugsupport" module and API)

On 13/05/14 11:49, "Bubke Marco" wrote: >Actually the different the difference between qtdeclarative and qtbase is >already producing enough overhead. For example bisect is hard to >impossible which I need to do often to find out smart changes. I very much disagree. The changes and refactorings

Re: [Development] Modules in qtbase (was: Re: new "debugsupport" module and API)

On 13/05/14 08:57, "Thiago Macieira" wrote: >Em ter 13 maio 2014, às 06:01:00, Knoll Lars escreveu: >> Actually I was thinking about splitting a few more things out. In >>addition >> to the ones mentioned above, I believe we would benefit from splitting >> Qt

Re: [Development] Modules in qtbase (was: Re: new "debugsupport" module and API)

On 13/05/14 08:23, "Kalinowski Maurice" wrote: >> >The rest of the libraries in qtbase are really base stuff. >> >> Actually I was thinking about splitting a few more things out. In >>addition to >> the ones mentioned above, I believe we would benefit from splitting >> QtNetwork out into it’s ow

[Development] Modules in qtbase (was: Re: new "debugsupport" module and API)

On 12/05/14 22:40, "Thiago Macieira" wrote: >Em seg 12 maio 2014, às 19:35:24, Oswald Buddenhagen escreveu: >> On Mon, May 12, 2014 at 08:39:37AM -0700, Thiago Macieira wrote: >> > Em seg 12 maio 2014, às 11:48:21, Ulf Hermann escreveu: >> > > The following changes create a debugsupport module wi

Re: [Development] Qt 5.3 header diff: QtQml

Look ok to me. Lars On 23/04/14 12:55, "Simon Hausmann" wrote: >On Tuesday 22. April 2014 14.12.46 Thiago Macieira wrote: >> http://macieira.org/~thiago/qt-5.3/QtQml.diff > >I think those changes look okay. > >The bulk of the work going into Qml right now is all focused on the >internals >firs

Re: [Development] Qt 5.3 header diff: QtSql

On 23/04/14 09:34, "Olivier Goffart" wrote: >On Wednesday 23 April 2014 00:28:46 Thiago Macieira wrote: >> Em qua 23 abr 2014, às 09:17:37, Olivier Goffart escreveu: >> > Just a little problem. >> > >> > +#if QT_DEPRECATED_SINCE(5, 3) >> > QSqlError( const QString& driverText = QString(), >

Re: [Development] Qt 5.3 header diff: QtPrintSupport

Also ok. Lars On 22/04/14 23:12, "Thiago Macieira" wrote: >http://macieira.org/~thiago/qt-5.3/QtPrintSupport.diff ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] utf-8 BOM and parsers

On 22/04/14 16:36, "Thiago Macieira" wrote: >Em ter 22 abr 2014, às 12:35:33, Knoll Lars escreveu: >> Hi, >> >> Just came back from vacation today. >> >> Unfortunately BOM’s at the beginning of files seem to still be used >>quite >> a bit

Re: [Development] utf-8 BOM and parsers

Hi, Just came back from vacation today. Unfortunately BOM’s at the beginning of files seem to still be used quite a bit esp. in the Windows world. So I would actually vote for option 1 and rather keep compatibility. Reason is that stripping the BOM will not break anything, but leaving it in will.

Re: [Development] HEADS UP: Qt 5.3.0 - merge stable into release

Hi, On 03/04/14 09:53, "Sergio Ahumada" wrote: >On 03.04.2014 09:42, Heikkinen Jani wrote: >> Hi, >> >> We are about to start the "Qt 5.3.0" release as agreed in [1], which >> means that: >> >> - We plan to do a fast-forward merge from 'stable' into 'release' branch >> on April 10th. > >Hi, >

Re: [Development] Nominating Sze Howe Koh as approver

Another +1 :) Lars On 23/03/14 10:13, "Smith Martin" wrote: >+1 > >From: development-bounces+martin.smith=digia@qt-project.org >[development-bounces+martin.smith=digia@qt-project.org] on behalf of >Thiago Macieira [thiago.macie...@intel.com] >Sent

Re: [Development] Qt patches to support AArch64 architecture

Hi, I’m happy to get aarch64 support in. Please add me to the reviews for stuff that is under BSD or public domain. Thanks, Lars On 11/03/14 17:40, "Dmitry Shachnev" wrote: >Lars: this mail needs your attention. > >Hi, > >AArch64 is a new 64-bit ARM architecture, that will be used in a big >ra

Re: [Development] Current problems in CI

On 13/03/14 21:14, "John Layt" wrote: >On 13 March 2014 18:21, John Layt wrote: >> On 13 March 2014 18:08, Frederik Gladhorn >>wrote: >>> Looks like we're somewhat back on track. We got a first run for qtbase >>>passing >>> and hopefully start getting the backlog down. Thanks for bearing with >

Re: [Development] Branches and time based releases

On 27/02/14 11:28, "Oswald Buddenhagen" wrote: > >> > so to come back to the starting point: i think we should continue to >> > target the release branch directly. the burden for the developers >>isn't >> > very big (actually, one can even argue that the burden being there is >>a >> > good thing

[Development] Branches and time based releases

Hi, there’s been quite a bit of discussions on both topics lately. I’ll sum up my thinking in a separate mail, as I think they are to some extent related. Let’s start with our release cycle. In my opinion (and having seen 15 years of doing Qt releases), our time based releasing model works better

Re: [Development] Qt 5.2.0 and Qt 5.1.1 are missing from the archives

On 20/02/14 10:05, "Heikkinen Jani" wrote: >What I have discussed here the process has been to move stuff to the >archive when new minor release is done. From that point of view archive >is almost up to date, only 5.1.1 is missing. > >But it is also OK to put stuff to the archive when new release

Re: [Development] RFC: Deprecating setSharable / isSharable in our containers and QString

On 20/02/14 08:32, "Thiago Macieira" wrote: >... and removing them in Qt 6 > >Please raise your hand if you knew we had that feature. > >Please raise your hand if you've ever used them in your own code. > >I doubt anyone has raised their hands to the second question and there >mustn't >be more t

Re: [Development] Plans for printing in 5.3 onwards

On 17/02/14 13:47, "John Layt" wrote: >On Wednesday 12 Feb 2014 15:37:29 John Layt wrote: >> On Wednesday 12 Feb 2014 12:03:53 John Layt wrote: > >> > Sorry, needed to wait until the full stack of changes had been >>completed >> > and integrated before pushing. The revised patches are up for revi

Re: [Development] HEADS UP: merge stable into release and dev into stable

On 17/02/14 13:01, "Simon Hausmann" wrote: >On Monday 17. February 2014 07.16.12 Heikkinen Jani wrote: >> Hi all, >> >> It seems we cannot start merge from dev branch to stable at the moment >> because there is still some issues to be solved before that: >> >> 1. There seems to be compilat

[Development] Maintainer & Approver update

Hi, Quite a bit more then the required time has passed for the Maintainer/Approver nominations from December and January. So I’d like to congratulate Yoann, Paul and Simon to their new maintainer roles, and Tony, Simo, Matti, Akseli, Jani to becoming Approvers. I’ve updated Jira, Gerrit and the M

Re: [Development] [I/O, Core] Defer a emitting of signal. It is possible?

On 10/02/14 08:52, "Thiago Macieira" wrote: >Em seg 10 fev 2014, às 11:45:31, Denis Shienkov escreveu: >> > Yes, profile it and let us know where the exact problem is. >> >> Ok, thanks. I will try do it as will have a free time. > >Last time I profiled our I/O code, the hotspot was memcpy. We

Re: [Development] Removing MSVC2008 from the CI build farm?

In addition, it’s still required for WinCE. I don’t think we can remove 2008 just yet. Cheers, Lars From: Chris Colbert mailto:sccolb...@gmail.com>> Date: Thursday 6 February 2014 02:28 To: Thiago Macieira mailto:thiago.macie...@intel.com>> Cc: "development@qt-project.org

Re: [Development] Bug fixes to Stable or Dev branch?

For now the policy is still to push to stable. We haven’t made any decision on whether to do or not do a 5.2.2 release yet, but it’s something we need to figure out rather soon. Cheers, Lars On 05/02/14 15:55, "John Layt" wrote: >Hi, > >I've seeing contradictory advice on Gerrit as to which bra

Re: [Development] Plans for printing in 5.3 onwards

On 05/02/14 13:59, "Knoll Lars" wrote: >Hi John, > >I’ve now gone through all changes. The set looks pretty good overall, and >testing on Linux showed no regressions compared to 5.2. One correction here: The paperRect as shown in the preview of the dialogs manual te

Re: [Development] Plans for printing in 5.3 onwards

Hi John, I’ve now gone through all changes. The set looks pretty good overall, and testing on Linux showed no regressions compared to 5.2. IMO, you can go ahead and stage the first set of changes that are mainly cleanups. There are quite a few comments on the changes adding the new public API.

Re: [Development] Plans for printing in 5.3 onwards

Hi John, Thanks a lot for all your work. I¹ll have a look at the changes as well. Cheers, Lars On 30/01/14 01:15, "John Layt" wrote: >On Monday 06 Jan 2014 22:40:44 you wrote: > >> My aims for the 5.3 release will be to >> * Define the new qpa print device api and implement support for the 3 >

Re: [Development] Prettier printing of Unicode strings

On 27/01/14 00:03, "Thiago Macieira" wrote: >On domingo, 26 de janeiro de 2014 20:17:20, Knoll Lars wrote: >> I usually prefer the output in utf8, as it gives readable strings (at >> least on Mac and Linux as long as you don¹t mess with the locale). >>Escaped &

Re: [Development] Prettier printing of Unicode strings

On 26/01/14 20:39, "Thiago Macieira" wrote: >On domingo, 26 de janeiro de 2014 12:36:27, Jan Kundrát wrote: >> On Tuesday, 21 January 2014 01:05:07 CEST, Thiago Macieira wrote: >> >Actual (s) : \u221212\u20A0\uD800\uDC00 >> >Expected (s2): \u221212\u20AC\uD800\uDC00 >> >> [...] >> >>

Re: [Development] Proposing Valerio Valerio (VDVsx) for Approver rights to messagingframework

On 23/01/14 00:32, "Thiago Macieira" wrote: >On quarta-feira, 22 de janeiro de 2014 22:50:49, Robin Burchell wrote: >> Hello, >> >> I'd like to propose Approver rights for Valerio on messaging framework. >> >> Justification: Valerio has worked on (& with) QMF for a long time, on >> both the Nok

Re: [Development] QtWebSockets as add-on: current voting status

Ok, let’s keep it as an add-on for now. I’m happy with that solution as well. When it comes to the QML API, I do agree with Simon that having compatibility with the standard JS web sockets API is important so people can re-use code. But that doesn’t have to exclude a more declarative QML API. C

Re: [Development] Text to Speech classes (tts)

+1 for the playground module. Cheers, Lars On 17/01/14 14:21, "Frederik Gladhorn" wrote: >Hi, > >I recently worked on a few small classes that wrap native TTS frameworks >(for >now SAPI5 on Windows, the Cocoa API on Mac, speech-dispatcher on Linux >and the >native Android tts framework). > >S

Re: [Development] Qt 5.3 Feature freeze is coming quite soon...

Ok, that's around 10% of Qt Network. From my side, I'm ok to simply add it there (and the QML component to qtdeclarative), but I'd like to hear an opinion from Peter and Rich. Cheers, Lars On 17/01/14 09:07, "Kurt Pattyn" mailto:pattyn.k...@gmail.com>> wrote:

Re: [Development] Qt 5.3 Feature freeze is coming quite soon...

>From a feature point of view it would fit best into Qt Network. But it's a >sizeable piece of code added to Qt Network. Do you have any numbers on how >this changes the size of Qt Network? Peter and Rich, and comments from your side? Cheers, Lars On 16/01/14 19:41, "Steve Gold" mailto:steveg

Re: [Development] Platform maintainers

Yes, I was about to write a mail about it. We don't currently officially have maintainers for platforms, but they exist in reality, and I'd like to make them explicit. So if nobody disagrees, I'll add them to the list next week. Cheers, Lars On 10/01/14 18:22, "David Faure" wrote: >Could we a

[Development] QtQml maintainer nomination

Hi, I'd like to continue on filling gaps in our maintainer list and thus want to propose Simon Hausmann as the new maintainer for QtQml. Guess I don't need to say a whole lot more about the nomination... ;-) Cheers, Lars ___ Development mailing list De

[Development] Nominating people from our release team for approver rights

Hi, I’d like to nominate a couple of people from the release team for approver rights. They’ve been working for the last 14 month with our release and CI infrastructure, and even though many of their contributions are not as directly visible (and often aren’t visible in gerrit), they are highly im

Re: [Development] 'register' not fully removed from Qt?

On 25.12.13 23:03, "Thiago Macieira" wrote: >On quarta-feira, 25 de dezembro de 2013 17:45:13, Jiergir Ogoerg wrote: >> return bswap_32(source); >> >> >> So was 'register' reintroduced or not fully removed, or something else? > >Something else. bswap_32 is a macro. I’m getting this as we

Re: [Development] Coding style proposal

On 02.01.14 08:42, "Simon Hausmann" wrote: >On Thursday 2. January 2014 09.34.21 Konstantin Ritt wrote: >> 1. In cpp, we typically use enums for numeric constants. In Qt coding >> style, enums are in CamelCase. >> 2. Just a wasting of time. Simply use generated documentation rather >>than >> sc

Re: [Development] Documentation maintainer

ith=digia@qt-project.org >[development-bounces+martin.smith=digia@qt-project.org] on behalf of >Laszlo Papp [lp...@kde.org] >Sent: Wednesday, December 18, 2013 7:15 PM >To: Knoll Lars >Cc: Pasion Jerome; development@qt-project.org >Subject: Re: [Development] Documentation

[Development] Documentation maintainer

Hi, I’d also like to nominate Topi Reiniö as the overall maintainer of our documentation. Topi has been doing an excellent job in handling and improving our documentation over the last year, and is IMO the best candidate we have for the job. Cheers, Lars _

[Development] QPA maintainer

Hi, I’d like to nominate Paul Tvete as the formal maintainer of the QPA architecture. He’s the original architect behind it anyway, and I don’t think there are many people out there who know it better :) Cheers, Lars ___ Development mailing list Develo

[Development] Multimedia maintainer

Hi, the first maintainer I’d like to nominate is Yoann Lopes for multimedia. Yoann has been taking care of multimedia for the last year, and done lots of work on the different backends. https://codereview.qt-project.org/#q,owner:yoann.lopes%2540digia.com,p,0028 cb2200011062 Cheers, Lars ___

[Development] Maintainer list

Hi everybody, Now that we have Qt 5.2 out, I’ve taken some time to go through the Maintainer list on our wiki (http://qt-project.org/wiki/Maintainers) trying to clean it up and remove outdated information. I’ve especially updated the list of modules that we have and removed everybody listed as a m

Re: [Development] Nominating Michael Brüning as Approver

Another +1. Lars On 13/12/13 23:51, "Allan Sandfeld Jensen" wrote: >On Friday 13 December 2013, Jocelyn Turcotte wrote: >> Hello, >> >> Michael has been working for Nokia since 2008 and joined the QtWebKit >>team >> in 2011, which he then followed in Digia. He has since then been >> contributi

Re: [Development] Enabling SSE2 by default on x86 builds (32-bit)

On 11/12/13 10:03, "Simon Hausmann" wrote: >On Wednesday 11. December 2013 09.36.46 Simon Hausmann wrote: >[...] >> > If we apply the change I mentioned in the other email, we change >>cases 2 >> > and 3: >> > >> > 2bis) distro builds Qt once with -no-sse2 flags >> > >> >=> all libs compile

Re: [Development] [Request] Compiler warnings in Qt

I think this is ok for the headers, but I don’t think we’d be doing ourselves a favor if we tried to use these warnings for .cpp files. Lars On 07.12.13 20:45, "Thiago Macieira" wrote: >On sábado, 7 de dezembro de 2013 13:36:35, Kurt Pattyn wrote: >> "-Wsign-conversion"

[Development] 5.3 schedule

Hi everybody, Now that 5.2 is getting close to being released, I think it’s time to have a look at a time schedule for 5.3. I’d like 5.3 to be less feature oriented then 5.2 has been, and more focused on stability and performance. At the same time I would like to adjust our release schedules, so

Re: [Development] Deprecating & removing the old atomics

On 03.12.13 03:02, "Thiago Macieira" wrote: >On quarta-feira, 19 de dezembro de 2012 15:00:41, Thiago Macieira wrote: >> I'd like to propose the following: >> - Qt 5.1 deprecates the old atomic code and their platforms >> - Qt 5.2 *removes* the code that doesn't get updated > >Looks like we for

Re: [Development] Integration of qt5.git

On 30/11/13 15:22, "Gladhorn Frederik" mailto:frederik.gladh...@digia.com>> wrote: On Friday 29. November 2013 21.19.33 Hausmann Simon wrote: > Once scenario I'm worried about is when a less active module (say qtscript) > has a regression test failure due to a change in an active module (qtbas

Re: [Development] New Qt 5.2 snapshot build #172

On 27/11/13 10:09, "Koehne Kai" wrote: >> Subject: Re: [Development] New Qt 5.2 snapshot build #172 >> >> Hi all. >> >> I find this one: https://bugreports.qt-project.org/browse/QTBUG-35002 >> >> I cannot remember any other related to 5.2 RC1 installer fonts. Do you >>see this is blocking RC1? I

Re: [Development] New Qt 5.2 snapshot build #172

I have to agree with Thiago. I tried the install on a retina mac book/10.9 two weeks ago, and the installer looked extremely ugly. It simply doesn¹t make for a good first impression. Cheers, Lars On 26.11.13 16:22, "Thiago Macieira" wrote: >On terça-feira, 26 de novembro de 2013 14:55:52, Koehn

Re: [Development] Request for new Playground Repo

On 20/11/13 21:05, "Oswald Buddenhagen" wrote: >On Wed, Nov 20, 2013 at 07:53:56PM +, Andrew Wooster wrote: >> Currently there is at least one API that is specific to BlackBerry >> that provides a wrapper for PPS > >> that would be used in plugins supplied for Qt Location, as well as in >> Qt

Re: [Development] Request for new Playground Repo

On 20/11/13 20:36, "Andrew Wooster" wrote: >Hi, I'd like to request the creation of a new playground repository. > >Name: BlackBerry Extras > >Description: A repository for creating BlackBerry specific APIs that are >useful for implementing Qt functionality. > >Let me know if there are any questi

Re: [Development] Backporting QTextLayout Performance Improvements to Qt4

On 18.11.13 11:49, "Milian Wolff" wrote: >On Monday 18 November 2013 10:11:40 Knoll Lars wrote: >> Yes, once the patch is in 5.x and it affects 4.8 as well, it¹s usually >>ok >> to back port. > >I ask b/c back then Eskil wrote: > >> Eskil Abrahamsen

Re: [Development] Backporting QTextLayout Performance Improvements to Qt4

Yes, once the patch is in 5.x and it affects 4.8 as well, it¹s usually ok to back port. Cheers, Lars On 18.11.13 11:06, "Milian Wolff" wrote: >Hey all, > >I'd like to ask again whether I could backport some performance >improvements >in QTextLayout/QTextEngine from Qt5 to Qt4. > >Most notably

Re: [Development] QML and JavaScript extensions

On 16.11.13 00:26, "Alan Alpert" <4163654...@gmail.com> wrote: >On Fri, Nov 15, 2013 at 2:17 PM, Kevin Krammer >wrote: >> [...] >>> Quoting your latest post: >>> > I can understand that you'd like to have the same script engine >>>evaluate >>> > both types of script, but since the decision was to

Re: [Development] the need to add a Task-Number in the release branch ...

On 14.11.13 13:50, "Oswald Buddenhagen" wrote: >On Thu, Nov 14, 2013 at 07:52:27AM +0000, Knoll Lars wrote: >> On 13.11.13 13:38, "Oswald Buddenhagen" >>wrote: >> >or to put is a bit concisely, the proposal is to simply pay attention >>

Re: [Development] the need to add a Task-Number in the release branch ...

On 13.11.13 13:38, "Oswald Buddenhagen" wrote: >moin, > >in >http://lists.qt-project.org/pipermail/development/2013-June/011610.html >thiago proposed that all changes pushed for release need to come with a >task-number footer. >the proposal met moderate approval. >little surprisingly, thiago see

Re: [Development] Staging changes in release branch

On 13/11/13 18:49, "Sean Harmer" wrote: >Hi, > >On Tuesday 12 November 2013 12:46:46 Heikkinen Jani wrote: >> Hi all, >> >> We have agreed in release team that Antti Kokko (irc: ankokko) will >>monitor >> all approved changes in release branch and stage all clear ones (fixes >>for >> P1 & P0 iss

Re: [Development] Moving JP2 imageformat from qt-solutions to qtimageformats

+1 to moving the plugins to qtimageformats. That¹s what we have the module for. And I don¹t think moving ICNS is an issue neither, as long as we have a configure test in qtimageformats to detect whether we can compile the plugin. Cheers, Lars On 06/11/13 11:27, "Saether Jan-Arve" wrote: >Actu

Re: [Development] Maintainership of QtNetwork

On 05/11/13 21:58, "André Pönitz" wrote: >On Mon, Nov 04, 2013 at 08:49:45PM -0800, Alan Alpert wrote: >> >> > As some of you may know, Shane has a new job and therefore has a >>lot >> >> > less time to spend on QtNetwork. He, Peter and I have discussed how >> >> > we should maintain the module i

Re: [Development] Qt 5.2 header diff: QtQml

Module looks ok. Some comment inline: On 05/11/13 01:07, "Thiago Macieira" wrote: >Pastebin URL (expires in 24 hours): >http://paste.fedoraproject.org/51637/13836114 > >template > QObject *qmlAttachedPropertiesObject(const QObject *obj, bool create = >true) > { >diff --git a/src/qml/qml/qqmlcomp

Re: [Development] Qt 5.2 header diff: QtQuick

Looks ok as well. Cheers, Lars On 05/11/13 01:07, "Thiago Macieira" wrote: >Pastebin URL (expires in 24 hours): >http://paste.fedoraproject.org/51638/61143313 > >--- >diff --git a/src/quick/designer/designersupport.h >b/src/quick/designer/designersupport.h >index 5139a65..41458ae 100644 >--- a

Re: [Development] Merging patches to old/5.0 or old/5.1 branches

On 04/11/13 17:18, "Thiago Macieira" wrote: >On segunda-feira, 4 de novembro de 2013 12:18:22, Allan Sandfeld Jensen >wrote: >> The biggest problem I see with these branches is that they do not have >>any >> bots testing it, so we need to be extra careful with merging patches. I >> suggest a p

Re: [Development] Maintainership of QtNetwork

On 04/11/13 17:25, "Koehne Kai" wrote: > >> -Original Message- >> From: development-bounces+kai.koehne=digia@qt-project.org >> [mailto:development-bounces+kai.koehne=digia@qt-project.org] On >> Behalf Of Richard Moore >> Sent: Monday, November 04, 2013 1:32 PM >> To: development@

Re: [Development] Color Management support in Qt 5?

Hi John, as far as I know there¹s nobody doing any work on it right now. Cheers, Lars On 02/11/13 14:10, "John Layt" wrote: >Hi, > >I'm wondering if anyone is working on color management support in Qt >5? I know there was some thought about it before 5.0 and vague >suggestions about support i

Re: [Development] Cut 7+ms of Qt5 startup time on Linux

Before going to a binary format, I’d first like to check whether we can further speed up the parsing. I’ve done some work in that area in spring, but I know there was still quite some room to improve it. Cheers, Lars From: Jiergir Ogoerg mailto:f35f22...@gmail.com>> Date: torsdag 31. oktober 20

Re: [Development] Where and how does Qt define which platforms are supported?

On 25.10.13 09:57, "Thiago Macieira" wrote: >On sexta-feira, 25 de outubro de 2013 07:49:47, Koehne Kai wrote: >> I think we should have only: >> + Reference Platforms >> + Supported Platforms >> + Platforms Reportedly Working > >Makes sense to me. Yes, that sounds actually good. It¹s certainly

Re: [Development] #error for unreleased MSVC versions

On 24/10/13 16:51, "Koehne Kai" wrote: > >> -Original Message- >> From: development-bounces+kai.koehne=digia@qt-project.org >> [mailto:development-bounces+kai.koehne=digia@qt-project.org] On >> Behalf Of Thiago Macieira >> Sent: Thursday, October 24, 2013 4:39 PM >> To: developm

Re: [Development] Removing libudev dependency from binary packages?

Sounds like dlopen¹ing is the way to go. Sucky, but at least it¹ll work. And according to the post below most things should be compatible between udev0 and udev1. Cheers, Lars On 24/10/13 16:28, "Thiago Macieira" wrote: >On quinta-feira, 24 de outubro de 2013 13:46:39, Koehne Kai wrote: >> I ju

Re: [Development] Removing libudev dependency from binary packages?

On 22.10.13 09:24, "Thiago Macieira" wrote: >On terça-feira, 22 de outubro de 2013 07:01:22, Knoll Lars wrote: >> >There are two major versions of libudev in use in major distros: >> >libudev.so.0 >> >and libudev.so.1. The new one has been in use for about

Re: [Development] Removing libudev dependency from binary packages?

On 22.10.13 08:09, "Thiago Macieira" wrote: >On terça-feira, 22 de outubro de 2013 06:05:13, Hausmann Simon wrote: >> I think the problem is shipping binaries that accommodate the fact that >> every distro ships libudev in a different major version. That means you >> can't reliably use dynamic li

Re: [Development] Qt 5.2 Testing (System tray)

That's basically how it looks. I'm happy to accept all patches that are required upstream (after review of course), but the authors (ie. Canonical) will have to submit them here. Cheers, Lars On 10/14/13 9:44 PM, "Hausmann Simon" wrote: > >I agree very much with what Thiago said. Also note that

Re: [Development] Requesting a playground repo for QtCertificateAddon

Another +1. Cheers, Lars From: Kurt Pattyn mailto:pattyn.k...@gmail.com>> Date: søndag 13. oktober 2013 13:35 To: "development@qt-project.org" mailto:development@qt-project.org>> Subject: Re: [Development] Requesting a playground repo for QtCertificateAddon +1

Re: [Development] Disabling exception support in QtCore?

On 10/10/13 6:02 PM, "Olivier Goffart" wrote: >On Thursday 10 October 2013 08:22:44 BRM wrote: > >> I have personnally maintained a 400k+ SLOC codebase based on QT. >> It made extensive use of Signals/Slots between objects. Even though I >>was >> pretty much the only developer working on it, I st

Re: [Development] Nokia/Digia copyright in PDF produced by QPrinter

On 10/7/13 12:35 PM, "David Boddie" wrote: >On Sun Oct 6 20:51:40 CEST 2013, Lars Knoll wrote: > >> The producer field in PDF is generally used for marking what has been >>used >> to produce the PDF. In Qt 5 this reads: >> >>xprintf("\n/Producer "); >>printString(QString::fromLatin1("Qt "

Re: [Development] Nokia/Digia copyright in PDF produced by QPrinter

The producer field in PDF is generally used for marking what has been used to produce the PDF. In Qt 5 this reads: xprintf("\n/Producer "); printString(QString::fromLatin1("Qt " QT_VERSION_STR " (C) 2012 Digia Plc and/or its subsidiary(-ies)")); which gives inside the PDF: /Producer (Qt 5.

Re: [Development] ODP: Disabling exception support in QtCore?

art [oliv...@woboq.com] >Wysłano: 2 października 2013 09:09 >Do: development@qt-project.org >Cc: Thiago Macieira >Temat: Re: [Development] Disabling exception support in QtCore? > >On Tuesday 01 October 2013 23:32:00 Thiago Macieira wrote: >> On quarta-feira, 2 de outubro de 2013 05

Re: [Development] Disabling exception support in QtCore?

On 02.10.13 09:09, "Olivier Goffart" wrote: >On Tuesday 01 October 2013 23:32:00 Thiago Macieira wrote: >> On quarta-feira, 2 de outubro de 2013 05:42:24, Knoll Lars wrote: >> > On 01.10.13 23:23, "Thiago Macieira" >>wrote: >> > >On terç

Re: [Development] Disabling exception support in QtCore?

On 01.10.13 23:23, "Thiago Macieira" wrote: >On terça-feira, 1 de outubro de 2013 20:00:56, Knoll Lars wrote: >> Yes, signal/slot connections between user code should IMO still be able >>to >> pass through exceptions. I am afraid removing that will break code &g

Re: [Development] Disabling exception support in QtCore?

Yes, signal/slot connections between user code should IMO still be able to pass through exceptions. I am afraid removing that will break code that's out there. Cheers, Lars On 10/1/13 9:31 PM, "Hausmann Simon" wrote: > >Hmm question - certainly worth it for sjlj platforms like 32-bit ios. > > >

Re: [Development] Bluetooth and NFC vs Reference Platforms

important to get something out and into the hands of people. Feature freeze doesn't imply a full API freeze. We have the alpha/beta period exactly for finding issues and fixing them. A missing signal is something we can fix if required. Cheers, Lars > >Konstantin > > >Regard

Re: [Development] Bluetooth and NFC vs Reference Platforms

On 9/30/13 7:48 PM, "Konstantin Ritt" wrote: >2013/9/30 Knoll Lars > >On 9/30/13 5:38 PM, "Thiago Macieira" wrote: >> >>Similarly for Bluetooth, which exists on all platforms. But since I don't >>know >>the QtBluetooth API, I don&

Re: [Development] Codifying the .qml License Header Exemption

On 9/30/13 7:00 PM, "Oswald Buddenhagen" wrote: >On Fri, Sep 20, 2013 at 03:15:47PM -0700, Alan Alpert wrote: >> Looking at the file sizes, I recommend excluding QML files under >> "tests" from requiring a license header if they have <=15 LoC. >> >in general i support this proposal, but as i said

Re: [Development] Bluetooth and NFC vs Reference Platforms

On 9/30/13 5:38 PM, "Thiago Macieira" wrote: >Qt Project guidelines say that all features that are relevant for the >reference platforms must be implemented in the reference platforms. No. It has to be implemented on all reference platforms if the module is an essential module. Add-ons where alw

Re: [Development] Policy: supplying the preferred format for modifications for everything we ship

On 9/29/13 9:56 PM, "Thiago Macieira" wrote: >>From the Minified javascript thread, I propose this policy: > >The Qt Project will always supply in its own infrastructure the preferred >sources for modification for whatever we ship. Under the GPL and LGPL, >anyone >who receives our sources and wi

Re: [Development] Nominating Thorbjørn Martsum (ThorbjornTux) as approver

Jira should be fine as well now. Congratulations Thorbjørn! Cheers, Lars On 9/21/13 10:22 PM, "Ahumada Sergio" wrote: >gerrit done >-- >Sergio Ahumada >Release Engineer - Digia, Qt > > >From: development-bounces+sergio.ahumada=digia@qt-project.org >[

Re: [Development] Nominating Andrew Knight (aknight) for Approver

Congratulations Andrew! On 19.09.13 12:48, "Robin Burchell" wrote: >And today marks weekday 15 since the proposal, with no negative >comments. I guess that means it's time to congratulate Andrew. > >Can someone please grant the necessary JIRA/Gerrit rights? Should be done now. Cheers, Lars >

Re: [Development] QtAndroidExtras

On 17.09.13 17:59, "Thiago Macieira" wrote: >On terça-feira, 17 de setembro de 2013 14:04:38, Stromme Christian wrote: >> Hi, >> >> I would like to propose that we add a platform extras repo for Android, >>as >> we needing a place to put android specific API's. Currently the only >>api we >> hav

Re: [Development] More on QDateTime / QTimeZone

On 9/12/13 9:06 PM, "John Layt" wrote: >Hi, > >Another QDateTime email. I'm still trying to get a fully working >reimplementation of QDateTime as well as the QTimeZone support in for >5.2, but >there's a couple of issues outstanding. > >Storage format / Change of System Time Zone behaviour: My

[Development] Qt WebEngine

Hi, As many of you know, we've been doing some research on a (chromium based) new web engine for Qt during spring and summer. I wanted to let you know that we've now come to the conclusion that we want to continue these efforts in the future. Please check http://blog.qt.digia.com/blog/2013/09/12

Re: [Development] Qt Platform Extras

Ok, let's use QtWin for the namespace. For the module itself it makes IMO to keep the 'Extras' in the name. Cheers, Lars On 06.09.13 15:52, "Sorvig Morten" wrote: >I agree, QtWin::foo looks much better. We can rename the QtMacExtras >namespace as well. > >What about the module name itself? Woul

Re: [Development] A QtCore class for event-driven jobs

Full agreement with Konstantin. It's two weeks before the feature freeze and we haven't seen any more then a draft. I am against any new classes going into Qt essential modules that do not have direct and proven use cases. Develop it in a playground project, show why it makes sense and once you

Re: [Development] Making QScopedPointer scoped (again)

On 9/5/13 8:02 AM, "Olivier Goffart" wrote: >On Wednesday 04 September 2013 20:09:38 Knoll Lars wrote: > >> >You also can typedef QScopedPointer QUniquePointer; and deprecate the >> >former >> >name. >> >> typedef's are usually not s

Re: [Development] Making QScopedPointer scoped (again)

On 9/5/13 2:00 AM, "Thiago Macieira" wrote: >On quarta-feira, 4 de setembro de 2013 22:37:55, Giuseppe D'Angelo wrote: >> On 4 September 2013 22:15, Stephen Kelly wrote: >> > When there is a >> > need for QUniquePointer in the future, it is added. >> >> https://codereview.qt-project.org/#change

Re: [Development] Cherry picking to replace a change set

On 9/3/13 6:30 PM, "Thiago Macieira" wrote: >On terça-feira, 3 de setembro de 2013 11:42:04, Oswald Buddenhagen wrote: >> you did, however, make no effort to substantiate your position. >> an argument against your interpretation is for example bisectability. >> also, it's just plain illogical to

<    1   2   3   4   5   6   >