[Development] Reimplementation of HTML5 support (QtWebKit)
Hey there! My main purpose here is to reimplement some behaviour of QtWebKit on HTML5 Video support. Am I right that there is an abstract layer between actual context rendering / processing and webkit abstraction for HTML5 Video standart? So what's the best place to start with there? ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Requesting a break in behavior in QML Text element
On 29 Jan 2015, at 23:46, Olivier Goffart oliv...@woboq.com wrote: On Thursday 29 January 2015 23:24:51 Robin Burchell wrote: tl;dr: I'd like to request a behavior break in QML's Text element. I would like to change the default value of Text::textFormat from Text.AutoText to Text.PlainText. Personally, that's what I am doing in the QML project I am working on (We had to develop our own set of component (it was started before QtQuick controls), and the text component default to Test.PlainText) Given the security implication, I do believe PlainText should be the default. However, I think it's too much of a breaking change for anyone who has used html tags on purpose and did not explicitly set the format. Is it possible to do the change if we do import QtQuick 2.5 That is, the default of textFormat changes depending on the number in the import statement. +1 to that. If you update your import versions, you can expect some minor changes; and if you are editing the QML anyway, it implies that you are ready to take the time to re-test your application and make small fixes and improvements. On 29 Jan 2015, at 23:24, Robin Burchell robin...@viroteck.net wrote: Seperately, we may want to look at a restriction on the loading of remote resources in Text. I can understand allowing remote URIs in Image, but Text seems like an unexpected behavior to me. If we do that, there needs to be a way to override the restriction, maybe by adding a property to control whether loading of anything outside the QML is allowed. It would IMO be OK to have this property false by default, since the majority of use cases don’t need it. I can imagine that loading remote resources is a useful feature which some apps are relying on. In fact, a single Text element is practically a web browser already, for certain limited purposes. It's kindof cool to forego the need for a real web engine if you need only to display lightweight mid-90’s HTML. I also think we should add a source URL property like Image has. It’s unfortunate to need to rely on ugly hacks like this one http://rschroll.github.io/beru/2013/08/12/opening-a-file-in-qml.html just to be able to read a file. And I/O should be more agnostic about local and remote resources, as long as the fact that you are doing I/O is explicit rather than unintended. Sometimes you want network access to be really easy. Other times you want to avoid security problems that come from unintentional network or filesystem access. So we need to make it easy to go either direction, and enforce it consistently. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Nomating Przemyslaw Gorszkowski as approver
Hi, I'd like to nominate Przemyslaw as approver. Przemyslaw has been active in the Qt Creator project for more than 2 years, and contributed many important patches for C++ issues. He resolved some of the most annoying bugs, and handled many complicated use-cases. His contributions https://codereview.qt-project.org/#/q/owner:pgorszkowski%2540gmail.com,n,z - Orgad ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Nominating André Hartmann as approver
Hi, I'd like to nominate André as approver. André has been actively reviewing changes for over 3 years, mostly for Qt Creator, and contributed many high quality patches. His contributions https://codereview.qt-project.org/#/q/owner:aha_1980%2540gmx.de,n,z His reviews https://codereview.qt-project.org/#/q/reviewer:aha_1980%2540gmx.de+-owner:aha_1980%2540gmx.de,n,z - Orgad ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Requesting a break in behavior in QML Text element
Den 30-01-2015 kl. 08:51 skrev Mathias Hasselmann: Am 30.01.2015 um 08:12 schrieb Bo Thorsen: Den 29-01-2015 kl. 23:24 skrev Robin Burchell: Hi, Rationale: Text.AutoFormat is a terrible misfeature in almost every case out there. [...] I agree that it would be better to set plain text as the default. In most cases it's what there is in the Text elements anyway. This is at least the case for most applications I have come across. But we can't do this before 6.0. It's a clear API change that will affect every single QML application with rich text in Text elements, where they don't explicitly set the format. And why would anyone set it if they accept rich text? AutoFormat is superior to plain text in that it can accept plain text as well. We would not accept such a change for QWidget based classes, so we can't accept it for QML elements either. Sorry, but that's nonsense. With QML we can as we have versioned import statements. They are made exactly for cases like this, incompatible API changes: If the proposed change only gets implemented for import QtQuick 2.5 all existing applications will keep running as they'll import QtQuick 2.4 at maximum. You are right that this is a possibility. But it's not without cost to do this. It adds complexity for Qt developers to keep multiple versions alive and weird bugs for our users. You say it's easy for developers to upgrade to a new version and then so a quick search and replace. This is only correct if you assume that developers know they have to do this. I really don't like forcing people to have to go through a list of things that must be done when upgrading from one minor QML version to another. IMHO that's an abuse of the concept. If this was a big problem that should be fixed, sure. But I tried to argue why it's not as big a problem as the OP said. I completely disagree that having the versioning gives the right to change all kinds of details. Bo. -- Viking Software Qt and C++ developers for hire http://www.vikingsoft.eu ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] New Qt 4.8.7 snapshot build is available
On Wed, Jan 14, 2015 at 12:34 PM, Salovaara Akseli akseli.salova...@theqtcompany.com wrote: Hi, 4.8.7-snapshot-2015-01-12-2-all-changes file uploaded next to installers ( http://download.qt.io/snapshots/qt/4.8/4.8.7/2015-01-12-2/4.8.7-snapshot-2015-01-12-2-all-changes ) to substitute actual change log file inside packages. 4.8.7-snapshot-2015-01-12-2-changes file published yesterday describes delta to previous snapshot. Similar changes files will be uploaded for the next snapshots. Change log file inside packages will be updated closer to actual release. Br, Akseli -Original Message- From: development-bounces+akseli.salovaara=theqtcompany.com@qt- project.org [mailto:development- bounces+akseli.salovaara=theqtcompany@qt-project.org] On Behalf Of Calogero Mauceri Sent: 13. tammikuuta 2015 17:09 To: development@qt-project.org Subject: Re: [Development] New Qt 4.8.7 snapshot build is available Hi, would it be possible to have a full changelog for this snapshot. The changelog file inside the pachage is empty. Thanks, Calogero Il 1/13/2015 4:04 PM, Salovaara Akseli ha scritto: Hi, New Qt 4.8.7 snapshot build is available http://download.qt.io/snapshots/qt/4.8/4.8.7/2015-01-12-2/ Snapshot is built against 50223ce5eebfdff01a88474f0589259137997458 Introduce Windows version 10. Changes compared to previous build: 50223ce5eebfdff01a88474f0589259137997458 Introduce Windows version 10. 6f55f3dbbb2cdae33a8b0d00b7bf2ada7fe79a04 Fix empty arrays in QML 1 18c5ff04103eadcb532d03d526714385943295ab Windows: Fix OS version determination for Windows = 8 8d831f5f444802879ae416bd110184d5a6cf1b26 QDateTime: Fix time format in doc 48194c74d3e2d2316fa4c57cf8b2e6687d8d6416 Fix compilation with QDND_DEBUG. 6f83ee60cf616731fb37d7a4357fc264fc167b2e Add Hebrew translation for Qt Linguist 25d972e12eda9dadf212d24af8d8f524572bdbfa Check world matrix is true when seeing if transformations are supported 62323e8d1b16167662c85e412d35804418593cc6 QIdentityProxyModel: remove slow bounds-checking, for more performance 87b82fb345a3384243da50240dab93589d072d7e Autotest: Setting tst_qaudiooutput and tst_qsound as insignificant Please test these snapshots, report possible regressions to bugreports.qt.io and send email about that (with bug id) to releas...@qt-project.org. Br, Akseli -- Akseli Salovaara The Qt Company ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development Hi, I've just hit this bug: https://bugreports.qt.io/browse/QTBUG-13776 in Qt 4.8.x which is fixed in 5.0 via this patch: https://codereview.qt-project.org/#/c/41984/ Could that patch be backported to 4.8.7? My work environment requires 4.8.x. I've hit this issue when porting the work project from vcxproj to pro files (which would then be used to generate vcxproj files). The generated vcxproj files work just fine, but manually running nmake debug (or install) makes this issue pop up. Best regards, Mark ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
