A ramble on Python GUI

Under Windows do C + + that will be used to use MFC, the framework has become dependent, using the framework although the use of a lot of unnecessary system resources, but also slowed down the program's running efficiency, but to do a demo or something to fill in the box code can be really convenient. And for me, this is more regular than pure handwriting, which part should be filled in what should not be filled out what system will help you to identify, to avoid the pure hand playing the casual. Today on the Internet casually search Python's post, think of a previous sweep of the PYQT. In fact, my basic requirements for the framework is that when I need to do the UI must be simple and practical, of course, it is best to have a very strong extensibility, so after really need to play the time also have to play. Possible personal level issues, using Python's standard tkinter, the things written out are too ugly, and the control position is difficult to control. Also some people recommend Wxpython, unfortunately the download page prompts currently only support Python2.7. By the way, Python3 have been out so long, why the original many useful tools have not followed. In fact, the reasons for the abandonment of Wxpython and some people say that many bugs, document resources are not rich, in fact, I am a document this kind of thing is still very dependent. With MFC, the document in full detail to let me admire, a lot of time to do a demo of the case is enough, learn something very easy to get started. As a matter of fact, what I need is a framework, not just some UI-level stuff, and tkinter and Wxpython are just some class libraries on the GUI, so they're back to PYQT, which seems to be a more comprehensive class library. Let's take a look at the Python page description of PyQt: PyQt is one of the both most popular Python bindings for the Qt cross-platform gui/xml/sql C + + Framew Ork (another binding is pyside). Take a look at the description of QT by Baidu:

QT is a cross-platform C + + graphical user Interface application Development framework developed by caused by parity technology in 1991. It can either develop GUI programs or be used to develop non-GUI programs, such as console tools and servers. QT is an object-oriented framework that uses special code generation extensions (called Meta Object Compiler, MOC) and some macros that are easy to extend and allow for component programming. In 2008, the technology was acquired by Nokia, and Qt became a programming language tool for Nokia. In 2012, QT was acquired by Digia. April 2014, cross-Platform integrated development environment QT Creator 3.1.0 officially released, to achieve full support for iOS, add plugins such as WINRT, Beautifier, discard gdb debugging support without Python interface, integrated with clang-C + + code module, and the Android support has been adjusted to achieve full support for iOS, Android, WP.
QT is a cross-platform C + + graphical user interface application framework developed by the 1991 technology. It provides all the functionality that application developers need to build an art-level graphical user interface. QT is easy to scale and allows for real component programming. Basically, Qt is the same type of thing as the MOTIF,OPENWIN,GTK on the X Window and the Mfc,owl,vcl,atl on the Windows platform.

OK, see here I am satisfied, because it said is with MFC is the same type of things, it seems to have not found the wrong.

Back to the front, I have to admit, I have obsessive-compulsive disorder, because I notice out of the PYQT, there is another Python package qt, pyside, it and pyqt who is better? The Python home page's description of Pyside is simple and nothing special is found. On the wiki page that came to Pyside, I saw the latest version of Pyside was 1.2.2 released on April, and provides access to the complete Q T 4.8 framework. Because it is a beginner python,python2 and Python3 to me is the same strange. Although there are a lot of projects and documents on Python2 online, python3 substitution python2 is a general trend, just a matter of time. Therefore, since it is a beginner, I would like to omit from the 2 over to 3 of Kung Fu. Of course, there are very few projects and documents based on Python3 now, and it will be a long way from python3 to start learning. Based on this idea, I hope that the things I use are up to date and can keep up with the situation, The latest version of QT has been updated to 5.x, and Pyside is now followed by 4.8, and the last update date is 14, online also has a post said pyside to Python3 is only part of the support, so basically give up the expectations of Pyside. But based on Pyside is pyqt strong on, or grilled a netizen on the PYQT and pyside comparison:

In the PYTHON-CN Mail group today, we see a discussion of PyQt and Nokia pyside issues.

PyQt is the copyright of the commercial and GPL, and Pyside is LGPL.

That is, if you use PYQT for commercial applications, you will need to pay for it, while using Nokia's pyside is not required.

Off Topic:

Since Nokia acquired QT, it has been aggressively promoting QT. The latest pyside released the day before yesterday has been supported by MS Windows,
And it's LGPL.

Believe that pyside future will be more powerful and easy to use than PyQt. According to Nokia, it will be more pythonic.

Pyside is a open source sofware project providing Python bindings for the QT framework. Qt is a cross-platform application and UI framework, allowing the developers to write applications once and deploy them AC Ross many operating systems without rewriting the source code, while Python was a modern, dynamic programming language with A vivid developer community.

Combining the power of Qt and Python, Pyside provides the wealth of the QT framework for developers writing software in Python and presents a first-class rapid application development platform purported to being available on all major operating system S.

The following are the results of online search

LGPL Concept

LGPL is a short form of the GNU Lesser General public License (GNU Wide Common license), formerly known as Gnulibrary General public License (the GNU Library Universal Common license), in a relaxed manner with B SD, APACHE,XFREE86 license similar.

The GPL (general public License) and LGPL (Lesser general public License) are two of the GNU License. More and more free software (software) uses the GPL as its authorization statement, and if the GPL is not understood at all, it may violate the GPL's mandate in the use of free software. It doesn't matter if it's an individual or an informal company, but if it's a company of any size, there's a risk of being sued.

When I was using log4cpp, I thought about authorizing things, so I had an interest in understanding the GPL. This is necessary, because the company also maintains a verified free software library, which contains the free software in addition to the functionality is reliable, but also must be private use, otherwise the consequences are serious.

The original version of Log4cpp used the GPL as an authorization statement and switched to a looser LGPL after version 0.2.1. LGPL was originally the abbreviation of the library GPL and later renamed the Lesser GPL, which is the looser GPL. When a free software uses the GPL statement, the user of the software has the right to republish, modify the software and obtain the source code of the software, but as long as the user uses the free software in their program, or the use of modified software, the user's program must also publish its source codes, while allowing others to publish, modify. In other words, the new software developed with free software under the GPL must also be free software.

LGPL is a variant of the GPL, and it is the GNU's offer to get more support from even commercial software developers. The biggest difference from the GPL is that free software, which can be privately used by LGPL, can be privately owned without the need for free software. Therefore, any company should ensure that it is licensed under LGPL or other GPL variants before using free software.
Edit this paragraph

Richard Stallman's treatise on the GPL and LGPL

Why you should not use LGPL to publish your next library

The GNU program has two primary licenses when using the library. One is the GNU LGPL (library GPL) and the other is the general GNU GPL. There is a big difference between choosing a different license: Selecting LGPL allows the library to be used in private programs, and selecting the normal GPL allows it to be used only in free software.

About which license is best for the specified library This problem is actually a policy issue, and it depends on the actual situation. Currently, most GNU libraries are LGPL, which means that we only use one of these strategies and ignore the other. So now we are looking for more libraries to be published in the form of an ordinary GPL license.

Proprietary software developers have a monetary advantage, and free software developers need to take advantage of each other's strengths. Using a common GPL for a library is more advantageous to free software developers than to proprietary software developers: libraries They can use are not available to private software developers.

Using the generic GPL is not good for all libraries. In some cases, it is more reasonable to use LGPL. The most common scenario is when a free library's features can be easily implemented by proprietary software in other alternative libraries. In this case, the library cannot give any special advantage to free software, It is therefore best to publish the library for LGPL.

That's why we chose LGPL for the GNU C library. In short, there are a lot of other C libraries, and we use the GPL to publish the library, forcing private software developers to use other libraries--that's not a problem for them, and we're in trouble.

However, when a library provides features that are very unique, such as the GNU Readline, the situation is quite different. The ReadLine library enables input editing and recording of interactive program operations, which are often rare elsewhere. Releasing it under the GPL and restricting it to be used only in free programs is an important promotion for our community. At least today, an application is free software, just because it needs to use ReadLine.

If we collect some powerful, proprietary, GPL-like libraries, they will provide a series of useful modules for the construction of new free software. This will be a significant advantage for future free software development, and some projects will consider liberalizing the software in order to use these libraries. University projects are easy to influence, and today, as some companies start to think about freeing up software, even some business projects will be affected.

Private software developers, trying to deny the importance of free competition, are desperate to persuade the authors not to use the GPL to publish the library. For example, they would call for egoism and vowed that if we let them use the code in proprietary software products, there would be "more users" to use it. Popularity is a temptation, and it makes a library developer inclined to believe that the first thing a society needs is to promote the popularity of a library.

But we should not listen to this temptation, because if we unite, we can do better. We, the free software developers, should support each other. By publishing libraries that can be used only for free software, we can help each other to make each other's free packages better than other private alternatives. The entire free software movement will have more opportunities because free software as a whole will perform better in the competition.

Because the term "LGPL (Library GPL)" conveys a false view of the issue, we plan to change the title to "sub-GPL (Lesser GPL)". In fact, it takes a while to change the name, but you don't have to wait-you can now publish a library that applies the GPL license.

The prospect of pyside from above seems to be more powerful than PYQT, and for commercial development, Pyside is a better choice, of course, for me personally, there is little difference. But I was thinking that Nokia would go bankrupt, and that Pyside would grow as fast as he said. Sure enough, a netizen's post confirms my guess:

When I got up in the morning, I saw a bad news, Matti Airas in the Pyside mailing list, said:

• Currently, the vast majority of the pyside core development is do by the Openbossa INdT team in Brazil and funded by Nok Ia ' s MeeGo Computers team-the Pyside Project has internally been a enabler for the MeeGo 1.2 Harmattan Python project. Unfortunately, the Nokia N9 is the only MeeGo (Harmattan) phone to being published by Nokia, and Nokia's MeeGo team is being Ramped down already in the near future. Because of this, the Nokia MeeGo funding for Pyside was slated to end after this year, and I had also failed to find a New sponsor for the project within Nokia.

Pyside, who had just finished its two birthday last week (August 18), has been funded by the Openbossa INdT (Nokia technology Institute) group in Brazil, with funding from Nokia's MeeGo computer group.

Unfortunately, Nokia's Meego team seems to be in a bad place, and their support for Pyside is expected to end next year. Pyside new supporters are not yet found.

Matti Airas believes that even without the continued help of the Nokia midwife, the Pyside project should also have the ability to survive and grow. But this means that the community will be responsible for leadership in both project planning and practical development.

In fact, from the Pyside and PYQT update speed I can choose which one. Just say PYQT, PYQT4 and PyQt5 two versions, the former is based on qt4.x, support Python. The latter is based on qt5.x, which supports Python3. Although only the C + + version of the QT document, but still very comprehensive. and the installation package brought a lot of examples, the role of the novice is still very big. However, there will be a problem starting examples, 5.3.1 version can start examples, but launch example will be error:

It is not possible to update the graphics driver. Later upgrade to 5.5.1examples Direct start does not get up, the annoyance. Examples's startup program is "C:\Python34\Lib\site-packages\PyQt5\examples\qtdemo.pyw"

Let's go back to the study tomorrow. But today suddenly found that the Python official website can open again, no more deliberately fq. Although Google was blocked but there are mirror sites can go up, but some foreign technical sites are still on the FQ, sooner or later.

A ramble on Python GUI