Difference between revisions of "Plasma/Next/Wayland"

< Plasma‎ | Next
Jump to: navigation, search
(Created page with "List of modules/libs that will need any work to run on Wayland: == kcontrol == Some KCM Modules need porting or at least adding runtime checks to avoid running some code === ...")
 
(kcontrol)
 
(2 intermediate revisions by one other user not shown)
Line 2: Line 2:
  
 
== kcontrol ==
 
== kcontrol ==
Some KCM Modules need porting or at least adding runtime checks to avoid running some code
+
Some KCM Modules need porting or at least adding runtime checks to avoid running some code. A KCM which is too X specific can be forced to be only shown on X11 with:
 +
X-KDE-OnlyShowOnQtPlatforms=xcb
 +
in the desktop file.
 
=== krdb ===
 
=== krdb ===
 
Already has HAVE_X11 so compilation is already optional. It seems that the code is no longer needed with Qt5 since we have our own QPT.
 
Already has HAVE_X11 so compilation is already optional. It seems that the code is no longer needed with Qt5 since we have our own QPT.
 
=== access ===
 
=== access ===
Uses krdb
+
Uses krdb, uses XKblib. Currently excluded from listing on non-x11.
 
=== colors ===
 
=== colors ===
 
Uses krdb
 
Uses krdb
Line 12: Line 14:
 
Uses krdb, already has HAVE_X11 for dpi configurationj
 
Uses krdb, already has HAVE_X11 for dpi configurationj
 
=== input ===
 
=== input ===
Rewrite all this with abstraction so we can support both, X11 and Wayland
+
Rewrite all this with abstraction so we can support both, X11 and Wayland, some modules are currently excluded from listing on non-X11
 
==== cursortheme ====
 
==== cursortheme ====
 
Needs abstraction, and implement wl_cursor_* backend for Wayland.
 
Needs abstraction, and implement wl_cursor_* backend for Wayland.
 
==== mouse ====
 
==== mouse ====
These settings belong now to the compositor (KWin), so we need to sort things out over there.
+
These settings belong now to the compositor (KWin), so we need to sort things out over there. Currently excluded from listing on non-X11.
 
=== keyboard ===
 
=== keyboard ===
Needs port tohttp://xkbcommon.org/  
+
Needs port to http://xkbcommon.org/ Currently excluded from listing on non-X11.
 
=== kfontsinst ===
 
=== kfontsinst ===
 
Drop Xft support and move to fontconfig only
 
Drop Xft support and move to fontconfig only
 
=== style ===
 
=== style ===
 
Uses krdb
 
Uses krdb
 +
== khotkeys ==
 +
Needs to be implemented somehow inside KWin, since the compositor is the only one that has access to the mouse.
 +
== kinfocenter ==
 +
Some calls to X api has to be made platform specific, it has a lot of #ifdef Q_WS_X11 already. Maybe also add a module for Wayland information.
 +
==  klipper ==
 +
Clipboard is handled by the compositor (KWin), we might need to wait to port klipper to it
 +
== krunner ==
 +
Probably won't need any porting once krunner in plasma2 is released. We might need a way of making sure it is placed centered on the screen since Apps can't decide position on Wayland.
 +
== ksmserver ==
 +
If screenlocker is split, we will only need to implement a new session management api based on dbus.
 +
== ksysguard ==
 +
Make the X11 platform dependent, they do not make sense in Wayland (x11 memory usage)
 +
== lib/taskmanager ==
 +
Needs platform abstraction and then talk to KWin
 +
== powerdevil/dpms ==
 +
Needs port to drm and probably go to KWin
 +
== kscreen ==
 +
Port to drm/kms and probably put it in KWin

Latest revision as of 08:00, 12 February 2014

List of modules/libs that will need any work to run on Wayland:

kcontrol

Some KCM Modules need porting or at least adding runtime checks to avoid running some code. A KCM which is too X specific can be forced to be only shown on X11 with: X-KDE-OnlyShowOnQtPlatforms=xcb in the desktop file.

krdb

Already has HAVE_X11 so compilation is already optional. It seems that the code is no longer needed with Qt5 since we have our own QPT.

access

Uses krdb, uses XKblib. Currently excluded from listing on non-x11.

colors

Uses krdb

fonts

Uses krdb, already has HAVE_X11 for dpi configurationj

input

Rewrite all this with abstraction so we can support both, X11 and Wayland, some modules are currently excluded from listing on non-X11

cursortheme

Needs abstraction, and implement wl_cursor_* backend for Wayland.

mouse

These settings belong now to the compositor (KWin), so we need to sort things out over there. Currently excluded from listing on non-X11.

keyboard

Needs port to http://xkbcommon.org/ Currently excluded from listing on non-X11.

kfontsinst

Drop Xft support and move to fontconfig only

style

Uses krdb

khotkeys

Needs to be implemented somehow inside KWin, since the compositor is the only one that has access to the mouse.

kinfocenter

Some calls to X api has to be made platform specific, it has a lot of #ifdef Q_WS_X11 already. Maybe also add a module for Wayland information.

klipper

Clipboard is handled by the compositor (KWin), we might need to wait to port klipper to it

krunner

Probably won't need any porting once krunner in plasma2 is released. We might need a way of making sure it is placed centered on the screen since Apps can't decide position on Wayland.

ksmserver

If screenlocker is split, we will only need to implement a new session management api based on dbus.

ksysguard

Make the X11 platform dependent, they do not make sense in Wayland (x11 memory usage)

lib/taskmanager

Needs platform abstraction and then talk to KWin

powerdevil/dpms

Needs port to drm and probably go to KWin

kscreen

Port to drm/kms and probably put it in KWin


This page was last edited on 12 February 2014, at 08:00. Content is available under Creative Commons License SA 4.0 unless otherwise noted.