< Plasma | Next Revision as of 17:14, 21 January 2014 (view source)Afiestas (talk | contribs)← Older edit Revision as of 17:21, 21 January 2014 (view source) Afiestas (talk | contribs) Newer edit → Line 39: Line 39: === powerdevil/dpms === === powerdevil/dpms === Needs port to drm and probably go to KWin Needs port to drm and probably go to KWin +=== kscreen === +Port to drm/kms and probably put it in KWin Revision as of 17:21, 21 January 2014 List of modules/libs that will need any work to run on Wayland: Contents 1 kcontrol 1.1 krdb 1.2 access 1.3 colors 1.4 fonts 1.5 input 1.5.1 cursortheme 1.5.2 mouse 1.6 keyboard 1.7 kfontsinst 1.8 style 1.9 khotkeys 1.10 kinfocenter 1.11 klipper 1.12 krunner 1.13 ksmserver 1.14 ksysguard 1.15 lib/taskmanager 1.16 powerdevil/dpms 1.17 kscreen kcontrol Some KCM Modules need porting or at least adding runtime checks to avoid running some code 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 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 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. keyboard Needs port tohttp://xkbcommon.org/ 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 Retrieved from "https://community.kde.org/index.php?title=Plasma/Next/Wayland&oldid=36192" Content is available under Creative Commons License SA 4.0 unless otherwise noted.