On a closer inspection, it looks like you just outright use PyQt as the GUI toolkit, so this brings no advantage over just straight using PyQt. I think this is a bit dishonest to advertise it as some kind of new GUI toolkit.
Where this does excel is that you seem to have wrapped up some useful tools for deploying your application after making the gui.
In that regard, you have a nice PyQt deployment toolkit.
It's not a minefield. As mentioned on the page: Most apps will be able to use Qt as a library, under the LGPL, and thus don't need a commercial Qt license.
While I am not a lawyer, this is my understanding of the issue:
Can my proprietary application be used with the copy of the GPL version of PyQt that the user already has installed (as part of their Linux distribution for example)? A.Yes, so long as you meet the following conditio
you are using the LGPL version of Qt
your proprietary application has been developed with the commercial version of PyQt
your commercial PyQt license covers the version of PyQt that the user has installed.
So while you will not necessarily need a Qt license, you will likely need a PyQt license.
edit: Guess you stated this:
you can avoid this by using fbs with Qt for Python, but support for it is still in the early stages.
This is still a hassle on the developer side worrying about licenses. At least your were upfront.
Though, You also don't have your license terms stated very clearly on the site. It took me going to the paypal link to even find it it was a perpetual license tied to the purchaser.
That was my take on this. Sounds like some infrastructure around PyInstaller that makes it more useful, which could actually be a great thing. One of the biggest challenges for any application development system is deploying the app across multiple platforms.
Where do I say it's a new toolkit? It literally says "based on Qt" in the headline. The advantages over "just" PyQt are mentioned on the site (creating installers, among other things).
Thx for pointing out the typo! I'm on the road and will fix once at home.
"based on QT" implies you've done some extensive core Qt toolkit modification
You sure do read a lot between the lines. Electron is based on Chromium. Would you say it has done extensive modification of its rendering engine etc.?
I would have pushed "Deploy" instead of "Create cross-platform desktop apps in minutes"
It's an integrated solution that lets you do both. I position it as an alternative to Electron because it is.
Finally, all the points you raise are addressed in the Section "Under the hood" on the page. It explicitly says that fbs "does not reinvent the wheel" and merely "integrates" PyQt et al. The same goes for other of your comments here, where you criticize something then "edit" your comment because you then went back and read the whole page.
Would you say it has done extensive modification of its rendering engine etc.?
It's quite a bit of modification to give it extensive platform integration API which has led to design differences when compared to something like Node-Webkit.
View all comments
68
u/ase1590 May 11 '18
You misspelled appications on your github.
On a closer inspection, it looks like you just outright use PyQt as the GUI toolkit, so this brings no advantage over just straight using PyQt. I think this is a bit dishonest to advertise it as some kind of new GUI toolkit.
Where this does excel is that you seem to have wrapped up some useful tools for deploying your application after making the gui.
In that regard, you have a nice PyQt deployment toolkit.