genode/repos/demo/src/server/liquid_framebuffer
Norman Feske b44f0554bd Adapt high-level components to new parent API
This patch adjusts the various users of the 'Child' API to the changes
on the account of the new non-blocking parent interface. It also removes
the use of the no-longer-available 'Connection::KEEP_OPEN' feature.

With the adjustment, we took the opportunity to redesign several
components to fit the non-blocking execution model much better, in
particular the demo applications.

Issue #2120
2016-11-30 13:37:03 +01:00
..

Liquid frame buffer is an implementation of the frame buffer interface
running as a client of the Nitpicker GUI server. It supports the
following configuration options. The example shows the default
values.

! <config
!
!   <!-- enable the animated background,
!        valid values are 'on' and 'off' -->
!   animate="on"
!
!   <!-- the initial window position and
!        size of the virtual frame buffer -->
!   xpos="400"
!   ypos="270"
!   width="500"
!   height="400"
!
!   <!-- set the window title -->
!   title="Liquid Framebuffer"
!
!   <!-- show a resize handle,
!        valid values are 'on' and 'off' -->
!   resize_handle="off"
!
!   <!-- show window decoration (title bar and borders),
!        valid values are 'on' and 'off' -->
!   decoration="on"
!
! />

Because Liquid frame buffer creates the virtual frame-buffer window at
start time, not at session-creation time, sufficient memory resources must
be provided when starting the program. Consequently, the client does not
need to donate memory for the frame buffer backing store.

Liquid frame buffer supports only one client. If multiple
virtual frame buffers are needed, multiple instances of the
program should be used.