KDE Device spectrum:
  Plasma Netbook




     Marco Martin
Why for netbooks?
Why KDE SC?
Why KDE SC?




     ●   Configurability
     ●   Rich api
     ●   Solid system to build upon
     ●   Us
Why Plasma?
Why Plasma?


●   Primary UI
●   Flexible, no assumptions we are in a desktop
●   In some cases secondary ui too
●   Start...
What do you want?



●   Users
     vs
●   Developers
Users
●   Something useful: content content content
Users
●   Something pretty
Developers
●   Powerful API
Common components
●   Separation between data and visualization
●   Plasma::Dataengine
●   Runners
●   They can be used on...
Common components
●   Visual theme engine based on SVG
●   Widget set
    ●   Based on QGraphicsView
    ●   Reusable
    ...
Common components
●   Plasmoids are designed to work at least:
    ●   Desktop
    ●   Panel
    ●   Netbook newspaper pag...
Netbook: window management
●   The desktop is an “application”
●   no border maximized windows
●   Present windows is the ...
Netbook: Search and launch
Netbook: Search and launch




   ●   Search more intuitive than browsing categories
   ●   Reuses runners
   ●   Simple m...
Netbook: newspaper
Netbook: newspaper



●   Flicking here too
●   Primary place for widgets
●   Biggest use case: PIM and webservice client
...
Future
●   Polishing
●   More widgets, especially PIM related
●   Caching for dataengines
●   Different devices: what comp...
Upcoming SlideShare
Loading in …5
×

Akademy 2010 presentation

391 views

Published on

Presentation about the Plasma architecture and the Plasma Netbook shell

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
391
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Akademy 2010 presentation

  1. 1. KDE Device spectrum: Plasma Netbook Marco Martin
  2. 2. Why for netbooks?
  3. 3. Why KDE SC?
  4. 4. Why KDE SC? ● Configurability ● Rich api ● Solid system to build upon ● Us
  5. 5. Why Plasma?
  6. 6. Why Plasma? ● Primary UI ● Flexible, no assumptions we are in a desktop ● In some cases secondary ui too ● Start from netbook, first logical step, less alien ● Alessandro will talk about someting even more challenging
  7. 7. What do you want? ● Users vs ● Developers
  8. 8. Users ● Something useful: content content content
  9. 9. Users ● Something pretty
  10. 10. Developers ● Powerful API
  11. 11. Common components ● Separation between data and visualization ● Plasma::Dataengine ● Runners ● They can be used on each shell, regardless of the visualization ● Plugins, loaded on demand Data ● Easy to mash-up
  12. 12. Common components ● Visual theme engine based on SVG ● Widget set ● Based on QGraphicsView ● Reusable ● Simple API ● Touchscreen friendly widgets like “flickable” scroll widgets Visualization
  13. 13. Common components ● Plasmoids are designed to work at least: ● Desktop ● Panel ● Netbook newspaper pages ● Standalone windows (from 4.5) ● Fullscreen on mobile devices (some of them) Plasmoids
  14. 14. Netbook: window management ● The desktop is an “application” ● no border maximized windows ● Present windows is the taskbar ● Some other different default settings
  15. 15. Netbook: Search and launch
  16. 16. Netbook: Search and launch ● Search more intuitive than browsing categories ● Reuses runners ● Simple menu, no trees ● Use of flicking and drag and drop
  17. 17. Netbook: newspaper
  18. 18. Netbook: newspaper ● Flicking here too ● Primary place for widgets ● Biggest use case: PIM and webservice client widgets here
  19. 19. Future ● Polishing ● More widgets, especially PIM related ● Caching for dataengines ● Different devices: what components can be reused on netbooks with touchscreen, tablets or smaller mobile devices? ● Beyond workspaces: application dashboards for Kontact, Skrooge and Kdevelop

×