Recent Features
| |||||||||||||
LFCS 2012: X and WaylandLFCS 2012: X and WaylandPosted Apr 13, 2012 9:29 UTC (Fri) by dgm (subscriber, #49227)In reply to: LFCS 2012: X and Wayland by glandium Parent article: LFCS 2012: X and Wayland
Each Wayland's compositor should provide it's own library. In a tiling Window manager most functions would be stubs, because windows do not really need decorations.
(Log in to post comments)
LFCS 2012: X and Wayland Posted Apr 15, 2012 18:06 UTC (Sun) by glandium (subscriber, #46059) [Link]
It doesn't really look like it's designed this way... How would these libraries be linked anyways? Toolkits would link with a generic implementation, and different implementations would be LD_PRELOADed at runtime? (or something similar)
LFCS 2012: X and Wayland Posted Apr 16, 2012 11:28 UTC (Mon) by nix (subscriber, #2304) [Link]
It's more likely that the Wayland library would read a configuration file (or other configuration state) which would then give it the name of a plugin .so to load to implement the pluggable stuff.
But, noooo, it's better to force people to reimplement or fork the whole thing! Bah.
|
|||||||||||||