Re: [Interest] Qt 6.2 vs. Qt 5.15 – The Feature Parity Comparison – QtPDF
Hi, On Fri, Sep 03, 2021 at 09:52:04AM +0200, Heiko Gerdau wrote: > Our main usecase is the quick display of stored external (and selfmade) > PDF-documents without the need to start an external application. Is that so > uncommon? FWIW if simple displaying of PDFs is all you need, you can also use a QWebEngineView and open the PDF in it - it will end up being displayed in Chromium's integrated PDFium, on which Qt PDF is based on as well. Florian -- m...@the-compiler.org | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ signature.asc Description: PGP signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] L Word
Hey everyone, On Thu, Apr 29, 2021 at 12:13:13PM +0300, coroberti wrote: > Dear Guiseppe, > You were very helpful for the list members and personally to me. > The list will deteriorate without you. > > Sincerely hope that the moderator will start to function and to do something. > > Note, that for Roland it's a pure business - spread links and sell > books, support, perhaps projects etc. > This is what is expected to be stopped by moderation. > > Hope, you will reconsider dropping the list. Thanks. I've been quiet on this so far, but I can only echo this sentiment. The signal-to-noise ratio on this list is abysmal since Roland showed up with his rants - by not banning him, list admins here allow an otherwise well-working community medium to be destroyed. I'm sure many people who've made significant useful contributions to this mailinglist have already left, and more will follow if nothing gets done about this. If you allow unhealthy community members to continue with their behaviour, over time, the healthy ones will leave. That's not something admins on this list should be okay with. Florian -- m...@the-compiler.org | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ signature.asc Description: PGP signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Mixing Commercial and Open Source license for different projects
Hey, On Mon, Mar 15, 2021 at 04:16:53PM +0100, James Maxwell wrote: > If I have a commercial Qt license, can I still develop for projects > which are going to be released under LGPL where also other people > don't have a Qt license (of course assuming we only use LGPL Qt and > nothing of the commercial only parts). > > I am afraid of the following: "(ii) use Licensed Software for creation of > any software created with or incorporating Open Source Qt" > what does licensed software mean? If I have Qt commercial, do I always use > Qt under commercial license and thus cannot create any software using open > source qt? The license text has a definition of "Licensed Software". Most notably, "Licensed Software does not include [...] Open Source Qt.". FWIW the licensing FAQ[1] says: Mixing Qt commercial licenses with Qt open-source licenses *in one project/product* is not permitted. (emphasis mine), and in the earlier discussion here[2], Tuukka Turunen said: For completely independent projects/products this is fine. Note that these really should not be same or in practice the same - or in any way depending, relating, using etc each other as defined in the license agreement. That all being said, I'm not a lawyer, and I'm not associated with The Qt Company in any way. Florian [1] https://www.qt.io/faq/2.7.-can-some-developers-in-our-team-working-on-the-same-project-use-open-source-version-of-qt-and-some-developers-use-commercial-version-of-qt [2] https://lists.qt-project.org/pipermail/interest/2020-March/034786.html -- m...@the-compiler.org | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ signature.asc Description: PGP signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Qt WebEngine 5.15.3 tag
Hey Tuukaa, On Tue, Mar 09, 2021 at 09:24:23PM +, Tuukka Turunen wrote: > I do understand the desire to have a supported / tagged release of QWE > and it is possible that it might even work quite well on an earlier > release of Qt. However, we are testing it in conjunction with the > other changes of a new patch level release and do not want to give a > guarantee that new releases of QWE would always work with earlier > releases of other modules. I see, this is indeed something I hadn't considered. However, your documentation indicates that this is officially supported: https://doc.qt.io/qt-5/qtwebengine-platform-notes.html#using-earlier-qt-versions-to-build-qt-webengine "Building Qt WebEngine with earlier Qt versions (down to the last LTS version) is supported. It means that Qt WebEngine 5.15 can be built with Qt 5.12.x, Qt 5.14.x, and Qt 5.15." (Sure, it says "can be built" and not "was tested" or "actually works", though that's kind of implied there) > Tagging a release would give such indication. Does it, though? Only because a 5.15.3 tag exists I don't think it's implied that it's officially supported to combine 5.15.3 and 5.15.2 tags. If the policy is "only matching patch releases are officially compatible" or "only whatever is integrated in qt5.git is guaranteed to be compatible" that's fine (except that it's contrary to the docs above), but then a new 5.15.3 tag doesn't change anything about that. > What would be a good way forward (other that testing each new QWE > version to work on Qt 5.15.2)? I don't see how pushing a tag would do any harm, or give any indication of a stronger "guarantee" than what already exists. Florian -- m...@the-compiler.org | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ signature.asc Description: PGP signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Qt WebEngine 5.15.3 tag
On Tue, Mar 09, 2021 at 06:37:35PM +0100, Benjamin TERRIER wrote: > I am pretty sure that Linux distros which have Qt 5.15 would be interested > in upgrading their Qt WebEngine to 5.15.3+ They can - Gentoo did even before the release, Archlinux did after I asked them to do so and convinced them it's not an accident that no tag exists for it (can't blame them, like I said, it's bizarre). But other Linux package maintainers might not even notice or know a new release is out (which I suspect is TQtC's aim here - keep in mind, QtWebEngine is probably only still public because the LGPL enforces that, apparently the people in charge of those decisions don't care about the involved serious security bugs much...). A dangerous and unethical game to play, even more so when considering that pushing a git tag is zero effort and the change file already was written... Florian -- m...@the-compiler.org | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ signature.asc Description: PGP signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Qt WebEngine 5.15.3 tag
On Tue, Mar 09, 2021 at 10:41:51AM +0100, Benjamin TERRIER wrote: > I would not mind if it was just a matter of tag, but the fact that the > change file for 5.15.3 (changes-5.15.3) is not present on the 5.15.3 branch > in the public repo does not help making this branch trustworthy. That's no accident FWIW, see the discussions here: https://codereview.qt-project.org/c/qt/qtwebengine/+/335435 https://codereview.qt-project.org/c/qt/qtwebengine/+/337355 Here's the changes file before the change adding it was abandoned: https://codereview.qt-project.org/c/qt/qtwebengine/+/335435/6/dist/changes-5.15.3 It's... bizarre. Even more so for a highly security-relevant piece of Qt (and a release which fixes 29 CVEs plus 9+ other security bugs). You'd think that The Qt Company would have an interest in keeping their users secure, paying or not. Perhaps someone should take the time to go through those CVEs and make sure that Qt is marked as a known affected product with no public fix released ;) Excuse the snark - I fully respect that TQtC needs to pay its employees after all, but honestly, this is negligent even from a business perspective. I don't care much about this change for qtbase or anything else (where security bugs aren't that prevalent, and where projects can migrate to Qt 6), but for QtWebEngine with no upgrade path available as of now, this is a horrible idea no matter how you look at it. Florian -- m...@the-compiler.org | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ signature.asc Description: PGP signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Qt 6 Ubuntu package
Hey, On Thu, Jan 28, 2021 at 12:08:44PM +0530, Nibedit Dey wrote: > I am looking for a way to install Qt6 without downloading the > *qt-unified-linux-x86-4.0.1-online.run* file. > Is there a Qt 6 Ubuntu package like the one for Qt 5? e.g.:- *sudo apt-get > install qt5-default* Ubuntu's packages are mostly inherited from Debian, where the Qt package maintainers stepped down before the Qt 6 release because of a lack of time: https://perezmeyer.blogspot.com/2020/08/stepping-down-as-qt-6-maintainers.html https://www.phoronix.com/scan.php?page=news_item=Debian-Needs-Qt6-Maintainers Also see: https://alioth-lists.debian.net/pipermail/pkg-kde-talk/2021-January/003236.html Given that everyone there is focusing on the next Debian Stable (Bullseye) which will ship Qt 5.15.2, I doubt there was work on Qt 6 so far. Also note that pretty much nothing is ported to Qt 6 at this point, because many modules are still missing in Qt 6.0 (and probably 6.1 too). Thus, you'll probably have to use the online installer (or an alternative such as aqtinstall). Florian -- m...@the-compiler.org | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ signature.asc Description: PGP signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] QPA display system query ?
Hey, On Mon, Jan 18, 2021 at 03:33:58PM -0800, Nicholas Yue wrote: > Is there some command line query I can make to determine the QPA display > system that is being used? For example, running that command on e.g. an > Ubuntu box may return something like *xcb* It sounds like QGuiApplication::platformName() would give you that? Florian -- m...@the-compiler.org | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ signature.asc Description: PGP signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Will a Qt 5.x release support macOS 11?
On Wed, Dec 09, 2020 at 09:19:16AM +0100, Allan Sandfeld Jensen wrote: > On Mittwoch, 9. Dezember 2020 08:07:45 CET Ben Haller via Interest wrote: > > Hi all. Just wondering whether there is any plan for any Qt 5.x release to > > support macOS 11. At present, Qt 5.15 supports only through macOS 10.15 > > (https://doc.qt.io/qt-5/macos.html#supported-versions), as far as I can > > tell, and my app built on macOS 10.15 apparently does not run properly on > > macOS 11 (so my users inform me). Since it looks like it will be a little > > while before a Qt 6 release is really solid (I just saw on the list that > > the first LTS release of Qt 6 is expected in September 2021, almost a year > > from now), it would be really nice if macOS 11 were added to the list of > > supported releases for 5.15. Any chance of that? I have users who are > > already on macOS 11 now; I’d like to have a better story for them. Thanks > > for any info! > > > I can't say anything for the company at this point, but at least report any > issues you encounter in JIRA. > > Builds so far seems to work, though the build process does warn about > building > for an unsupported version. FWIW no issues with my application using QtWebEngine with Qt 5.15.2, from what I can tell. People might need to set QT_MAC_WANTS_LAYER=1 though - for me, not doing that caused the application to hang when opening the (QtWebEngine default) context menu: https://bugreports.qt.io/browse/QTBUG-87014 The respective fix didn't make it to 5.15.2: https://codereview.qt-project.org/c/qt/qtbase/+/38 Florian -- m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ signature.asc Description: PGP signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Qt 6.0.0 released
On Tue, Dec 08, 2020 at 03:19:51PM +, Nuno Santos wrote: > How can install this. It does not show up in Maintenance Tool. Shows up just fine for me FWIW. Florian -- m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ signature.asc Description: PGP signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Qt5 font size issue with fontconfig
On Thu, Nov 12, 2020 at 10:01:23AM +, Hamish Moffatt wrote: > > On 12/11/20 8:47 pm, Florian Bruhin wrote: > > On Thu, Nov 12, 2020 at 12:37:33AM +, Hamish Moffatt wrote: > > > On 12/11/20 2:46 am, Thiago Macieira wrote: > > > > NEVER calculate font sizes in pixels. Your design is wrong. Delete this > > > > function and use point sizes throughout. > > > Too bad the Qt Widget stylesheet function only supports point sizes for > > > fonts. > > Not sure what makes you think so: > > https://doc.qt.io/qt-5/stylesheet-reference.html#font-prop > > "The font size. In this version of Qt, only pt and px metrics are > > supported." > > > What I meant was ONLY font sizes can be specified in points. Other > dimensions (max-height for example) can't be specified in pt. Ah, right, sorry :) You can (at least according to the docs) specify other sizes in em or ex (i.e. relative to the font size) though. Florian -- m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ signature.asc Description: PGP signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Qt5 font size issue with fontconfig
On Thu, Nov 12, 2020 at 12:37:33AM +, Hamish Moffatt wrote: > On 12/11/20 2:46 am, Thiago Macieira wrote: > > > > NEVER calculate font sizes in pixels. Your design is wrong. Delete this > > function and use point sizes throughout. > > Too bad the Qt Widget stylesheet function only supports point sizes for > fonts. Not sure what makes you think so: https://doc.qt.io/qt-5/stylesheet-reference.html#font-prop "The font size. In this version of Qt, only pt and px metrics are supported." Florian -- m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ signature.asc Description: PGP signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] [Development] Windows 7 support will be dropped in Qt 6
On Thu, Jun 11, 2020 at 06:02:53PM +, Jérôme Godbout wrote: > or Windows 11 by the time Qt 6 and you get your application ready "Microsoft > will release Windows 11 on July 29, 2020, and will be available to the > general public." Do you have a source for that? I'm assuming it's https://www.window11updates.com/ which is a hoax. Florian -- m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ signature.asc Description: PGP signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Qt 5.15 for Linux/X11 : "-qt-xcb" no longer supported?
On Fri, May 22, 2020 at 06:56:32PM -0700, Thiago Macieira wrote:
> On Friday, 22 May 2020 07:54:03 PDT Florian Bruhin wrote:
> > I'm talking about running Qt's binary releases, not building from sources.
>
> Then take the list of "not found" and pass it through your package manager
> installer.
>
> On an RPM-based distro:
>
> ldd binary | awk '/not found/ { print $1 "()(64bit)" | xargs $PM install
>
> where $PM is zypper or dnf or yum.
That works. However, initially you'll be met with an error message like this:
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even
though it was found.
This application failed to start because no Qt platform plugin could be
initialized. Reinstalling the application may fix this problem.
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl,
offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl,
wayland-xcomposite-glx, xcb.
There's nothing in there that tells me:
- What exactly happened in a clear way (what does the 'in ""' mean?!)
- That there's some dependency missing
- That I need to go look at /usr/lib/qt/plugins/platforms/libqxcb.so
Especially on CI where this is likely to happen, it can be painful to find out.
Setting QT_DEBUG_PLUGINS=1 usually helps:
[lots of output]
Cannot load library .../Qt/plugins/platforms/libqxcb.so:
(libxcb-randr.so.0: cannot open shared object file: No such file or
directory)
But again, that's something you need to know about - if you're new to Qt and
just trying to use the binaries on CI (e.g. via PyQt), it doesn't seem to be
clear to me at all how to get started, and the vague error message doesn't
help. Thus why I think this should be documented somewhere (and/or the error
message improved, though I don't know how difficult it is to get a proper error
message when something like this happens).
Florian
--
m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org
https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
I love long mails! | https://email.is-not-s.ms/
signature.asc
Description: PGP signature
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
Re: [Interest] Qt 5.15 for Linux/X11 : "-qt-xcb" no longer supported?
On Fri, May 22, 2020 at 04:43:51PM +0200, Shawn Rutledge wrote: > > > > On 2020 May 22, at 16:25, Florian Bruhin wrote: > > > > Hey, > > > > On Wed, May 13, 2020 at 05:48:09PM +, Kai Köhne wrote: > >> And indeed the linux documentation wasn't updated yet :/ > >> > >> https://codereview.qt-project.org/c/qt/qtdoc/+/300239 > > > > Is there some good place to start documenting what packages are needed for > > the > > XCB platform plugin? It took me a while to find out this is what I needed to > > install on Ubuntu (and I'm guessing Debian) so that my tests worked again on > > Travis CI: > > > > - libxkbcommon-x11-0 (since 5.12 already) > > - libxcb-icccm4 > > - libxcb-image0 > > - libxcb-keysyms1 > > - libxcb-randr0 > > - libxcb-render-util0 > > - libxcb-xinerama0 > > https://wiki.qt.io/Building_Qt_5_from_Git#Linux.2FX11 I'm talking about running Qt's binary releases, not building from sources. Florian -- m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ signature.asc Description: PGP signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Qt 5.15 for Linux/X11 : "-qt-xcb" no longer supported?
Hey, On Wed, May 13, 2020 at 05:48:09PM +, Kai Köhne wrote: > And indeed the linux documentation wasn't updated yet :/ > > https://codereview.qt-project.org/c/qt/qtdoc/+/300239 Is there some good place to start documenting what packages are needed for the XCB platform plugin? It took me a while to find out this is what I needed to install on Ubuntu (and I'm guessing Debian) so that my tests worked again on Travis CI: - libxkbcommon-x11-0 (since 5.12 already) - libxcb-icccm4 - libxcb-image0 - libxcb-keysyms1 - libxcb-randr0 - libxcb-render-util0 - libxcb-xinerama0 Florian -- m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ signature.asc Description: PGP signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Qt 5.12.x LTS
On Tue, May 19, 2020 at 12:38:53PM +0530, Ramakanth Kesireddy wrote: > Apart from CVE-2020-0569 and CVE-2020-0570, could you please let me know > other security fixes that donot have associated CVE or any other CVEs > backported to Qt 5.12.8? You might want to check the change files for 5.12.8: https://wiki.qt.io/Qt_5.12.8_Change_Files Florian -- m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ signature.asc Description: PGP signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] unexpected result from QString::compare
On Fri, May 08, 2020 at 08:51:19AM +, Hamish Moffatt wrote: > On 8/5/20 5:13 pm, Fabrice Mousset | GEOCEPT GmbH wrote: > > Perhaps you should use QString::localeAwareCompare() ? > > > Thanks, I didn't know about that. Maybe the QString::compare() documentation > could mention it... From https://doc.qt.io/qt-5/qstring.html#compare : Case sensitive comparison is based exclusively on the numeric Unicode values of the characters and is very fast, but is not what a human would expect. Consider sorting user-visible strings with localeAwareCompare(). Florian -- m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ signature.asc Description: PGP signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] QVariant compare operator
On Mon, Apr 20, 2020 at 09:50:06AM -0600, Thiago Macieira wrote: > On Monday, 20 April 2020 03:28:48 MDT Florian Bruhin wrote: > > FWIW that's the choice Python had taken with Python 2 (ordering different > > types by their type name). It was widely regarded as a bad decision and > > replaced by a TypeError exception in Python 3. > > Interesting. Do you have more information on why it is regarded a bad > decision? A PEP, hopefully? I have to admit my "widely regarded as" was perhaps a bit too anecdotal. It doesn't look like a PEP exists for this, which seems quite surprising. There was some discussion via email, but it's quite a mess to read, unfortunately: https://mail.python.org/pipermail/python-dev/2004-June/thread.html (the "Comparing heterogeneous types" threads) https://mail.python.org/archives/search?q=Comparing+heterogeneous+types=1=python-dev%40python.org=date-asc (same content, more modern archive webinterface) Florian -- m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ signature.asc Description: PGP signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] QVariant compare operator
On Sun, Apr 19, 2020 at 12:42:16PM -0300, Thiago Macieira wrote: > On Sunday, 19 April 2020 09:39:40 -03 André Pönitz wrote: > > > What about non-integral types? > > > > They are compared by typeName(). So any QChar would be less-than any > > QRegularExpression. > > We can order by type, but I don't think we should. But that's a choice. FWIW that's the choice Python had taken with Python 2 (ordering different types by their type name). It was widely regarded as a bad decision and replaced by a TypeError exception in Python 3. Florian -- m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ signature.asc Description: PGP signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
[Interest] Qt and Open Source
Hi, (Note: Parts of this mail are similar to a mail I sent to the kde-community list a couple of minutes ago, but the majority of it is different) As some people here might already know, the KDE Free Qt foundation made a very concerning announcement yesterday: https://mail.kde.org/pipermail/kde-community/2020q2/006098.html In the announcement, one of the KDE representatives in that foundation claims that: [...] But last week, the company suddenly informed both the KDE e.V. board and the KDE Free QT Foundation that the economic outlook caused by the Corona virus puts more pressure on them to increase short-term revenue. As a result, they are thinking about restricting ALL Qt releases to paid license holders for the first 12 months. They are aware that this would mean the end of contributions via Open Governance in practice. (I encourage you to read the full announcement for some more context). As the maintainer of a web browser[1] using QtWebEngine, I find this deeply concerning. A year delay in security updates would be unacceptable for my project, so, realistically I'd need to take a decision between: a) Switching to something different like Chromium Embedded Framework, which means months of work on top of an ever-growing backlog; b) Buying a Qt Startup License with all that it entails (probably including qutebrowser not being a proper FOSS project anymore), which is pretty much not an option given the licensing terms; c) Throwing the towel after 6.5 years (which also means losing a donation-funded part-time job, not to mention abandoning a project and community which is of immense importance to me personally). Needless to say, that wouldn't be a decision I want to make, and this announcement from KDE really wasn't an easy thing to digest. Of course that announcement made its way to sites Phoronix and Reddit, and I'm sure it'll be picked up by more people soon. Yet, I haven't seen any prior public discussions about this (e.g. on this list). Today, The Qt Company released a quick statement: https://www.qt.io/blog/qt-and-open-source There have been discussions on various internet forums about the future of Qt open source in the last two days. The contents do not reflect the views or plans of The Qt Company. The Qt Company is proud to be committed to its customers, open source, and the Qt governance model. Unless I'm missing something, there aren't many possible interpretations of what's going on. 1) There was some kind of misunderstanding between KDE and Qt, and those statements never were intended they way that KDE cited them. I try to always assume good faith, but after more and more moves against the open-source side of Qt recently, I place a lot more trust in statements coming from KDE rather than those coming from TQtC... 2) Qt tried to bluff in order to force KDE to change some other provision of their contract, possibly even using the current pandemic as an excuse to do so. I find this repulsive, but unfortunately, it seems the most likely explanation, especially given this part of KDEs announcement: "The Qt Company says that they are willing to reconsider the approach only if we offer them concessions in other areas. I am reminded, however, of the situation half a year ago. We had discussed an approach for contract updates, which they suddenly threw away by restricting LTS releases of Qt instead." 3) Qt is just trying to do damage control and still intends to follow through with those changes. Like I said, I always try to assume good faith, but the lack of transparency on TQtC's side about this topic really doesn't help. I completely understand that the Qt Company needs to pay its bills and developers, and that the Qt Project (and FOSS community) benefits a lot from that. I understand it's a very difficult balance to strike, and I can see how some of the recent changes could've been necessary from a business perspective. This, however, would kill Qt as we all know it. I'm still hoping there's a way out of this with as little damage as possible for everyone. But for that to happen, more transparency about what's going on from TQtC's side is needed. I'd very much appreciate a more detailed statement on what's gone wrong here. Finally: I know I'm starting a public discussion about this topic on a public mailinglist. I know some readers will have very strong opinions agains the Qt Company after the announcement, and I can understand where you're coming from. But before throwing expletives at people, please reconsider and maybe take a break first (I'd suggest a walk, but alas, that's difficult right now). Let's please keep this a civilized and constructive discussion despite the circumstances. Florian -- m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! |
Re: [Interest] QtWebkit error while building Qt5.12.7 sources
On Thu, Feb 20, 2020 at 09:02:13AM +1000, Nyall Dawson wrote: > An example: qtwebkit allows rendering of HTML content direct to a > QPainter surface, keeping text as text objects and other components as > vectors. This isn't possible in the webengine classes, at best you can > render a rasterized image of a page to a painter. Without this > capability it's impossible in Qt to render HTML content to SVG or PDF > files without loss of quality. There's QWebEnginePage::printToPdf() which does keep text as text and vectors as vectors. Florian -- m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ signature.asc Description: PGP signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Why doesn't my model filter update?
On Tue, Feb 18, 2020 at 04:49:57PM -0500, Matthew Woehlke wrote:
> On 18/02/2020 16.31, Konstantin Shegunov wrote:
> > On Tue, Feb 18, 2020 at 11:20 PM Matthew Woehlke wrote:
> >> I wonder if anyone else can spot it? ;-)
> >
> > Without knowing anything about the code at all, my best guess based on a
> > very quick glance would be the range for the dataChanged is wrong.
>
> Okay, I'll give you half a cookie, since I can't really say much more
> without giving it away. (Incidentally, if I hadn't already figured it
> out, you comment probably would have helped!)
>
> Here's the broken code:
>
> if (auto const rows = this->rowCount())
> {
> auto const& first = this->index(0, 0);
> auto const& last = this->index(rows, 0);
>
> emit this->dataChanged(first, last, {MyFilterRole});
> }
>
> It fell victim to one of the two hard problems of programming (as
> enumerated by Leon Bambrick¹). To wit, `last` is an invalid index, which
> trips one of the sanity checks in QSortFilterProxyModel's internal logic.
>
> If you can't tell *why* `last` is invalid, well, keep looking until you
> can ;-). All the information you need to spot the problem is in the
> above snippet, and it's *obvious* once you see it. (Note: assume that
> the class otherwise behaves in a correct fashion.)
>
> (¹ https://www.goodreads.com/quotes/7443069)
I'd recommend running QAbstractItemModelTester (or ideally, including it in
your testsuite) over custom models:
https://doc.qt.io/qt-5/qabstractitemmodeltester.html
It'd likely have caught an issue like this (though I haven't checked).
Florian
--
m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org
https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
I love long mails! | https://email.is-not-s.ms/
signature.asc
Description: PGP signature
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
Re: [Interest] equivalent of python glob
On Mon, Aug 26, 2019 at 11:59:00PM +, Hamish Moffatt wrote: > I think it's a shame there isn't something simpler built in to C++ or Qt > though. There's std::filesystem::path::append in C++17: https://en.cppreference.com/w/cpp/filesystem/path/append Florian -- https://www.qutebrowser.org | m...@the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ signature.asc Description: PGP signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] [PySide] PySide2 installer for windows?
Hi, On Mon, May 20, 2019 at 12:07:42PM +1200, Frank Rueter | OHUfx wrote: > So the only way out of this is update my code to Python3? You might want to consider doing that anyways, if you haven't yet. Python 2 is EOL (including security fixes) in about half a year: https://pythonclock.org/ Many projects have pledged to drop support for it by then: https://python3statement.org/ There are various good porting guides available: https://docs.python.org/3/howto/pyporting.html http://python3porting.com/ https://portingguide.readthedocs.io/ Florian -- https://www.qutebrowser.org | m...@the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ signature.asc Description: PGP signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Backporting bugs to Qt 5.6
Hey, On Fri, Sep 21, 2018 at 09:49:19AM +0200, Danny Smit wrote: > I'm running into two (old) Qt bugs using the latest Debian, with still > uses the LTS Qt 5.6. What do you mean with "the latest Debian"? According to [1], Debian stable packages Qt 5.7.1 (which is not an LTS), and testing/unstable both ship 5.11.1. [1] https://packages.debian.org/search?keywords=libqt5core5a=names=all=all > And is likely that my request for such backports will even get accepted? See [2]. The Qt 5.6 release was in March 2016, so it's in the "very strict" phase since March 2018. As such, only critical things like security issues are still fixed there. [2] http://code.qt.io/cgit/meta/quips.git/tree/quip-0005.rst Florian -- https://www.qutebrowser.org | m...@the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ signature.asc Description: PGP signature ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] How do I get the most robust version of 5.10
On Thu, Apr 12, 2018 at 02:32:43PM -0400, william.croc...@analog.com wrote: > > > > > > > It immediately failed one of my regression tests. > > > You should have known there was an issue because I here it has been fixed > > > in > > > 5.11 > > > > Of course there are problems. Do you want us to delete every old release > > because we've fixed bugs? We already have fixes for bugs post 5.9.5, which > > was > > released today. Should we delete it too? > > > > Bugs will be fixed in the next release. > > > > > Fortunately I did not spend too much time blaming my code. > > > I submitted a bug report and was offered 3 patches which fixed the > > > problem. > > > > > > I think leaving that prominent, dangling version with known > > > issues is irresponsible. > > > > Ok, we'll delete all releases. Please build only from Git, from the dev > > branch. It's the only one that has all fixes. > > > > I view the most recent branch (5.11 in this case) as your bold move into new > features and, as long as that branch is sub-versioned (5.11.x), > the dust has not settled. > > It appeared that the dust had settled on 5.10 and all known bugs, especially > those introduced in otherwise mature code, like QAbstractItemView, would > have been resolved. > > So, I can't use 5.11 because the dust has not settled and > now I can't use any previous version because even the most basic > of classes may have known bugs. > > That is my conundrum. Like other people mentioned before, it sounds like LTS branches (currently 5.9) are the right fit for you. Those get bugfixes for a long time, without any changes which have a bigger potential for breaking something (so there's no dust to settle). They are also supported for a much longer time than a regular release (3 years, but getting stricter even with non-critical bugfixes after some time). Florian -- https://www.qutebrowser.org | m...@the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ signature.asc Description: PGP signature ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] qutebrowser v1.0.0 released!
Hey, I'm delighted to announce that I just released qutebrowser v1.0.0! qutebrowser is a keyboard driven browser with a vim-like, minimalistic interface. It's written using PyQt and cross-platform. This release comes with many big breaking changes such as the new config and QtWebEngine by default. See the changelog for details. Florian Major changes ~ - Dependency changes: * Support for legacy QtWebKit (before 5.212 which is distributed independently from Qt[1] is dropped. * Support for Python 3.4 is dropped. * Support for Qt before 5.7.1 and PyQt before 5.7 is dropped. * New dependency on the QtSql module and Qt sqlite support. * New dependency on the attrs[2] project (packaged as `python-attr` in some distributions). * The depedency on PyOpenGL (when using QtWebEngine) got removed. Note that PyQt5.QtOpenGL is still a dependency. * PyQt5.QtOpenGL is now always required, even with QtWebKit. - The QtWebEngine backend is now used by default. Note this means that QtWebEngine now should be a required dependency, and QtWebKit (if new enough) should be changed to an optional dependency. - Completely rewritten configuration system which ignores the old config file. See qute://help/configuring.html for details. - Various documentation files got moved to the doc/ subfolder; `qutebrowser.desktop` got moved to misc/. - `:set` now doesn't support toggling/cycling values anymore, that functionality got moved to `:config-cycle`. - New completion engine based on sqlite, which allows to complete the entire browsing history. The default for `completion.web_history_max_items` got changed to `-1` (unlimited). If the completion is too slow on your machine, try setting it to a few 1000 items. [1] https://github.com/annulen/webkit/wiki [2] http://www.attrs.org/ Added ~ - QtWebEngine: Spell checking support, see the `spellcheck.languages` setting. - New `qt.args` setting to pass additional arguments to Qt/Chromium. - New `backend` setting to select the backend to use. Together with the previous setting, this should make most wrapper scripts unnecessary. - qutebrowser can now be set as the default browser on macOS. - New config commands: * `:config-cycle` to cycle an option between multiple values. * `:config-unset` to remove a configured option. * `:config-clear` to remove all configured options. * `:config-source` to (re-)read a `config.py` file. * `:config-edit` to open the `config.py` file in an editor. * `:config-write-py` to write a `config.py` template file. - New `:version` command which opens `qute://version`. - New back/forward indicator in the statusbar. - New `bindings.key_mappings` setting to map keys to other keys. - QtWebEngine: Support for proxy authentication. Changed ~~~ - Using `:download` now uses the page's title as filename. - Using `:back` or `:forward` with a count now skips intermediate pages. - When there are multiple messages shown, the timeout is increased. - `:search` now only clears the search if one was displayed before, so pressing `` doesn't un-focus inputs anymore. - Pinned tabs now adjust to their text's width, so the `tabs.width.pinned` setting got removed. - `:set-cmd-text` now has a `--run-on-count` argument to run the underlying command directly if a count was given. - `:scroll-perc` got renamed to `:scroll-to-perc`. Removed ~~~ - Migrating QtWebEngine data written by versions before 2016-11-15 (before v0.9.0) is now not supported anymore. - Upgrading qutebrowser with a version older than v0.4.0 still running now won't work properly anymore. - The `--harfbuzz` and `--relaxed-config` commandline arguments got dropped. Fixes ~ - Exiting fullscreen via `:fullscreen` or buttons on a page now restores the correct previous window state (maximized/fullscreen). - When `input.insert_mode.auto_load` is set, background tabs now don't enter insert mode anymore. - The keybinding help widget now works correctly when using keybindings with a count. - The `window.hide_wayland_decoration` setting now works correctly again. -- https://www.qutebrowser.org | m...@the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ signature.asc Description: PGP signature ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] QWebEngine block domain
On Tue, Jun 13, 2017 at 09:41:17PM -0700, Kevin Mcintyre wrote: > Is it possible to block requests, like for instance to a specific domain. > > Is see QWebEngineUrlRequestInterceptor but this is only informational. Only informational how? There's a QWebEngineUrlRequestInfo::block() which seems to do exactly what you want. Florian -- https://www.qutebrowser.org | m...@the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ signature.asc Description: PGP signature ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] Crowdfunding campaign for new config system in qutebrowser
Hi, I'm the main developer of qutebrowser, a keyboard-focused vim-like web browser, built using PyQt: https://www.qutebrowser.org/ Like last year, I'd love to spend my summer holidays working full-time on qutebrowser again! This is why I started another crowdfunding - this time with the goal of ripping out some of its oldest code (the configuration) and replacing it with something much more sane - something which has been planned for a long time already. You can find more details here: https://www.kickstarter.com/projects/the-compiler/qutebrowser-v10-with-per-domain-settings?ref=e3nfby Florian -- http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc I love long mails! | http://email.is-not-s.ms/ signature.asc Description: PGP signature ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] Crowdfunding campaign for QtWebEngine support in qutebrowser, a vim-like browser
Hi! (first of all, I hope this kind of thing is okay on this list - I decided to go for it after I saw some release announcements too. Please let me know if not, and sorry!) I'm the main developer of qutebrowser, a keyboard-focused vim-like web browser built using Qt and Python: http://www.qutebrowser.org/ qutebrowser is currently using QtWebKit - this comes with various stability, performance and security issues. This is why I want to add QtWebEngine support to the project. Since this is a lot more work than I originally hoped when I started 2.5 years ago, I decided to launch a crowdfunding campaign with the goal to work on this full-time for a few weeks. You can find the campaign here: http://igg.me/at/qutebrowser Thanks! Florian -- http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc I love long mails! | http://email.is-not-s.ms/ signature.asc Description: Digital signature ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
