Talk:PyMaemo/GUI toolkit selection guide

Matti, can you elaborate why is PyQt's commercial license considered impractical on Maemo ? As I understand it just allows proprietary applications to use PyQt, it's not any more impractical that it is for GPL software. There is no requirement to use 'special binaries' or sorts.

I believe you would, at least according to this page, have to provide separate versions of PyQt modules for commercial use, which would be quite a hurdle on Maemo.

mairas 15:16, 8 January 2010 (UTC)

On a second thought, restored the original wording as it was more neutral.

mairas 16:14, 8 January 2010 (UTC)

[edit] Ovi compatibility

If there are concerns about my (speculative?) wording regarding the non-acceptability of binding-based software in Ovi, please submit an acceptable one. Stating an important fact CANNOT be speculative. I’m saying important as there were several submissions to Calling All Innovators which were written in Python and are now in jeopardy of being rejected because the authors were not aware of the limitations of Ovi.

[edit] "Best choice" binding for Maemo specific functionality

"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."

I find this comment biased or misleading at best unless there is a clear comparison WHY PySide should be considered a better choice in case of Maemo/MeeGo-specific Qt extensions. That’s why I added the PyQt comment striving for balace - I didn’t want to reword somebody else’s sentences, but as is, the claim is IMHO pretentious.

Retrieved from "http://bugs.maemo.org/Talk:PyMaemo/GUI_toolkit_selection_guide"