xpra icon
Bug tracker and wiki

Changes between Version 15 and Version 16 of ProjectIdeas


Ignore:
Timestamp:
02/25/14 11:22:25 (6 years ago)
Author:
Antoine Martin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ProjectIdeas

    v15 v16  
    1717
    1818       Xpra acts as an X11 compositor, and uses many different X APIs and features to achieve its purpose. We have run into some limitations related to X11 features.
    19        For example, Xpra has to be able to dynamically adapt the remote (server-side) virtual framebuffer to match the client configuration. Although this mostly works ok using {{{xf86-video-dummy}}} and [/wiki/FakeXinerama libfakeXinerama], there is still much room for improvement.
    20        * Better [http://en.wikipedia.org/wiki/RandR RandR] support in the dummy driver (or maybe in the core server?) to allow us to use any resolution we choose without needing to have it pre-defined in the [/browser/xpra/trunk/src/etc/xpra/xorg.conf xorg.conf] shipped with xpra.
    21        * DPI issues (should probably be tied to {{{RandR}}}): some applications will talk to the X11 server directly to obtain the screen dimensions and calculate their own DPI value. The virtual screen we define for Xpra is not meant to have a fixed size: it is meant to adapt to what the client specifies.
     19       For example, Xpra has to be able to dynamically adapt the remote (server-side) virtual framebuffer to match the client configuration exactly. Although this mostly works OK using {{{xf86-video-dummy}}} and [/wiki/FakeXinerama libfakeXinerama] (to fake the same number of screens), there is still much room for improvement.
     20       * Better [http://en.wikipedia.org/wiki/RandR RandR] support in the [http://cgit.freedesktop.org/xorg/driver/xf86-video-dummy/ dummy driver] ({{{xf86-video-dummy}}}) to allow us to use any resolution we choose without needing to have it pre-defined in the [/browser/xpra/trunk/src/etc/xpra/xorg.conf xorg.conf] shipped with xpra. The changes may actually need to be applied to the core server and/or the dummy driver.
     21       * DPI issues (should probably be tied to the {{{RandR}}} issue above - though it may also interact with {{{libfakeXinerama}}}): some applications will talk to the X11 server directly to obtain the screen dimensions and calculate their own DPI value. The virtual screen we define for Xpra is not meant to have a fixed size: it is meant to adapt to what the client specifies and should be changed whenever a new client connects. Because the X11 server assumes that the dummy screen size is fixed, the DPI values calculated by the client applications will vary widely depending on the current screen resolution set at the time, causing some ugly rendering problems. The dummy driver needs to support changes to the "phisical" screen dimension at runtime (and not just the resolution).
    2222       * [http://keithp.com/blogs/dri3k_first_steps/ DRI3K] support. Someone interested in the world of X.org may be interested in this project.
    2323