Proposal: Split Xfitman and liblxqt

46 views
Skip to first unread message

PCMan

unread,
Apr 7, 2014, 12:44:06 PM4/7/14
to lxde-list, razo...@googlegroups.com, Александр Соколов
Hello,
For smoother migration toward Qt5 and Wayland, I'd like to propose
splitting Xfitman from liblxqt.

The rationale.
1. Due to Xfitman, liblxqt depends on Xlib now. All programs using
liblxqt got the indirect dependency on Xlib, too. Actually, many of
them only requires LxQt::Settings.

2. Actually, every Qt programs are using liblxqt implicitly since our
Qt platform plugin reads LxQt settings using liblxqt and apply the
settings to other Qt programs.

3. The only components that use Xfitman are: lxqt-panel (very heavy
use), app switcher (used 4 methods), notification daemon (used 2-3
methods), and runner (used 2 methods only). Other components depending
on liblxqt does not require X11 at all.

4. Xfitman will stop working in Qt5 and Wayland. Qt5 uses xcb, and X11
event filters work differently, giving us xcb event structures, not
XEvent. In the Wayland/weston world, xdg_shell will be used to replace
some of the functionality of NETWM. EWMH will stop working. The
desktop panel may need to be a compositor plugin in wayland, too. So
this part is hard to port to wayland. It might be needed to add a
layer of abstraction around Xfitman and avoid touching X11 directly to
ease the porting.

Any comments?
As the developer of Xfitman, Alexander Sokoloff, do you have any suggestions?

Thank you all!
Reply all
Reply to author
Forward
0 new messages