LabRPS at 17:49, 26 July 2024

2024-07-26T17:49:35Z

← Older revision		Revision as of 10:49, 26 July 2024
Line 10:		Line 10:
	The [[PySide\|PySide]] library gives access to the cross-platform graphical user interface (GUI) toolkit Qt from [[Python\|Python]]. Qt is a collection of C++ libraries, but with the help of PySide, the same components can be used from [[Python\|Python]]. Every graphical interface that can be created in C++, can also be created and modified in Python. An advantage of using Python is that Qt interfaces can be developed and tested live, as we don't need to compile the source files.		The [[PySide\|PySide]] library gives access to the cross-platform graphical user interface (GUI) toolkit Qt from [[Python\|Python]]. Qt is a collection of C++ libraries, but with the help of PySide, the same components can be used from [[Python\|Python]]. Every graphical interface that can be created in C++, can also be created and modified in Python. An advantage of using Python is that Qt interfaces can be developed and tested live, as we don't need to compile the source files.

	When you install ~~FreeCAD~~, you should get both Qt and PySide as part of the package. If you are [[Compiling\|compiling]] yourself then you must verify that these two libraries are installed in order for ~~FreeCAD~~ to run correctly. Of course, PySide will only work if Qt is present.		When you install LabRPS, you should get both Qt and PySide as part of the package. If you are [[Compiling\|compiling]] yourself then you must verify that these two libraries are installed in order for LabRPS to run correctly. Of course, PySide will only work if Qt is present.

	In the past, ~~FreeCAD~~ used PyQt, another Qt binding for Python, but in 2013 ([https://github.com/~~FreeCAD~~/~~FreeCAD~~/commit/1dc122dc9a commit 1dc122dc9a]) the project migrated to PySide because it has a more permissible [[License\|License]].		In the past, LabRPS used PyQt, another Qt binding for Python, but in 2013 ([https://github.com/LabRPS/LabRPS/commit/1dc122dc9a commit 1dc122dc9a]) the project migrated to PySide because it has a more permissible [[License\|License]].

	For more information see:		For more information see:
Line 22:		Line 22:
	{{Caption\|Examples created with PySide. Left: a simple dialog. Right: a more complex dialog with graphs.}}		{{Caption\|Examples created with PySide. Left: a simple dialog. Right: a more complex dialog with graphs.}}

	==PySide in ~~FreeCAD~~ with Qt5==		==PySide in LabRPS with Qt5==

	~~FreeCAD~~ was developed to be used with Python 2 and Qt4. As these two libraries became obsolete, ~~FreeCAD~~ transitioned to Python 3 and Qt5. In most cases this transition was done without needing to break backwards compatibility.		LabRPS was developed to be used with Python 2 and Qt4. As these two libraries became obsolete, LabRPS transitioned to Python 3 and Qt5. In most cases this transition was done without needing to break backwards compatibility.

	Normally, the {{incode\|PySide}} module provides support for Qt4, while {{incode\|PySide2}} provides support for Qt5. However, in ~~FreeCAD~~ there is no need to use {{incode\|PySide2}} directly, as a special {{incode\|PySide}} module is included to handle Qt5.		Normally, the {{incode\|PySide}} module provides support for Qt4, while {{incode\|PySide2}} provides support for Qt5. However, in LabRPS there is no need to use {{incode\|PySide2}} directly, as a special {{incode\|PySide}} module is included to handle Qt5.

	This {{incode\|PySide}} module is located in the {{incode\|Ext/}} directory of an installation of ~~FreeCAD~~ compiled for Qt5.		This {{incode\|PySide}} module is located in the {{incode\|Ext/}} directory of an installation of LabRPS compiled for Qt5.

	{{Code\|code=		{{Code\|code=
Line 55:		Line 55:
	* [[PySide_Advanced_Examples\|PySide Advanced Examples]], many widgets.		* [[PySide_Advanced_Examples\|PySide Advanced Examples]], many widgets.

	The examples of PySide are divided into 3 parts, differentiated by level of exposure to PySide, Python and the ~~FreeCAD~~ internals. The first page has an overview on PySide; the second and third pages are mostly code examples at different levels.		The examples of PySide are divided into 3 parts, differentiated by level of exposure to PySide, Python and the LabRPS internals. The first page has an overview on PySide; the second and third pages are mostly code examples at different levels.

	It is expected that these examples are useful to get started, and afterwards the user can consult other resources online, or the official documentation.		It is expected that these examples are useful to get started, and afterwards the user can consult other resources online, or the official documentation.

LabRPS: Created page with "{{Docnav |Pivy |Interface creation }} {{TOCright}} ==Introduction== The PySide library gives access to the cross-platform graphical user interface (GUI) toolkit Qt from Python. Qt is a collection of C++ libraries, but with the help of PySide, the same components can be used from Python. Every graphical interface that can be created in C++, can also be created and modified in Python. An advantage of usin..."

2024-07-26T17:45:54Z

Created page with "{{Docnav |Pivy |Interface creation }} {{TOCright}} ==Introduction== The PySide library gives access to the cross-platform graphical user interface (GUI) toolkit Qt from Python. Qt is a collection of C++ libraries, but with the help of PySide, the same components can be used from Python. Every graphical interface that can be created in C++, can also be created and modified in Python. An advantage of usin..."

New page

{{Docnav
|[[Pivy|Pivy]]
|[[Interface_creation|Interface creation]]
}}

{{TOCright}}

==Introduction==

The [[PySide|PySide]] library gives access to the cross-platform graphical user interface (GUI) toolkit Qt from [[Python|Python]]. Qt is a collection of C++ libraries, but with the help of PySide, the same components can be used from [[Python|Python]]. Every graphical interface that can be created in C++, can also be created and modified in Python. An advantage of using Python is that Qt interfaces can be developed and tested live, as we don't need to compile the source files.

When you install FreeCAD, you should get both Qt and PySide as part of the package. If you are [[Compiling|compiling]] yourself then you must verify that these two libraries are installed in order for FreeCAD to run correctly. Of course, PySide will only work if Qt is present.

In the past, FreeCAD used PyQt, another Qt binding for Python, but in 2013 ([https://github.com/FreeCAD/FreeCAD/commit/1dc122dc9a commit 1dc122dc9a]) the project migrated to PySide because it has a more permissible [[License|License]].

For more information see:
* [https://en.wikipedia.org/wiki/PySide Wikipedia:PySide]
* [https://wiki.qt.io/Differences_Between_PySide_and_PyQt Differences Between PySide and PyQt]

[[File:PySideScreenSnapshot1.jpg]] [[File:PySideScreenSnapshot2.jpg]]

{{Caption|Examples created with PySide. Left: a simple dialog. Right: a more complex dialog with graphs.}}

==PySide in FreeCAD with Qt5==

FreeCAD was developed to be used with Python 2 and Qt4. As these two libraries became obsolete, FreeCAD transitioned to Python 3 and Qt5. In most cases this transition was done without needing to break backwards compatibility.

Normally, the {{incode|PySide}} module provides support for Qt4, while {{incode|PySide2}} provides support for Qt5. However, in FreeCAD there is no need to use {{incode|PySide2}} directly, as a special {{incode|PySide}} module is included to handle Qt5.

This {{incode|PySide}} module is located in the {{incode|Ext/}} directory of an installation of FreeCAD compiled for Qt5.

{{Code|code=
/usr/share/freecad/Ext/PySide
}}

This module just imports the necessary classes from {{incode|PySide2}}, and places them in the {{incode|PySide}} namespace. This means that in most cases the same code can be used with both Qt4 and Qt5, as long as we use the single {{incode|PySide}} module.
{{Code|code=
PySide2.QtCore -> PySide.QtCore
PySide2.QtGui -> PySide.QtGui
PySide2.QtSvg -> PySide.QtSvg
PySide2.QtUiTools -> PySide.QtUiTools
}}

The only unusual aspect is that the {{incode|PySide2.QtWidgets}} classes are placed in the {{incode|PySide.QtGui}} namespace.
{{Code|code=
PySide2.QtWidgets.QCheckBox -> PySide.QtGui.QCheckBox
}}

{{Top}}

==Examples of PySide use==

* [[PySide_Beginner_Examples|PySide Beginner Examples]], hello world, announcements, enter text, enter number.
* [[PySide_Intermediate_Examples|PySide Intermediate Examples]], window sizing, hiding widgets, popup menus, mouse position, mouse events.
* [[PySide_Advanced_Examples|PySide Advanced Examples]], many widgets.

The examples of PySide are divided into 3 parts, differentiated by level of exposure to PySide, Python and the FreeCAD internals. The first page has an overview on PySide; the second and third pages are mostly code examples at different levels.

It is expected that these examples are useful to get started, and afterwards the user can consult other resources online, or the official documentation.

{{Top}}

==Documentation==
There are some differences in handling of widgets in Qt4 (PySide) and Qt5 (PySide2). The programmer should be aware of these incompatibilities, and should consult the official documentation if something doesn't seem to work as expected on a given platform. Nevertheless, Qt4 is considered obsolete, so most development should target Qt5 and Python 3.

The PySide documentation refers to the Python-style classes; however, since Qt is originally a C++ library, the same information should be available in the corresponding C++ reference.
* [https://doc.qt.io/qtforpython/modules.html Qt Modules] available from PySide2 (Qt5).
* [https://doc.qt.io/qt-5/modules-cpp.html All Qt classes by module] in Qt5 for C++.
* [https://deptinfo-ensip.univ-poitiers.fr/ENS/pyside-docs/index.html Qt Modules] available from PySide (Qt4).

{{Top}}

{{Docnav
|[[Pivy|Pivy]]
|[[Interface_creation|Interface creation]]
}}

{{Powerdocnavi}}
[[Category:Developer Documentation]]
[[Category:Python Code]]

PySide - Revision history

LabRPS at 17:49, 26 July 2024