Live data from Hacker News

PyQt5 Tutorial: Create a Python GUI in 2018

build-system.fman.io

71–80 of 211 posts

Re: PyQt5 Tutorial: Create a Python GUI in 2018

#71
post #36

Earlier quoted context omitted.

PySide2 is now out of beta?

It's still just a "technical preview", but I've been using it for a while and didn't have any problems that weren't caused by me not knowing how Qt works. Some of the examples in the documentation are still in C++, but it's pretty easy to translate them to Python since the names are the same. (Sometimes painfully so, e.g PySide2.QtCore.Qt.ScrollBarPolicy.ScrollBarAlwaysOff .)

> Some of the examples in the documentation are still in C++

If you do anything serious with Qt you'll have to read those anyway, I believe even PyQt stopped "translating" the docs to python. It's easy enough anyway, even for people like me with no real experience of C++.

Re: PyQt5 Tutorial: Create a Python GUI in 2018

#73

Earlier quoted context omitted.

Qt qualifies then, at least on Linux.

Qt qualifies on any platform, imo.

Unless you use Qt quick which seems to be the way forward, and what many devs with html/css/js background seem to prefer.

Qt widgets look close to native UIs but the feel isn't always the same, especially when you have to juggle with different platforms (all native widgets differ in subtle ways even when their function is the same).

Re: PyQt5 Tutorial: Create a Python GUI in 2018

#74

We use Qt heavily at Starsky Robotics. We initially used it because it has tight integration with ROS via RQT [1], but I'm pretty impressed with the framework in general. Lots of great tools out of the box, QtCreator is awesome and once you get the right signal/slot model in your head everything is a breeze. Plus getting to prototyping in python is always fast! For our use case, relative speed of the GUI isn't a fact…

What's the memory consumption of pyQT compared to electron apps?

An order of magnitude lower. I see 40Mb on macos right now for a simple app.

Re: PyQt5 Tutorial: Create a Python GUI in 2018

#76

We use Qt heavily at Starsky Robotics. We initially used it because it has tight integration with ROS via RQT [1], but I'm pretty impressed with the framework in general. Lots of great tools out of the box, QtCreator is awesome and once you get the right signal/slot model in your head everything is a breeze. Plus getting to prototyping in python is always fast! For our use case, relative speed of the GUI isn't a fact…

What's the memory consumption of pyQT compared to electron apps?

I can't comment for pyQt. But the regular C++ Qt app I'm tinkering with at the moment uses 11MB private and about 50MB in shared memory for displaying a simple window with some nested widgets and scrollable lists.

Re: PyQt5 Tutorial: Create a Python GUI in 2018

#77
Steve Yegge was a true visionary. In 2004 he predicted the massive popularity of (future) Electron:

> web application programming is gradually going to become the most important client-side programming out there. I think it will mostly obsolete all other client-side toolkits: GTK, Java Swing/SWT, Qt, and of course all the platform-specific ones like Cocoa and Win32/MFC

https://danluu.com/yegge-predictions/

Re: PyQt5 Tutorial: Create a Python GUI in 2018

#78
post #10

Earlier quoted context omitted.

What would you use for an app that needs to look really good and be fast?

Really good? Platform-native APIs.

The original post said

> why are you using Python?

I'm not sure

> Platform-native APIs.

are a replacement for Python?

Re: PyQt5 Tutorial: Create a Python GUI in 2018

#79
post #32

Earlier quoted context omitted.

I was recently surprised by how non-ugly a Python Tkinter app can look with some effort. Take a look at this: https://thonny.org/

that's an interesting definition of "non-ugly". I would hesitate a lot before making an app that looks like this screenshot public.

[deleted]

Re: PyQt5 Tutorial: Create a Python GUI in 2018

#80

Earlier quoted context omitted.

Thank you for not using Electron.

All of our end users are internal, so the main bloat-related problems wouldn't really be an issue at all. Why should we be worried about electron in the future?

The worry is that you have too many developers who don't consider HTML/CSS/JS a proper stack for a "real" engineer and there refuses to learn it.
Post reply on HN