Re: [Development] Qt for NaCl port

On 11 Jun 2014, at 14:53, Thiago Macieira thiago.macie...@intel.com wrote: Em ter 10 jun 2014, às 21:33:44, Daiwei Li escreveu: Hello, I'm investigating porting an existing C++/QML application to Google NaCl, and I found that Qt had attempted a port a couple years ago:

[Development] Qt High-dpi QtCS report and patch status (on hold)

A quick report from the contributors summit (I apologize for the delay and sketchy notes): * I went though the general approach: - Setting the scale factor: - platform plugin: QWindow::devicePixelRatio, QScreen::devicePixelRatio - the user: QT_HIGHDPI_SCALE_FACTOR=2 -

Re: [Development] Private Qt helper libraries?

On 03 Jul 2014, at 17:13, Sune Vuorela nos...@vuorela.dk wrote: On 2014-07-03, Milian Wolff milian.wo...@kdab.com wrote: I imagine, it could work by create just a normal library but not install and public headers, only private ones. That should be OK then, or what do you think? We have

Re: [Development] Qt 4.x and Qt 5 frameworks should use @rpath (QTBUG-31814)

On 04 Aug 2014, at 12:22, Adam Strzelecki o...@java.pl wrote: So, let's end this discussion and start focusing efforts towards building the solution. Now let's focus on submitting patches : Before you do that, can you write up a proposal on what you want to accomplish and how to get

Re: [Development] Qt 4.x and Qt 5 frameworks should use @rpath (QTBUG-31814)

On 04 Aug 2014, at 21:38, Adam Strzelecki o...@java.pl wrote: Before you do that, can you write up a proposal on what you want to accomplish and how to get there? WHAT I WANT TO ACCOMPLISH (1) Remove need to rewrite Qt libraries (frameworks) headers during install and during

Re: [Development] Qt 4.x and Qt 5 frameworks should use @rpath (QTBUG-31814)

On 11 Aug 2014, at 23:15, Jake Petroules jake.petrou...@petroules.com wrote: This was mostly a counterargument to people complaining against copying frameworks into the bundle. However, copying frameworks into the bundle is the correct solution, and is what must be done in the end.

Re: [Development] Qt 4.x and Qt 5 frameworks should use @rpath (QTBUG-31814)

On 12 Aug 2014, at 13:37, Adam Strzelecki o...@java.pl wrote: On to my now standard question: Can you summarize the discussion so far into a proposal on what you want to change? Keep it as short as possible :) For example, I think it’s understood that (incremental) framework coping is

Re: [Development] Qt 4.x and Qt 5 frameworks should use @rpath (QTBUG-31814)

On 12 Aug 2014, at 16:25, Adam Strzelecki o...@java.pl wrote: Okay, Phase II. (1) Introduce bundle_frameworks CONFIG option, and set it default for rpath shared builds on iOS OS X (2) Introduce bundle make target, when bundle_frameworks CONFIG is set, it is added to all (3)

Re: [Development] Qt WebChannel 5.5 roadmap: WebEngine, QtWebView

On 27 Aug 2014, at 16:51, Milian Wolff milian.wo...@kdab.com wrote: On Wednesday 27 August 2014 14:49:08 Hausmann Simon wrote: I'm pretty sure that all the native webview APIs allow for at least runJavascript(string), so injection may also be an easier option. Oh nice, I assumed without

Re: [Development] Qt WebChannel 5.5 roadmap: WebEngine, QtWebView

On 27 Aug 2014, at 22:02, Milian Wolff m...@milianw.de wrote: A synchronous API is bound to fail, see WK1 vs. WK2/WebEngine. Make it asynchronous and copy the WebEngine API. I see now QQuickWebEngineView has: runJavaScript(const QString script, const QJSValue callback) So that

Re: [Development] Important OSX 10.9.5 10.10 codesign changes

On 18 Sep 2014, at 22:07, Adam Strzelecki o...@java.pl wrote: Reported already 24/Jan/14 QTBUG-36429 FYI more recent and prioritized bug report is QTBUG-38511 I think it deserves a lot of attention now since 10.9.5 is live. This will indeed receive attention in the coming days. There

Re: [Development] Important OSX 10.9.5 10.10 codesign changes

And the Info.plist should *always* set CFBundleExecutable to QtCore. To use the debug version you set the DYLD_IMAGE_SUFFIX environment variable to _debug prior to execution. A minor case: What would you do for debug-only builds? As far as I'm aware, we already do this correctly (aside

Re: [Development] Important OSX 10.9.5 10.10 codesign changes

On 19 Sep 2014, at 11:28, Sorvig Morten morten.sor...@digia.com wrote: This will indeed receive attention in the coming days. There are already some patches attached to the QTBUGs. I’ll post back here once we have a complete patch set ready. Target branches are Qt 5.3 and Qt 4.8. I’m

Re: [Development] Important OSX 10.9.5 10.10 codesign changes

On 22 Sep 2014, at 12:03, Sorvig Morten morten.sor...@digia.com wrote: On 19 Sep 2014, at 11:28, Sorvig Morten morten.sor...@digia.com wrote: This will indeed receive attention in the coming days. There are already some patches attached to the QTBUGs. I’ll post back here once we have

Re: [Development] Important OSX 10.9.5 10.10 codesign changes

On 24 Sep 2014, at 16:17, Alexander Ilyin ip.alexander.il...@gmail.com wrote: CODESIGN FAILED WITH MESSAGE unsealed contents present in the root directory of an embedded framework In subcomponent: /Developer/res-plan/bin/s-test.app/Contents/Frameworks/QtCore.framework (Please look at the

Re: [Development] CI configuration changes

On 02 Feb 2015, at 10:01, Sarajärvi Tony tony.saraja...@theqtcompany.com wrote: Hi Here's a wiki page describing the planned changed along with a bit of version information of the tools: http://qt-project.org/wiki/Qt-5.5.0-tools-and-versions Since OS X 10.7 is no longer CI tested

Re: [Development] Deprecating modules with 5.5

On 06 Feb 2015, at 09:32, Ziller Eike eike.zil...@theqtcompany.com wrote: What simpler alternative do you have in mind? One possibility that would cover the use case of “show some simple styled html without javascript” case (e.g. documentation browsers) would be to give QTextBrowser

Re: [Development] Nominating Timur Pocheptsov as approver

On 22 Jan 2015, at 07:52, Blasche Alexander alexander.blas...@theqtcompany.com wrote: Hi, I'd like to nominate Timur Pocheptsov for approver status. He wrote the OSX and iOS implementations for QtBluetooth and lately has been increasing his footprint in other modules for the same

Re: [Development] Qt for iOS: Management Retina vs Non-Retina Images

On 18 Feb 2015, at 10:59, Robert Iakobashvili corobe...@gmail.com wrote: What about support for @3x? Is it inside or is it planned? I’ve started implementing @3x support here: https://codereview.qt-project.org/106717 https://codereview.qt-project.org/106705 There’s some refactoring work

Re: [Development] Running Qt 5.4.0 Applicationat Mac 10.6

On 26 Jan 2015, at 09:09, Robert Iakobashvili corobe...@gmail.com wrote: It seems that QStyle returns 0. Should I create some style in advance and pass it to application? Which style could be appropriate for 10.6? Yes, I know that 10.6 is not a supported target for 5.4.0, but any

Re: [Development] Processing synthesized mouse events in platform plugins

On 24 Dec 2014, at 14:48, Александр Волков a.vol...@rusbitech.ru wrote: Hi all, Currently three major platform plugins (xcb, windows and cocoa) by default behave absolutely different when they receive synthesized mouse events from the system: 3) cocoa plugin doesn't distinguish them

Re: [Development] OSX 10.7 dropped from Qt?

On 27 Feb 2015, at 14:34, Blasche Alexander alexander.blas...@theqtcompany.com wrote: If 10.7 is required then it should be added back to main CI targets. If it is not added back then I will remove consequently remove every trace of it. I don’t think it will be added back. You should

Re: [Development] Mime database size

On 23 Feb 2015, at 13:00, Knoll Lars lars.kn...@theqtcompany.com wrote: Yes, I still don’t like the fact we’re embedding a 1.7M xml file in Qt Core at all. I’m not too fond of checking the binary file into the repositories, but it’s probably still better than continuing with the XML

Re: [Development] SSL Plans for Qt 5.6

On 22 Feb 2015, at 18:50, Jeremy Lainé jeremy.la...@m4x.org wrote: On 02/22/2015 06:42 PM, Richard Moore wrote: On 22 February 2015 at 17:39, Jeremy Lainé jeremy.la...@m4x.org wrote: Whilst I agree with the goal of dropping support for old / unmaintained OpenSSL versions, in the case

Re: [Development] QStandardPaths could be helpful for cross platform portability, Qt Everywhere

On 24 Feb 2015, at 07:24, Jeremy Whiting jpwhit...@kde.org wrote: Hello list, I discussed a bit with Thiago and some others on irc this evening and have realized that the QStandardPaths patch from [1] and discussion on [2] is trying to solve too many problems at once. I'll list the

Re: [Development] 5.4.1 OSX macdeployqt FAIL

On 11 May 2015, at 08:45, Ziller Eike eike.zil...@theqtcompany.com wrote: On May 10, 2015, at 9:08 PM, mark diener rpzrpz...@gmail.com wrote: Well, it looks like the big weakness in OSX deployment is macdeployqt and we are on version 5.4.1+ I was able to change my macdeployqt

Re: [Development] 5.4.1 OSX macdeployqt FAIL

On 11 May 2015, at 23:12, m...@rpzdesign.com wrote: Thiago: My intention was never (explicity or implied) to insult anyone. Now I know who the platform maintainer is! https://wiki.qt.io/Maintainers And how Mr Sorvig could take offense! And for that I share my sincere apology

Re: [Development] Rotating JPEG images by default

On 17 Apr 2015, at 10:48, Allan Sandfeld Jensen k...@carewolf.com wrote: Ideally the orientation could also be kept as metadata in QImage. I’d like to see general metadata support in QImage. The closest thing we have seems to be QImage::text(), which supports QString data only. My

[Development] Cross-platform high-DPI Qt tech preview

We are happy to share the results of our work on cross-platform high-DPI scaling in Qt, which is planned for Qt 5.6. It is now at a stage where it can be tested by others. You can get the code from our branch in qtbase: wip/highdpi. The branch is open for business, and contributions are

Re: [Development] Your actions needed, Qt5.5.0 RC Final is nearing!

On 09 Jun 2015, at 11:18, René J.V. Bertin rjvber...@gmail.com wrote: On Tuesday June 09 2015 08:27:09 Sorvig Morten wrote: I think it’s OK if other modules, and especially new modules, have stricter requirements. Qt users can make a decision if the provided OS version support

Re: [Development] Qt 5.5.0 header diff: QtWidgets.diff

On 08 Jun 2015, at 11:07, Marc Mutz marc.m...@kdab.com wrote: On Friday 05 June 2015 10:11:27 Frederik Gladhorn wrote: diff --git a/src/widgets/widgets/qmaccocoaviewcontainer_mac.h b/src/widgets/widgets/qmaccocoaviewcontainer_mac.h index a98d30f..5920c1f 100644 ---

[Development] Qt for Native Client

Hi, I’m happy to announce that a work-in-progress port of Qt to the Chrome / Native Client platform has now been pushed to the wip/nacl branch in QtBase. So far development has been closed, but we are now ready to develop in the open and also take contributions. My intention is to at some

Re: [Development] Qt LTS C++11 plans

On 18 Aug 2015, at 07:46, Thiago Macieira thiago.macie...@intel.com wrote: On Monday 13 July 2015 18:44:40 Thiago Macieira wrote: On Wednesday 08 July 2015 13:42:12 Thiago Macieira wrote: The only compiler I currently know that will have problems with this is the Intel compiler on OS X

Re: [Development] Pixelated UI elements in Windows HiDPI mode (5.6)

> On 11 Nov 2015, at 01:40, Adam Light wrote: > > I built Qt 5.6 (latest from the 5.6 git branch as of this morning) and tested > our application with the build on Windows 10. I'm calling > QApplication::setAttribute(Qt::AA_EnableHighDpiScaling); > before the QApplication

Re: [Development] mouse wheel zooming and inertial scrolling

> On 01 Sep 2015, at 18:50, René J.V. Bertin wrote: > > Hi, > > Qt4 and Qt5 both have a "feature" where holding down the Meta key (Command on > OS X) while scrolling a view causes text in the view to zoom in or out. This > also works with the 2-finger scroll that most

[Development] Qt 5.6: QWindowSystemInterface and event acceptance state

Hi, QWindowSystemInterface has recently gained the ability to return the “accepted" status of events, that is whether Qt used the event or not. The intended use case is Qt-as-a-plugin type scenarios, where we would like to propagate unhandled events back to the host. The top level visible API

Re: [Development] so it turns out there *is* a way to get Qt5 apps to use a custom style automatically?

> On 05 Sep 2015, at 15:39, René J. V. Bertin wrote: > > and I can indeed use `foo --style=kde` to start foo using the currently > selected > style for KDE applications. However: > > 1- simply setting KDEHOME to ~/.kde doesn't have any effect (it's not > required > for

Re: [Development] Qt 5.5.0 build issue on OS X (10.9): OpenGL libraries

> On 15 Sep 2015, at 03:51, Thiago Macieira <thiago.macie...@intel.com> wrote: > > On Monday 14 September 2015 08:09:28 Sorvig Morten wrote: >> Then the question is: which ones should QtGui link against? On other words >> OpenGL usage is not confined to platform

Re: [Development] Qt 5.5.0 build issue on OS X (10.9): OpenGL libraries

> On 13 Sep 2015, at 00:55, Thiago Macieira wrote: > > On Saturday 12 September 2015 18:16:54 René J. V. Bertin wrote: >> Thiago Macieira wrote: >>> Maybe we need two tests: one for OpenGL for XCB plugin (with GLX support) >>> and one for OpenGL for the Cocoa plugin

Re: [Development] Qt 5.5.0 build issues on OS X : rpath

> On 28 Sep 2015, at 23:40, Thiago Macieira wrote: > > What if we add an extra rpath to Qt libs as @executable_path/../Frameworks? > Would this make loading work? > > Jake, Morten: as a stop-gap, is there a configure-time switch to revert to > the > old behaviour?

Re: [Development] Bug in macdeployqt?

> On 17 Sep 2015, at 19:15, Dean Floyd wrote: > > Dear all, > > We have a project where we weak link our app against the Wacom framework > which on MacOSX by default gets installed in: > > /Library/Frameworks/WacomMultiTouch.framework > > otool -L returns the

[Development] High-DPI 5.6 beta update

Hi, I’d like to provide short update on the changes in this space, an also lay out some plans and possibilities for the future. Thanks to everyone who has helped out! New changes: * @3x support landed, both for Qt Widgets and Qt Quick. Implemented as @Nx support, with @9x as a maximum value.

Re: [Development] High-DPI 5.6 beta update

> On 18 Dec 2015, at 01:05, Corentin Jabot wrote: > > Having stumbled upon this issue very recently, here are my 2 cents. > • Svg images should be devicePixelRatio aware without having to set a > source size > • Likewise, QQuickImageProvider should know

Re: [Development] High-DPI 5.6 beta update

> On 15 Dec 2015, at 22:16, Tim Blechmann wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Your thoughts on projects that use ONLY SVG image resources > and not PNG/JPEG? But the above: 1) already works >>> >>> kind of ... the

Re: [Development] High-DPI 5.6 beta update

> On 15 Dec 2015, at 20:25, rpzrpz...@gmail.com wrote: > > Instead of worrying about @2x and @3x and trying to generate artwork in all > of the sizes, would it not be advantageous > to only use SVG vector format and allow the svg plugin to generate and scale > at run-time a single svg file in

Re: [Development] RFC: QProcess variant or separate class for launching applications "GUI-style"

> On 08 Jan 2016, at 10:03, Ziller Eike <eike.zil...@theqtcompany.com> wrote: > > >> On Jan 7, 2016, at 10:14 PM, René J. V. Bertin <rjvber...@gmail.com> wrote: >> >> Sorvig Morten wrote: >> >>> Another point: Isn't there a

Re: [Development] High-DPI on Win

Hello! > On 28 Dec 2015, at 21:50, Die Waldmanns wrote: > > (1) Support of fractional scaling (devicePixelRatio). > This ratio is qreal, but in QT5.5 it nevertheless seems not be possible to > set it to fractional values (I could get it only to 1.0,2.0,3.0 etc). In >

Re: [Development] RFC: QProcess variant or separate class for launching applications "GUI-style"

> On 08 Jan 2016, at 12:56, René J. V. Bertin <rjvber...@gmail.com> wrote: > > Sorvig Morten wrote: > >> But you seldom want to have two instances of (say) Mail running - you start >> it, or bring the existing one to front. So kLSLaunchNewInstance does not >&

Re: [Development] Qt Nacl

> On 23 Feb 2016, at 18:00, Jon Mullen wrote: > > Hey > > I’m trying to figure out how far along the Qt Nacl code is and if I’m able to > use it on the project I’m working on. I have the code built from the qtbase > wip/nacl branch. However, when I go to run the example

Re: [Development] extending QtMacExtras?

> On 18 Jan 2016, at 11:02, René J.V. Bertin wrote: > > > One thing that's really missing from Qt at the moment is a way for an > application that is not the foreground application to post a window in the > foreground (cf. also my thread on extending QProcess). To my

Re: [Development] Scalable UIs in QtQuick (take 2)

> On 18 Feb 2016, at 12:35, Nikita Krupenko wrote: > > 2016-02-18 12:50 GMT+02:00 Hausmann Simon : >> (1) In order to make it really easy to scale "logical" pixels without having >> to introduce your own context property or factor in a .qml

Re: [Development] Scalable UIs in QtQuick (take 2)

> On 18 Feb 2016, at 15:24, Welbourne Edward > wrote: > > To meet all the actual use cases, we need three different *kinds* of > size for things: > * fraction of the available display area - good for top-level >sub-division of the space an app has at its

Re: [Development] Scalable UIs in QtQuick (take 2)

> On 19 Feb 2016, at 10:44, Gunnar Sletta wrote: > > > One obvious usecase which always comes back to haunt is when those logical > units need to be translated to actual pixels, such as when dealing with > graphics. Up until some time ago, Something::size() was enough to

Re: [Development] Scalable UIs in QtQuick (take 2)

> On 19 Feb 2016, at 10:44, Gunnar Sletta wrote: > > Now every piece of code needs to also know about device pixel ratio and that > needs to passed down to image loaders, icon generators This is essential complexity, not accidental complexity. With high-DPI displays in use

Re: [Development] Qt Coding Guidelines

> On 18 Mar 2016, at 08:48, Jędrzej Nowacki > wrote: > > So I think, that we should not discuss what is better qdoc or md. The real > discussion is about tooling, what is the best tool to sanitize Qt code. We > need something that: > 1. Can work as a sanity

Re: [Development] The behaviour of Image / image provider are different from 5.5.1 to 5.6 in iOS

> On 11 Apr 2016, at 12:38, Ben Lau wrote: > > Hi, > > I am writing an image provider that read all the images to memory at startup. > And I found that the behaviour is different from 5.5.1 to 5.6 in iOS. Seems > that it is undocumented. I wonder is it an expected

Re: [Development] Qt Coding Guidelines

> On 16 Mar 2016, at 22:43, Knoll Lars wrote: > > We should actually consider having a section about contributing to Qt in our > documentation. Coding guidelines would fit nicely into that. But I think the > .qdoc files should rather live in qtdoc instead of

<    1   2