Talk:PyMaemo/GUI toolkit selection guide
m (Talk:PyMaemo/GUIToolkitSelectionGuide moved to Talk:PyMaemo/GUI toolkit selection guide: Naming convention - no CamelCase) |
(→Ovi compatibility: new section) |
||
| Line 12: | Line 12: | ||
[[User:mairas|mairas]] 16:14, 8 January 2010 (UTC) | [[User:mairas|mairas]] 16:14, 8 January 2010 (UTC) | ||
| + | |||
| + | == 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. | ||
Revision as of 17:49, 11 June 2010
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)
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.