genode

History

Norman Feske 8243329ad4 os: Move Genode::Config into 'config' library Originally, the convenience utility for accessing a process configuration came in the form of a header file. But this causes aliasing problems if multiple compilation units access the config while the configuration gets dynamically updated. Moving the implementation of the accessor to the singleton object into a library solves those problems.		2013-09-23 14:25:58 +02:00
..
framebuffer_window.h	liquid_fb: dynamic reconfiguration support	2013-05-22 21:30:17 +02:00
main.cc	liquid_framebuffer: fix initial window size	2013-06-10 10:45:31 +02:00
README	liquid_fb: dynamic reconfiguration support	2013-05-22 21:30:17 +02:00
services.cc	liquid_fb: dynamic reconfiguration support	2013-05-22 21:30:17 +02:00
services.h	liquid_fb: dynamic reconfiguration support	2013-05-22 21:30:17 +02:00
target.mk	os: Move Genode::Config into 'config' library	2013-09-23 14:25:58 +02:00

README

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.