Комментарии:
If people are going to commit to anyone of these to options, note there is no substantive community for working with these two frameworks. And absolutely zero for working with the QML language. (Qt is not QML) You’ll pretty much have a pretty interface but connecting to a database or doing serial communications, you’ll be on your own. It should come with a warning, that the developers of the framework don’t respect the time commitment of folks new to the framework. But this would become obvious when you see that no one is really offering any tutorials on it. You can take your chances with Qt but not the QML part.
ОтветитьExcellent intro, thank you!
ОтветитьI don't understand something: What do you mean by give my code to my client? how people from PyQt5 knows I am going to sell a gui built using this framework? If I create a .exe to install the gui in the client's computer... I don't really understand
ОтветитьGreat video, well presented and pretty much told me what I needed to know. I'll subscribe and watch more!
Ответитьi prefer tkinter when possible. sometimes simple is better
ОтветитьThank you 💕
ОтветитьAm I wrong for thinking that pyside is only commercial (paid) licensing
ОтветитьExcellent video. Clearly explained, with genuinely helpful clarifications, you've obviously put thought into this rather than cribbing points. Now I'm keen to watch other of your videos too 👍
ОтветитьI was wondering - even if I want to distribute my software, since it is python scripts, how can I hide the code from users? Isn't python code always source code?
ОтветитьSuperb exposition. Thanks so much.
ОтветитьThank you for this very clear and concise explanation.
Ответитьwhat an instructive video! Keep up the good work
ОтветитьQt is actually pronounced as "cute" according to Wikipedia.
ОтветитьYour voice....you speak very fluently. Thanks for this video !
ОтветитьC++ 📈📈📈
ОтветитьQuite good video, but in my opinion two very important questions should be considered, too: Which one has the larger user base? And how easy is it to contribute (e.g. bugs, code, documentation). Both affects how up-to-date each software stays when it is already released. While a big user base might faster stumble uppon bugs in the software, and maybe provide workarounds or solutions, a project that allows easy contribution might even have faster provisioning of bug fixes.
From my daily use, I would always go with pyqt in early development. And then, if really needed switch to pyside for releasing.
It’s not QuTee, it’s pronounced “Cute”.
ОтветитьIt's just awesome
Ответить