Re:PyQt5 Tutorial: Create a Python GUI in 2018
by morenoh149 on Tuesday September 25, 2018 @01:13PM
(#18068276)
What's the memory consumption of pyQT compared to electron apps?
Re:PyQt5 Tutorial: Create a Python GUI in 2018
by denysonique on Tuesday September 25, 2018 @10:04PM
(#18072121)
For a JavaScript alternative to pyQT I recommend proton-native[1] - a React environment for cross platform native desktop apps.
Re:PyQt5 Tutorial: Create a Python GUI in 2018
by vbsteven on Tuesday September 25, 2018 @01:55PM
(#18068747)
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
by jcelerier on Tuesday September 25, 2018 @04:14PM
(#18070096)
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
by Thev00d00 on Wednesday September 26, 2018 @04:00AM
(#18073747)
/me cries in electron
Re:PyQt5 Tutorial: Create a Python GUI in 2018
by toyg on Tuesday September 25, 2018 @01:53PM
(#18068727)
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
by megous on Tuesday September 25, 2018 @02:54PM
(#18069310)
I see a simple electron app using 140MB total. Measured by running 'free -m' before and after starting the app and waiting a while for a gc to run.
Measuring memory use is difficult.
Re:PyQt5 Tutorial: Create a Python GUI in 2018
by TheAceOfHearts on Tuesday September 25, 2018 @03:06PM
(#18069428)
FYI, you can open dev tools in electron and manually trigger GC [0].
Re:PyQt5 Tutorial: Create a Python GUI in 2018
by megous on Wednesday September 26, 2018 @07:00AM
(#18074643)
I'm sure opending dev tools will increase memory use significantly though. So it's a bit self-defeating. :)
Perhaps there's some API to call instead.
Re:PyQt5 Tutorial: Create a Python GUI in 2018
by DanFeldman on Tuesday September 25, 2018 @02:01PM
(#18068810)
I don't know off hand, and we never compared w/ Electron, it was just floated as an idea. When we eventually fully refactor our GUI code to be agnostic of ROS we'll profile more completely.
Re:PyQt5 Tutorial: Create a Python GUI in 2018
by Waterluvian on Tuesday September 25, 2018 @05:50PM
(#18070812)
I'm presenting QGIS-ROS at ROSCon this year. It's a QGIS plugin for integrating real time robot data. Was relatively easy to do thanks to QGIS being Qt 5.
Felt exactly like making a RQT plugin.
Re:PyQt5 Tutorial: Create a Python GUI in 2018
by solarkraft on Tuesday September 25, 2018 @01:16PM
(#18068295)
Thank you for not using Electron.
Re:PyQt5 Tutorial: Create a Python GUI in 2018
by DanFeldman on Tuesday September 25, 2018 @01:34PM
(#18068509)
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?
Re:PyQt5 Tutorial: Create a Python GUI in 2018
by deckiedan on Tuesday September 25, 2018 @01:47PM
(#18068661)
I have 3 "internal" tools in electron I need to have running all the time on my PC... It's a corporate dell mini PC, poor thing.
Re:PyQt5 Tutorial: Create a Python GUI in 2018
by cpburns2009 on Tuesday September 25, 2018 @01:37PM
(#18068542)
Electron is notorious for disregarding all platform conventions, being slow, and being a memory hog.
Re:PyQt5 Tutorial: Create a Python GUI in 2018
by hotpotjunkie on Tuesday September 25, 2018 @01:59PM
(#18068795)
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.
Re:PyQt5 Tutorial: Create a Python GUI in 2018
by codemac on Tuesday September 25, 2018 @02:07PM
(#18068887)
> even though the development time is obviously shorter with electron
Evidence? I think you're making a great point (about the reputation of html/css/js) but leave the unfounded claims out and your point would be stronger.
For our use case, relative speed of the GUI isn't a factor. We've considered moving to electron just for ease of development, but python is winning out.
[1] http://wiki.ros.org/rqt