1.
KDE mobile: Plasma
Marco Martin 1

2. Desktop, netbook, mobile
Desktop, netbook, mobile
KDE3: Kdesktop and Kicker, technical limitations
What we needed Data (tasks, weather, news) and visualization (desktop widgets, panel...)
Qt 4 and QGraphicsView -> Plasma
Without QWidgets limitations 2

3.
Plasma is a library
Data fetching and connection to visualizations, both based on plugins
Advanced SVG theme engine: widgets with touch capability (flickable views) today, QtComponents tomorrow
Loading of addon packages from Open Collaboration Services (with Attica)
Remote sharing of widgets 3

4. Workspaces: device spectrum
Workspaces: device spectrum
Plasma Desktop -> traditional desktop with panels, wallpaper etc, desktop widgets hooked to DataEngines
Plasma Netbook -> full screen menu, full screen application switcher, “pages” of Plasma widgets to access quickly to information and content
Plasma Mobile -> launcher and widget space both optimized for touchscreen, activity based. Uses QML to be customizable on different devices
3 workspaces, 3 behaviours, one technology 4

5. Workspaces: device spectrum
Workspaces: device spectrum 5

6. Workspaces: device spectrum
Workspaces: device spectrum 6

7. Workspaces: device spectrum
Workspaces: device spectrum
3 workspaces, 3 behaviours, one technology 7

8.
Beyond workspaces 8

9.
Beyond workspaces
A Plasma Widget can be designed complex enough to be a full screen application on mobile
It is possible to write a Plasma widget in pure QML, with device specific files and shared ones
In the following example, in less than ~80KB we have an RSS reader with a Plasma Desktop, a MeeGo Handheld and a MeeGo Tablet UI, last two with QtComponents 9

10. 10

11. 11

12. 12