If you need some help with PyQt development, call me up, I'm cheap ;)
PyQt5 Tutorial: Create a Python GUI in 2018
51–60 of 211 posts
Re: PyQt5 Tutorial: Create a Python GUI in 2018
#52Earlier quoted context omitted.
Flexibility to do what, though? I'm genuinely curious: what doesn't Qt offer that a desktop app might need?
I assume learning to build interfaces in Javascript allows you to port that skill to both the desktop environment (via something like Electron) or web environment through a browser.
Re: PyQt5 Tutorial: Create a Python GUI in 2018
#53I've been using wxPython for many years, and it works very well. What are the advantages of PyQT over wxPython? Anyone experienced both 'worlds' in a non-trivial application?
The reason why I chose PyQt over wxPython was the former's support for custom styles. I wrote an article with my thoughts on picking a GUI framework [1], in case you're interested. 1: https://fman.io/blog/picking-technologies-for-a-desktop-app-...
Dumb question time: Is this also usable with QML?
Re: PyQt5 Tutorial: Create a Python GUI in 2018
#54Anybody know if it's easy to reverse engineer or strip parts of the application when deploying PyQt5 apps? Or do you need extra measures to obfuscate the code to protect certain logic?
I've never tried it but given Python's interpreted nature, it is likely pretty easy unless you use an obfuscator. Note that that's true for Java .class files as well. I was really surprised once when I tried to decompile one of my own that I had thought would be safe. You get near-perfect accuracy.
Part of my job used to be the large scale modification and recompilation of Android apps....you'd be amazed how many passwords are floating around in those.
Re: PyQt5 Tutorial: Create a Python GUI in 2018
#55Earlier quoted context omitted.
Flexibility to do what, though? I'm genuinely curious: what doesn't Qt offer that a desktop app might need?
I assume learning to build interfaces in Javascript allows you to port that skill to both the desktop environment (via something like Electron) or web environment through a browser.
In Qt you use the Designer, you need to learn about the layout system if you want to do good UIs, but your GUI is saved in a file and then the c++/python code implements the event handlers and app logic.
Re: PyQt5 Tutorial: Create a Python GUI in 2018
#56Re: PyQt5 Tutorial: Create a Python GUI in 2018
#57That I have to choose between C++ or Python makes it very difficult for many use cases in other languages. What essentially ends up happening is you create the UI in C++ then build a communication/bridge layer with your Go/Rust/JVM/etc app via C and the respective language's FFI features.
Re: PyQt5 Tutorial: Create a Python GUI in 2018
#58Earlier quoted context omitted.
> Why would I want to switch to Qt? Because GTK is awful outside of Linux.
I'd argue GTK is awful inside of Linux because of client-side decorations (removal of the standard title-bar) that you cannot disable, removal of the menu bar, and the mobile/tablet first design (some people do use desktops and I'm not allergic to text).
I'm pretty sure you can. I like them in most cases, though, just wish they'd gone the Windows/MacOS way of slowly intruding/overlapping a bit occasionally instead of reinventing the whole bar.
Re: PyQt5 Tutorial: Create a Python GUI in 2018
#59Anybody know if it's easy to reverse engineer or strip parts of the application when deploying PyQt5 apps? Or do you need extra measures to obfuscate the code to protect certain logic?
I've never tried it but given Python's interpreted nature, it is likely pretty easy unless you use an obfuscator. Note that that's true for Java .class files as well. I was really surprised once when I tried to decompile one of my own that I had thought would be safe. You get near-perfect accuracy.
Here's a resource that may help: https://devguide.python.org/compiler/#introducing-new-byteco...
Re: PyQt5 Tutorial: Create a Python GUI in 2018
#60We 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…
Thank you for not using Electron.