PyQt5 Tutorial: Create a Python GUI in 2018
191–200 of 211 posts
Re: PyQt5 Tutorial: Create a Python GUI in 2018
#192Re: PyQt5 Tutorial: Create a Python GUI in 2018
#193Too bad it's only for Python3 and installing both 2 and 3 is complicated. Would be a good program if it supported python2.
Re: PyQt5 Tutorial: Create a Python GUI in 2018
#194Earlier quoted context omitted.
Looking at a tutorial, it looks like all it does is layout the form for you. That's a shame. Things closer to what the original VB was are sorely missed in modern computing.
Here you go: vTcl -- just like Visual Basic 3.0. Also, you get to use Tcl instead of Visual Basic, so even better ! http://vtcl.sourceforge.net/
Even Visual Basic 3's P-Code interpreter was faster than TCL string based one.
Re: PyQt5 Tutorial: Create a Python GUI in 2018
#195I would kind of expect that "in 2018" we'd be using QML and not QtWidgets?
Re: PyQt5 Tutorial: Create a Python GUI in 2018
#196Earlier quoted context omitted.
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.
for reference, the app I'm working on ( https://ossia.io ), a multiple-hundred-LOC Qt-based DAW with support for many network protocols and which uses most Qt libraries as well as boost uses itself 41 megabytes of RAM (private working set) and 70 megabytes total (working set) with a small document loaded, according to the windows task manager.
Re: PyQt5 Tutorial: Create a Python GUI in 2018
#197Re: PyQt5 Tutorial: Create a Python GUI in 2018
#198I'd like to take this time to introduce a project I have been working on. I'm using it in production currently. https://github.com/qmlnet/qmlnet It is a perfect balance between QML and .NET. The tech stack splits along the perfect line. QML for UI, .NET for business logic. I'd be glad to answer any questions.
Re: PyQt5 Tutorial: Create a Python GUI in 2018
#199The hardest problem in this space is not writing the code, but packaging the app. All the freeze utilities have their quirks which ensure no one solution works for all three OS consistently. Even Dropbox had to rewrite their packaging to ensure maximum system compatibility ( https://news.ycombinator.com/item?id=18067784 )
I created https://build-system.fman.io to help with this exact (general) problem.