PyMaemo/GUI toolkit selection guide - Revision history

imported_>amigadave: a couple of links

2010-06-23T12:21:22Z

a couple of links

← Older revision		Revision as of 12:21, 23 June 2010
Line 1:		Line 1:
	~~== Introduction ==~~		This page describes the alternative toolkits with which graphical user interfaces can be created in [[PyMaemo]]. Their respective differences and future prospects are discussed to help any new PyMaemo developers make an informed technology selection.

	This page describes the alternative toolkits with which graphical user interfaces can be created in PyMaemo. Their respective differences and future prospects are discussed to help any new PyMaemo developers make an informed technology selection.

	In particular, the differences of GTK+ and Qt toolkits are described, as well as the roles of the PySide and PyQt Qt binding projects.		In particular, the differences of GTK+ and Qt toolkits are described, as well as the roles of the PySide and PyQt Qt binding projects.
Line 55:		Line 53:
	PyQt 4.7 for N900 was released in Feb 2010 announced [http://talk.maemo.org/showthread.php?t=42754 here]		PyQt 4.7 for N900 was released in Feb 2010 announced [http://talk.maemo.org/showthread.php?t=42754 here]

	PyQt 4.7.3 for N900 PR1.2 (Qt4.6) was released in Apr 2010 announced [http://talk.maemo.org/showthread.php?p=626443 here]		PyQt 4.7.3 for N900 [[Maemo 5/PR1.2\|PR1.2]] (Qt4.6) was released in Apr 2010 announced [http://talk.maemo.org/showthread.php?p=626443 here]







	[[Category:Python]]		[[Category:Python]]

imported_>mairas: Updated the PySide section

2010-06-07T17:49:21Z

Updated the PySide section

← Older revision		Revision as of 17:49, 7 June 2010
Line 31:		Line 31:
	=== PySide ===		=== PySide ===

	[http://www.pyside.org/ PySide] is a Python binding for the Qt framework, developed by Nokia at OpenBossa by the same team as PyMaemo itself. It was initially published in August 2009 and, on the Maemo 5 platform, provides full-featured bindings for Qt 4.6 (including the Maemo-specific QMaemo5 classes). PySide is licensed under LGPL, allowing both open source and proprietary software development. The generator tools for creating new bindings are also available, allowing developers to rapidly create new bindings if required.		[http://www.pyside.org/ PySide] is a Python binding for the Qt framework, developed by Nokia at OpenBossa by the same team as PyMaemo itself. It was initially published in August 2009 and, on the Maemo 5 platform, provides full-featured bindings for Qt 4.7 (on Maemo 5, Qt 4.6, including the Maemo-specific QMaemo5 classes). PySide is licensed under LGPL, allowing both open source and proprietary software development. The generator tools for creating new bindings are also available, allowing developers to rapidly create new bindings if required.

	The PyMaemo team will provide the bindings for ~~Maemo 6~~ platform APIs (~~DirectUI~~, ~~Maemo API~~) using PySide.		The PyMaemo team will provide the bindings for the Harmattan platform APIs (MeeGo Touch, Qt Mobility, select Harmattan platform APIs) using PySide.

	Currently, the disk and memory footprint of PySide is still somewhat larger than PyQt (although the run-time performance is at least on par). This issue will be solved in March 2010 when the new binding architecture, [http://setanta.wordpress.com/2009/08/31/shiboken/ Shiboken], will replace the current Boost.Python based implementation. Also, since PySide is a relatively young project, it is still more ~~buggy~~ than PyQt.		Since PySide is a relatively young project, it is still ongoing maturization period and faces more changes than PyQt.

	If your project requires Maemo-specific Qt extensions or Qt ~~4.6~~ features and you ~~don't mind the temporary memory impact of PySide and~~ want your application to work ~~as is~~ in the future ~~Maemo~~ platforms, PySide is the best choice for you.		If your project requires Maemo/MeeGo-specific Qt extensions or latest Qt features and you want your application to work in the future MeeGo platforms, PySide is the best choice for you.

	=== PyQt ===		=== PyQt ===

imported_>mairas: Let's keep the PyQt commentary in the PyQt section, shall we?

2010-06-07T17:40:41Z

Let's keep the PyQt commentary in the PyQt section, shall we?

← Older revision		Revision as of 17:40, 7 June 2010
Line 38:		Line 38:

	If your project requires Maemo-specific Qt extensions or Qt 4.6 features and you don't mind the temporary memory impact of PySide and want your application to work as is in the future Maemo platforms, PySide is the best choice for you.		If your project requires Maemo-specific Qt extensions or Qt 4.6 features and you don't mind the temporary memory impact of PySide and want your application to work as is in the future Maemo platforms, PySide is the best choice for you.

	~~(Note: starting with PR1.2, PyQt also provides full QMaemo5* and Qt4.6 support)~~

	=== PyQt ===		=== PyQt ===

imported_>mairas: Undo revision 35441: biased wording, speculation

2010-06-07T17:40:06Z

Undo revision 35441: biased wording, speculation

← Older revision		Revision as of 17:40, 7 June 2010
Line 4:		Line 4:

	In particular, the differences of GTK+ and Qt toolkits are described, as well as the roles of the PySide and PyQt Qt binding projects.		In particular, the differences of GTK+ and Qt toolkits are described, as well as the roles of the PySide and PyQt Qt binding projects.

	Note that even though all bindings have licensing options that allow proprietary/commercial development in some form, at least for Maemo 5, the Ovi store does not accept Python based applications. This means that if you plan on using the bindings listed below, you will have to manage distribution and payment by yourself.

	== GTK+-based toolkits ==		== GTK+-based toolkits ==

imported_>achipa: No python in Ovi :(

2010-06-07T11:41:29Z

No python in Ovi :(

← Older revision		Revision as of 11:41, 7 June 2010
Line 4:		Line 4:

	In particular, the differences of GTK+ and Qt toolkits are described, as well as the roles of the PySide and PyQt Qt binding projects.		In particular, the differences of GTK+ and Qt toolkits are described, as well as the roles of the PySide and PyQt Qt binding projects.

			Note that even though all bindings have licensing options that allow proprietary/commercial development in some form, at least for Maemo 5, the Ovi store does not accept Python based applications. This means that if you plan on using the bindings listed below, you will have to manage distribution and payment by yourself.

	== GTK+-based toolkits ==		== GTK+-based toolkits ==

imported_>achipa: Qt4.6 support landed before PR1.2

2010-05-23T17:57:52Z

Qt4.6 support landed before PR1.2

← Older revision		Revision as of 17:57, 23 May 2010
Line 43:		Line 43:
	=== PyQt ===		=== PyQt ===

	[http://www.riverbankcomputing.co.uk/software/pyqt/intro PyQt] is a Python binding for the Qt framework, developed by Riverbank Computing Ltd. It is a very established and stable set of bindings and widely used in the desktop world. On Maemo 5, it is maintained as a community effort. PyQt on Maemo 5 provides support for both Qt 4.6 ~~(starting from [[Maemo 5/PR1.2]])~~ and Qt 4.5. It will also support the future Qt 4.7 through experimental releases in extras-devel. PyQt for Qt 4.6 supports the Maemo 5 specific classes.		[http://www.riverbankcomputing.co.uk/software/pyqt/intro PyQt] is a Python binding for the Qt framework, developed by Riverbank Computing Ltd. It is a very established and stable set of bindings and widely used in the desktop world. On Maemo 5, it is maintained as a community effort. PyQt on Maemo 5 provides support for both Qt 4.6 and Qt 4.5. It will also support the future Qt 4.7 through experimental releases in extras-devel. PyQt for Qt 4.6 supports the Maemo 5 specific classes.

	It is licensed under GPL for Open Source projects, but a commercial license can be obtained from Riverbank for proprietary development. While new PyQt-compatible bindings can be created using [http://directory.fsf.org/project/Python-SIP/ SIP], no freely available automatic binding generation tools exist, making independent generation of bindings for large SIP-based libraries impractical.		It is licensed under GPL for Open Source projects, but a commercial license can be obtained from Riverbank for proprietary development. While new PyQt-compatible bindings can be created using [http://directory.fsf.org/project/Python-SIP/ SIP], no freely available automatic binding generation tools exist, making independent generation of bindings for large SIP-based libraries impractical.

imported_>achipa: experimental nomenclature

2010-04-26T08:29:46Z

experimental nomenclature

← Older revision		Revision as of 08:29, 26 April 2010
Line 26:		Line 26:

	Any native Qt application written for Maemo 5 adopts the platform's native look and feel. Furthermore, these applications will be at least source-level compatible with Maemo 6 and will adopt its look and feel accordingly. Hence, Qt is the best selection as a toolkit if you want to future-proof your application.		Any native Qt application written for Maemo 5 adopts the platform's native look and feel. Furthermore, these applications will be at least source-level compatible with Maemo 6 and will adopt its look and feel accordingly. Hence, Qt is the best selection as a toolkit if you want to future-proof your application.

			The development snapshot releases of next versions is available from extras-devel, and is marked with ’experimental’ in the package name (libqt4-experimental, python2.5-qt4-experimental, pyside-experimental). Use these packages only if you need cutting edge features and have no intention of publishing your software to end-users.

	=== PySide ===		=== PySide ===

imported_>achipa: PyQt 4.7.3 release

2010-04-26T08:25:59Z

PyQt 4.7.3 release

← Older revision		Revision as of 08:25, 26 April 2010
Line 41:		Line 41:
	=== PyQt ===		=== PyQt ===

	[http://www.riverbankcomputing.co.uk/software/pyqt/intro PyQt] is a Python binding for the Qt framework, developed by Riverbank Computing Ltd. It is a very established and stable set of bindings and widely used in the desktop world. On Maemo 5, it is maintained as a community effort. PyQt on Maemo 5 ~~currently~~ provides support for Qt 4.5 ~~(which is shipped with the release firmware~~) ~~in Extras,~~ and ~~Qt4~~.6 support ~~with Maemo classes is available from source, binaries will appear~~ in extras-devel ~~in sync with~~ the [[Maemo 5~~/PR1.2]] release~~. It is licensed under GPL for Open Source projects, but a commercial license can be obtained from Riverbank for proprietary development. While new PyQt-compatible bindings can be created using [http://directory.fsf.org/project/Python-SIP/ SIP], no freely available automatic binding generation tools exist, making independent generation of bindings for large SIP-based libraries impractical.		[http://www.riverbankcomputing.co.uk/software/pyqt/intro PyQt] is a Python binding for the Qt framework, developed by Riverbank Computing Ltd. It is a very established and stable set of bindings and widely used in the desktop world. On Maemo 5, it is maintained as a community effort. PyQt on Maemo 5 provides support for both Qt 4.6 (starting from [[Maemo 5/PR1.2]]) and Qt 4.5. It will also support the future Qt 4.7 through experimental releases in extras-devel. PyQt for Qt 4.6 supports the Maemo 5 specific classes.

			It is licensed under GPL for Open Source projects, but a commercial license can be obtained from Riverbank for proprietary development. While new PyQt-compatible bindings can be created using [http://directory.fsf.org/project/Python-SIP/ SIP], no freely available automatic binding generation tools exist, making independent generation of bindings for large SIP-based libraries impractical.

	PyQt cannot be intermixed with the future Harmattan platform API bindings created using PySide (though such bindings might become available via PyQt).		PyQt cannot be intermixed with the future Harmattan platform API bindings created using PySide (though such bindings might become available via PyQt).
Line 47:		Line 49:
	PyQt is currently the most mature set of Qt bindings for PyMaemo. It provides a stable, and bugfree set of Python Qt bindings. Moreover, the source-level compatibility of PySide with PyQt is rather high, making porting PyQt programs to PySide (and vice versa) an easy task, thus providing an upgrade path for PyQt developers in the future. PyQt (as a Qt 4.5 binding) is also available on the legacy [[Nokia N800\|N800]] and [[Nokia N810\|N810]] devices and pre-PR1.2 N900s.		PyQt is currently the most mature set of Qt bindings for PyMaemo. It provides a stable, and bugfree set of Python Qt bindings. Moreover, the source-level compatibility of PySide with PyQt is rather high, making porting PyQt programs to PySide (and vice versa) an easy task, thus providing an upgrade path for PyQt developers in the future. PyQt (as a Qt 4.5 binding) is also available on the legacy [[Nokia N800\|N800]] and [[Nokia N810\|N810]] devices and pre-PR1.2 N900s.

	If you want to ~~immediately~~ release a Python Qt 4.5 or Qt 4.6 application with as stable bindings as possible, and are prepared to possibly port your code to PySide in the future, then PyQt is the right choice for you.		If you want to release a Python Qt 4.5 or Qt 4.6 application with as stable bindings as possible, and are prepared to possibly port your code to PySide in the future, then PyQt is the right choice for you.

	==== Current Versions ====		==== Current Versions ====
Line 53:		Line 55:
	PyQt 4.7 for N900 was released in Feb 2010 announced [http://talk.maemo.org/showthread.php?t=42754 here]		PyQt 4.7 for N900 was released in Feb 2010 announced [http://talk.maemo.org/showthread.php?t=42754 here]

			PyQt 4.7.3 for N900 PR1.2 (Qt4.6) was released in Apr 2010 announced [http://talk.maemo.org/showthread.php?p=626443 here]

imported_>achipa: PyQt also has QMaemo5 and Qt4.6 support starting from PR1.2

2010-04-02T17:23:32Z

PyQt also has QMaemo5 and Qt4.6 support starting from PR1.2

← Older revision		Revision as of 17:23, 2 April 2010
Line 36:		Line 36:

	If your project requires Maemo-specific Qt extensions or Qt 4.6 features and you don't mind the temporary memory impact of PySide and want your application to work as is in the future Maemo platforms, PySide is the best choice for you.		If your project requires Maemo-specific Qt extensions or Qt 4.6 features and you don't mind the temporary memory impact of PySide and want your application to work as is in the future Maemo platforms, PySide is the best choice for you.

			(Note: starting with PR1.2, PyQt also provides full QMaemo5* and Qt4.6 support)

	=== PyQt ===		=== PyQt ===

imported_>achipa: Qt4.6 status + Maemo classes

2010-04-02T17:20:32Z

Qt4.6 status + Maemo classes

← Older revision		Revision as of 17:20, 2 April 2010
Line 39:		Line 39:
	=== PyQt ===		=== PyQt ===

	[http://www.riverbankcomputing.co.uk/software/pyqt/intro PyQt] is a Python binding for the Qt framework, developed by Riverbank Computing Ltd. It is a very established and stable set of bindings and widely used in the desktop world. On Maemo 5, it is maintained as a community effort. PyQt on Maemo 5 currently provides support for Qt 4.5 (which is shipped with the release firmware) in Extras, and Qt4.6 support with Maemo classes will appear in extras-devel in sync with the [[Maemo 5/PR1~~.2PR1~~.2]] release. It is licensed under GPL for Open Source projects, but a commercial license can be obtained from Riverbank for proprietary development. While new PyQt-compatible bindings can be created using [http://directory.fsf.org/project/Python-SIP/ SIP], no freely available automatic binding generation tools exist, making independent generation of bindings for large libraries impractical.		[http://www.riverbankcomputing.co.uk/software/pyqt/intro PyQt] is a Python binding for the Qt framework, developed by Riverbank Computing Ltd. It is a very established and stable set of bindings and widely used in the desktop world. On Maemo 5, it is maintained as a community effort. PyQt on Maemo 5 currently provides support for Qt 4.5 (which is shipped with the release firmware) in Extras, and Qt4.6 support with Maemo classes is available from source, binaries will appear in extras-devel in sync with the [[Maemo 5/PR1.2]] release. It is licensed under GPL for Open Source projects, but a commercial license can be obtained from Riverbank for proprietary development. While new PyQt-compatible bindings can be created using [http://directory.fsf.org/project/Python-SIP/ SIP], no freely available automatic binding generation tools exist, making independent generation of bindings for large SIP-based libraries impractical.

	PyQt cannot be intermixed with the future Harmattan platform API bindings created using PySide.		PyQt cannot be intermixed with the future Harmattan platform API bindings created using PySide (though such bindings might become available via PyQt).

	PyQt is currently the most mature set of Qt bindings for PyMaemo. It provides a stable, and bugfree set of Python Qt bindings. Moreover, the source-level compatibility of PySide with PyQt is rather high, making porting PyQt programs to PySide (and vice versa) an easy task, thus providing an upgrade path for PyQt developers in the future. PyQt (as a Qt 4.5 binding) is also available on the legacy [[Nokia N800\|N800]] and [[Nokia N810\|N810]] devices and pre-PR1.2 N900s.		PyQt is currently the most mature set of Qt bindings for PyMaemo. It provides a stable, and bugfree set of Python Qt bindings. Moreover, the source-level compatibility of PySide with PyQt is rather high, making porting PyQt programs to PySide (and vice versa) an easy task, thus providing an upgrade path for PyQt developers in the future. PyQt (as a Qt 4.5 binding) is also available on the legacy [[Nokia N800\|N800]] and [[Nokia N810\|N810]] devices and pre-PR1.2 N900s.

	If you want to immediately release a Python Qt 4.5 application with as stable bindings as possible~~, don't require the Maemo-specific pieces~~, and are prepared to possibly port your code to PySide in the future, then PyQt is the right choice for you.		If you want to immediately release a Python Qt 4.5 or Qt 4.6 application with as stable bindings as possible, and are prepared to possibly port your code to PySide in the future, then PyQt is the right choice for you.

	==== Current Versions ====		==== Current Versions ====