Jump to content

Plasma/Akademy2k14: Difference between revisions

From KDE Community Wiki
D ed (talk | contribs)
Sebas (talk | contribs)
add notes page
 
(6 intermediate revisions by 3 users not shown)
Line 1: Line 1:
==Notes==
https://notes.kde.org/p/plasma-bof-akademy-2014
==Agenda==
==Agenda==
===Increasing Involvement===
We are currently quite a small core team, we need to get some new blood flowing.
Brainstorming session on improving this.


===HighDpi===
===HighDpi===
Line 5: Line 13:
* Qt5.4 merges its high DPI support for the X backend.
* Qt5.4 merges its high DPI support for the X backend.
* We need this for apps
* We need this for apps
* Plasma Framework does it's own thing
* Plasma Framework does its own thing
* Both have advantages, disadvantages and clashes!
* Both have advantages, disadvantages and clashes!
(Plasma 5.2+ material)
(Plasma 5.2+ material)
Line 12: Line 20:


Where do we put each plasmoid; plasma-workspace, plasma-desktop, plasma-addons, kde-look. I want defined rules.
Where do we put each plasmoid; plasma-workspace, plasma-desktop, plasma-addons, kde-look. I want defined rules.
===Plugin loading===
* unify and finalize the way plugins are loaded
* duplicate macros?
* remove the old ones?
===SLC===
===Shell loading===
* loading every shell's "handler.qml" doesn't scale, intentions and needed input features  should perhaps be just config files
SLC BoF
===Wayland===
* Protocols and Interfaces
* Session bringup
* More X11-specific bits
===System Settings===
* Redesign ideas
* Strategy

Latest revision as of 12:47, 8 September 2014

Notes

https://notes.kde.org/p/plasma-bof-akademy-2014

Agenda

Increasing Involvement

We are currently quite a small core team, we need to get some new blood flowing. Brainstorming session on improving this.

HighDpi

  • Qt5.4 merges its high DPI support for the X backend.
  • We need this for apps
  • Plasma Framework does its own thing
  • Both have advantages, disadvantages and clashes!

(Plasma 5.2+ material)

Which repo for which plasmoid

Where do we put each plasmoid; plasma-workspace, plasma-desktop, plasma-addons, kde-look. I want defined rules.

Plugin loading

  • unify and finalize the way plugins are loaded
  • duplicate macros?
  • remove the old ones?

SLC

Shell loading

  • loading every shell's "handler.qml" doesn't scale, intentions and needed input features should perhaps be just config files

SLC BoF

Wayland

  • Protocols and Interfaces
  • Session bringup
  • More X11-specific bits

System Settings

  • Redesign ideas
  • Strategy