About the PyGTK blog
I was surprised to find that there is nothing at all about such a wonderful cross-platform GUI framework like PyGTK , although there are regular articles on Python . Well, let's correct this misunderstanding :-)
A little about why you might be interested in a cross-platform framework.
')
It is no secret that in recent years, many companies are seeking to reduce software licensing costs. Therefore, more and more office jobs are being transferred from Windows to Linux (Ubuntu and other distributions). This is great, but it creates a heterogeneous working environment: software running under one OS does not work under another. Of course, wine is gorgeous, but not a panacea.
It seems to me that in this case a good option with an eye to the future is to develop at least internal software using PyGTK. It will work on both Linux and Windows (Mac OS X is not very common in a corporate environment), good investment protection.
So, the advantages of PyGTK:
Minuses:
For the sake of fairness, I note that unusual does not mean a bad one; the appearance under Windows is good enough, but under Mac OS X it still works :-)
If the cross-platform GUI is important to you, the “native” appearance under Windows is not very important, and you are not going to distribute your application under Mac OS X anytime soon, this framework is a good choice.
Post introductory, so now I will list (approximately) what will be written in future articles:
I hope the blog will be useful for readers :-) I invite everyone to share information about PyGTK in this blog.
PS
Why not wxPython ? I have nothing against wxPython, it's just a PyGTK blog :-)
A little about why you might be interested in a cross-platform framework.
')
It is no secret that in recent years, many companies are seeking to reduce software licensing costs. Therefore, more and more office jobs are being transferred from Windows to Linux (Ubuntu and other distributions). This is great, but it creates a heterogeneous working environment: software running under one OS does not work under another. Of course, wine is gorgeous, but not a panacea.
It seems to me that in this case a good option with an eye to the future is to develop at least internal software using PyGTK. It will work on both Linux and Windows (Mac OS X is not very common in a corporate environment), good investment protection.
So, the advantages of PyGTK:
- PyGTK is a real Python library, so many routine things are solved using a very compact code.
- The PyGTK-based interface will work on Linux and Windows without rewriting the code.
- The LGPL license allows you to use it in commercial projects.
- There is a good visual interface designer, Glade
Minuses:
- Unusual (for non-Java programmers) widget layout system
- "Non-native" for Windows appearance.
- Under Mac OS X, it works through mmm ... glands.
For the sake of fairness, I note that unusual does not mean a bad one; the appearance under Windows is good enough, but under Mac OS X it still works :-)
If the cross-platform GUI is important to you, the “native” appearance under Windows is not very important, and you are not going to distribute your application under Mac OS X anytime soon, this framework is a good choice.
Post introductory, so now I will list (approximately) what will be written in future articles:
- Layout - start of beginnings
- More about layout and widgets
- Widgets
- Containers aren't just the layout.
- MVC in PyGTK
- Making the application installer on PyGTK for Windows
I hope the blog will be useful for readers :-) I invite everyone to share information about PyGTK in this blog.
PS
Why not wxPython ? I have nothing against wxPython, it's just a PyGTK blog :-)
Source: https://habr.com/ru/post/44670/
All Articles