KDE Mobile/QML/Components: Difference between revisions
Created page with 'Started ~~~~ Facts: *Desktop KDE apps are very different, they use KDE/Qt Widgets. *To port and app, one needs to extracte the business logic and design the workflow for the mob...' |
No edit summary |
||
| Line 1: | Line 1: | ||
Started [[User:Jstaniek|Jstaniek]] 21:15, 7 March 2011 (UTC) | Started [[User:Jstaniek|Jstaniek]] 21:15, 7 March 2011 (UTC) | ||
Facts | ==Facts== | ||
*Desktop KDE apps are very different, they use KDE/Qt Widgets. | *Desktop KDE apps are very different, they use KDE/Qt Widgets. | ||
*To port and app, one needs to extracte the business logic and design the workflow for the mobile UX. | *To port and app, one needs to extracte the business logic and design the workflow for the mobile UX. | ||
*Basic, default QML components may be sufficient but it's good to perform some research | *Basic, default QML components may be sufficient but it's good to perform some research | ||
*Default QML components may need styling compliant with various mobile platforms, currently those Android-based | *Default QML components may need styling compliant with various mobile platforms, currently those Android-based | ||
Revision as of 21:15, 7 March 2011
Started Jstaniek 21:15, 7 March 2011 (UTC)
Facts
- Desktop KDE apps are very different, they use KDE/Qt Widgets.
- To port and app, one needs to extracte the business logic and design the workflow for the mobile UX.
- Basic, default QML components may be sufficient but it's good to perform some research
- Default QML components may need styling compliant with various mobile platforms, currently those Android-based